Find published dossiers by topic, company, product or technology.

Showing 61–80 of 107 dossiers

Formbricks 6.0 makes SpiceDB mandatory for self-hosted surveys — and ends legacy follow-ups in December

The consequential change in Formbricks 6 isn't its new charts: self-hosted operators need a separate authorization service, a maintenance window and verified migration before enabling v6 traffic. Existing follow-up automations also have a December deadline.

DocsBot says better customers are barely offsetting a shrinking signup funnel

The useful small-SaaS lesson is not that SEO is dead or AI search has won. DocsBot’s own numbers show how a channel can remain the largest share of conversions while the total funnel underneath it shrinks, and how 'Direct' can conceal the discovery path that actually influenced a sale.

Meta Muse turns a consumer AI assistant into a persistent agent — and its first Mac zero-day tests the containment model

Muse packages persistent autonomous execution, credentials, payments, app access and memory into a mainstream consumer product. A September macOS hotfix now provides an early real-world lesson: agent containment has to protect not only the cloud runtime but also the local control path into the agent.

Cognition’s Fusion uses a frontier lead and cheaper sidekick to cut coding-agent task cost

Fusion is interesting less as another routing feature than as a different agent-cost architecture: two persistent model contexts divide planning, review and execution instead of making one expensive model handle every token. The practical question for builders is shifting from token price to cost per completed task.

Azure Document Intelligence v2.0 API retires August 31 — old integrations need a version migration

Azure Document Intelligence v2.0 reaches retirement on August 31, 2026. Microsoft recommends moving workloads to the current v4.0 API; the post-v2 REST surface was redesigned, so teams should verify the actual api-version their SDK or HTTP client sends rather than assuming a package upgrade is enough.

Vercel Sandbox expands from four regions to all 20 — with ordered failover

For agent and untrusted-code workloads, the useful change is not simply lower latency. Sandbox location becomes an explicit execution policy, so teams can align code execution with nearby data and avoid a resilience fallback quietly moving work outside an allowed region.