What Happened
datasette-llm 0.1a11 adds support for OpenAI-compatible endpoints, allowing other Datasette plugins to use models hosted outside OpenAI. Local models served through LM Studio, Ollama or llama.cpp can now power a Datasette Agent instance. The release example uses uvx to launch Datasette with datasette-agent, a local model endpoint and a SQLite database, content.db. [1]…
What Happened
Four AWS implementation reports illustrate a practical principle for enterprise AI: match the serving architecture to the workload before optimizing models or buying more capacity. Scheduled predictions, interactive agents, coding assistants and long-running scientific inference have different latency, isolation and cost requirements. [1][2][3][4]
Scheduled ML: GS Caltex separates model release from inference execution.…
What Happened
Google is expanding two capabilities that move AI operations closer to enterprise data: agent observability in BigQuery and Looker, and model-powered text processing inside AlloyDB. Together, they offer a way to reduce separate telemetry pipelines and application-side inference code—not replace the orchestration layer of an AI platform. [1][2]
Agent observability: BigQuery conversation logging,…
What Happened
Recent AWS and Google Cloud releases move more AI infrastructure into managed services: retrieval, agent execution, tool integration, web search and database-native inference. The architectural opportunity is to reduce custom orchestration and infrastructure work. The operational challenge is that application teams still own authorization, answer quality, release decisions and recovery.
Managed retrieval: Amazon…
What Happened
Recent releases point toward a more differentiated enterprise AI stack: specialized models for narrow decisions, database-integrated inference for structured processing, and general-purpose models reserved for harder tasks. The opportunity is lower operating cost; the engineering challenge is preserving accuracy, security and predictable behavior across those execution paths.
Decision APIs are competing on price…
What Happened
Google Cloud’s latest AI announcements address three production bottlenecks: moving data into model workflows, controlling agents across enterprise systems, and allocating accelerator capacity efficiently.
Database-native AI: AlloyDB introduced preview functions ai.classify and ai.extract for text classification and structured JSON extraction through SQL. They require PostgreSQL 18 and google_ml_integration version 1.6.1 or later. Smart…
What Happened
Recent enterprise AI deployments point to a common architecture: bounded agents inside governed workflows, with explicit execution controls, model routing and invocation-level observability.
TCS’s Agentic Test Orchestrator connects requirements, test generation, execution, correction and reporting. Specialized agents run on Amazon Bedrock AgentCore under a deterministic supervisor; Amazon EKS handles application intake, while Amazon…
What Happened
The llm-anthropic 0.31 release added support for Anthropic’s Fable 5.2 and Mythos 5.2. Fable 5.2 is available through the llm CLI as claude-fable-5.2. [1]
The accompanying test highlights a deployment risk: when asked to generate an SVG of a pelican riding a bicycle, Fable 5.2 produced its best result at the xhigh reasoning…
What Happened
Enterprise AI adoption is being constrained by existing software estates, while cloud platforms are making specialized compute more flexible. The architectural challenge is to gain that flexibility without replacing legacy dependence with new infrastructure commitments.
A Google Cloud and Hypothesis Group survey of 1,250 U.S. enterprise IT and business decision-makers found that 49%…
What Happened
On The Vergecast, Nilay Patel argued that current AI products do not deliver benefits clear enough to justify their costs. He pointed to data-center noise, low-quality generated content and agents that do not yet work as users expect. He also asserted that companies spend more on these products than they earn. These are…
What Happened
Recent Google Cloud announcements highlight three connected requirements for production AI: asynchronous orchestration, governed data access and explicit unit economics.
Orchestration at creative-production scale: Mito built an asynchronous Google Cloud platform to coordinate more than 5,000 assets, including 1,000 videos, across roughly 65 rounds of iteration for a 120-second Movistar Plus+ television spot.…
What Happened
Google Cloud has made Gemini Omni 1.2 Flash generally available for video generation and editing, with API access, Provisioned Throughput, enterprise security capabilities and imperceptible SynthID watermarking. The model supports clips up to 15 seconds and lists a price of $0.07 per second for 720p video, 30% below version 1.1. [1]
The release…