Google previews AlloyDB Express for coding-agent databases Google previews AlloyDB Express for coding-agent databases

Development databases

Express automatically pauses unused compute and wakes when a connection or query arrives. The instances retain AlloyDB’s vector, text and hybrid search capabilities, alongside Gemini functions callable from SQL. Google offers natural-language SQL tooling for developers working through database queries. An in-place upgrade preserves data, schemas, users and connection details, allowing an application to move beyond the development configuration without changing its connection string.

Creation speed is not wake-up speed

Google’s overview distinguishes approximately two-second provisioning through public DNS from roughly twenty seconds through Private Service Connect. Resuming a paused instance also takes about twenty seconds. Express supports PostgreSQL 18 and a single zonal primary, with no standby. Storage grows automatically to 20 GB, at which point further writes are blocked. The connection ceiling is fixed at 200; changing the corresponding database flag has no effect. Backups, point-in-time recovery, cross-region disaster recovery and high availability are unavailable, and Express has no service-level agreement. Memory-intensive extensions can exhaust the instance’s four or eight gigabytes of memory. Maintenance normally occurs when an instance resumes or during low usage. The documentation lists seven supported regions, rather than worldwide availability. Once upgraded to standard AlloyDB, a cluster cannot return to Express.

Network and upgrade choices need explicit handling

Creation requires one vCPU; requesting two initially fails, although resizing to two is supported afterward. The console enables both public DNS and Private Service Connect, while CLI, API and MCP creation defaults to private connectivity. Public DNS must be enabled separately in those flows. The MCP instance-creation tool automatically enables Data API access and IAM database authentication. Direct PostgreSQL clients using public DNS need an external-IP allowlist. The authenticated proxy and language connectors do not require that list. Updating authorized networks replaces the entire existing list, so an automation must preserve entries it still needs. The management guide also places conditions on the production upgrade. Keeping a one-vCPU instance requires a region supporting C4A machines; otherwise, resize to two first. Upgrading disables scale-to-zero and switches the database to always-on AlloyDB billing. It opens access to production features rather than automatically configuring them. Customer-managed encryption keys cannot be introduced as part of that upgrade. The upgrade keeps the vCPU count but doubles memory per vCPU from four to eight gigabytes.