Showing 161–180 of 182 dossiers

Grafana Agent Observability links live agent telemetry to evals and CI regression gates

The observe–test–release loop now has explicit economics: Free and Pro include 30,000 captured generations and 25 million system-initiated AI tokens per month; Pro overages start at $1.50 per 1,000 generations and $2 per million LLM Eval/Guard tokens, while ordinary telemetry is billed separately.

Amazon Aurora Serverless gets faster burst scaling

Aurora Serverless can now add roughly 12 ACUs in the first second of a scale-up event on platform versions 3 and 4. The change is automatic and is most useful for bursty SaaS, API, batch and agent workloads, but it does not remove the separate resume delay when a database has scaled all the way to zero.

Railway Cloud Agents turn coding agents into persistent deployment-adjacent VMs

Railway Cloud Agents are managed, persistent development machines rather than a new model or harness. They reuse developers’ existing agent credentials, sleep when disconnected by default, retain disk state, and live inside Railway project environments—blurring the boundary between remote coding workspace and deployment platform.

Docker Desktop is replacing its third-party VM layer with Docker VMM

Docker VMM gives Docker direct control over Desktop’s hidden Linux-VM layer and is still targeted to become the default for new installs at GA. The August 24 Desktop 4.88 release is an important beta signal: it fixes a severe inbound-network-throughput regression and removes a 28 GiB Mac memory ceiling, reinforcing the need for workload-specific testing before standardisation.

Neon’s branchable backend reaches Europe as Functions and Object Storage expand to Frankfurt

Neon is extending database branching into a broader backend stack and now into a second geography. The Frankfurt expansion improves latency and data-location choices, but Functions and Object Storage remain beta products with pricing and production boundaries still unsettled.

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.

Supabase fixes broken client trace propagation and now preserves trace IDs even for unsampled requests

supabase-js 2.112.3 materially improves the tracing rollout BTN covered earlier: unsampled requests now still carry traceparent for backend log correlation, tracing misconfiguration produces warnings, and browser Edge Function calls need current CORS headers to admit W3C trace context.

Cloud decisions show up in reliability, latency, security and the monthly bill. This beat follows hosting, edge platforms, compute, AI infrastructure and important changes across the providers and tools that keep internet products running.

BTN focuses on developments that alter an engineering or business decision: a new capability, a material price change, a platform constraint or an operational risk. The goal is not to reproduce provider announcements, but to explain what the change means for teams running real services.