Long-form from our team. Engineering, product, and company posts.
When an AI assistant changes your content through an MCP server, the first question is who did it. A shared project key cannot answer that, and it cannot be taken back from one person. Here is what we replaced it with, and the six details that mattered.
Your site has a dark mode toggle. The support widget in the corner does not care. Here is why embedded widgets get theming wrong — the OS media query, the shadow root, the remount — and what a widget needs to offer so yours does not.
The Model Context Protocol has no way to send a file, and the obvious workarounds either burn tokens or turn your server into a proxy. Here is the presign, upload, confirm shape we shipped, and the four details that decide whether it is safe.
Tool calling and streaming pull in opposite directions, and the obvious way to reconcile them makes every answer twice: once to find out it was an answer, once to show it. Here is the shape of the bug, and what streaming every round actually costs you in care.
An anonymous chat log tells you what people asked. It cannot tell you whether your best customer has asked the same thing four times. Here is how to add identity to an AI support widget without turning it into a security hole.
Most RAG chatbots show you what they retrieved, not what they used. The two are different sets, and conflating them quietly destroys the one thing citations are for: trust.
AI agents are becoming heavy readers of product docs. How llms.txt, MCP servers, and structured content make yours legible to them.
A step-by-step guide to building a SaaS help center: article structure, categories, semantic search, AI answers, and keeping docs on your own domain.
A practical guide to adding a blog to a SaaS product: architecture options, rendering, SEO metadata, and a build path that takes hours, not weeks.
How a headless CMS differs from a traditional CMS, where each wins, and why SaaS products usually end up API-first. A practical comparison.
Does fetching content from an API hurt SEO? No — if you render it right. Canonicals, structured data, sitemaps, and the checklist that matters.