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

Showing 101–120 of 139 dossiers

OpenAI’s Assistants API has shut down

The Assistants API shutdown date has passed. OpenAI’s deprecation documentation lists August 26, 2026 as the removal date and directs developers to Responses and Conversations for replacement workloads.

Meta opens Muse Spark’s 816B weights — but large model-as-a-service operators need a separate licence

Meta Muse Spark Open is genuinely downloadable, unlike a promised future weight release. But 42B active parameters do not make its 816B weights cheap to host, and the Muse Model License is not Apache or MIT: model-as-a-service operators over $20M in affiliated annual gross revenue need a separate agreement.

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.

Buttondown cut its database from 2TB to 750GB by deleting three legacy tables

Buttondown’s 'Great Pruning' is a small-SaaS operations story about deleting architecture rather than adding it. The company removed duplicated or over-retained request and email-event data after changing how those workloads were processed.

Claude Code Projects turns one engineering goal into parallel cloud-agent branches

The important change is not simply that Claude can run several agents. Projects now owns decomposition, shared context, branch isolation and progress coordination across full Claude Code sessions, while the trade-offs become usage burn, cloud-only execution and ordinary merge conflicts when parallel work overlaps.

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.