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

Showing 61–80 of 84 dossiers

Google Cloud is making every Application Integration run execute under an explicit identity

The migration turns integration identity from an implicit platform detail into an operational dependency. Teams may need new run-as accounts and `Service Account User` grants not only for runtimes but also for editors, publishers, approvers and deployment automation.

Anthropic’s Model Hardware Standard gives AI agents a shared interface for physical devices

MHS is an attempt to make microscopes, liquid handlers, robotic arms and other programmable hardware look like a consistent tool surface to AI agents. It is still a research preview, but the interoperability layer is already being tested with research institutions and hardware vendors.

VS Code is moving coding agents into a standalone host with shared AHP sessions

Microsoft is rearchitecting VS Code around a dedicated Agent Host rather than treating each coding agent as an editor-bound extension. AHP gives different harnesses one shared session model, but the rollout is still active and VS Code 1.132 removed the administrator policy that had centrally disabled the Agent Host.

Qwen3.8-27B brings stronger agentic coding into a locally deployable 27B model

Qwen3.8-27B is now available as open weights on Hugging Face and ModelScope. For builders, the important change is not another benchmark bump: a comparatively compact 27B model now combines native vision, long context, controllable reasoning and OpenAI-compatible serving paths for local or self-hosted coding and agent workloads.

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.

A 3,940-product SaaS census finds flat platform pricing is more common than pure per-seat billing

The useful finding is not that one pricing model has 'won.' It is that observable SaaS pricing is much more heterogeneous than the default per-seat narrative suggests—and that the answer changes sharply with methodology. PulseSignal’s living public-price census keeps moving, and its latest disclosed extraction audit improved to 90%, but the data should still be treated as directional packaging evidence rather than a universal market truth.

Funes gives coding agents a local memory that can follow you across tools and machines

Funes treats agent memory as user-owned data rather than a hosted account feature: retrieval and reranking run locally, provenance stays attached to recalled passages, and cross-machine sharing is optional. The main risk is that publishing session-derived memory can still expose secrets if redaction misses them.

Cloud Run adds singleton instances for long-lived, individually addressable workloads

Cloud Run instances sit between autoscaling serverless services and a small VM. They run one individually addressable container continuously, can be stopped and restarted, and use shared CPU economics; Google’s launch example prices 1 vCPU plus 1 GiB running for 30 days at $5.70.

Railway has stopped new services adopting Config as Code ahead of the December 1 hard cutoff

The August 28 transition is now active, and Railway’s current documentation removes an earlier ambiguity about new services in existing projects. Config as Code is legacy-only from here; production users should migrate and validate `.railway/railway.ts` before the December hard cutoff.

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.