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

Showing 141–160 of 242 dossiers

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.

GLM-5.3-Flash turns the anonymous Ox Alpha trial into an open-weight multimodal coding model

GLM-5.3-Flash combines open weights, multimodal coding/agent capability and an 18B-active sparse architecture with a large anonymous pre-launch trial. Z.ai has already issued a chat-template correction for early downloads, showing that day-one self-hosted deployments need artifact-level validation as well as model benchmarking.

Zipchat’s rebuild shows how platform risk reshaped its AI SaaS economics

Zipchat is useful as an operating case study, not a comeback story. Founder-reported figures show how a prior platform dependency failure influenced a new AI SaaS model built around reply-based pricing, channel diversification, revenue-based financing and tighter hiring discipline.

Gemini 3.8 Flash raises agent capability at the same token price — but may use more tokens per task

Gemini 3.8 Flash keeps 3.7 Flash’s promotional per-token rate and Flash-tier latency, but early independent analysis suggests harder reasoning can increase tokens consumed per task. A separate 3.8 Flash Cyber model is available only through Google’s Fairwind defensive-security program.

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.

Vercel lets coding-agent harnesses use your existing subscriptions without handing tokens to the sandbox

The change separates three things that are often bundled together: the harness, the subscription that pays for it, and the sandbox that executes it. Builders can switch among supported coding agents behind one interface while reusing existing subscription access and reducing credential exposure inside agent runtimes.