Releasesby GlyphAlloyDB now supports cross-region failover in Preview
AlloyDB now supports cross-region failover in Preview . You can optionally enable cross-region failover to automate the recreation of the original primary when a secondary cluster is promoted while maintaining your replication topology without requiring manual cluster deletion or re-creation.
Also shipped Jul 27, 2026Google Cloud in July 2026 →
AI_EXTRACT and AI_PARSE_DOCUMENT support for client-side encrypted stages and network-restricted accounts (Preview)
With this preview release, AI_EXTRACT and AI_PARSE_DOCUMENT support documents stored on stages that use client-side or server-side encryption, including in accounts that use PrivateLink or other network policies that restrict public network access to stages. For more information, see the following topics:
Custom incremental dynamic tables (General availability)
Custom incremental dynamic tables are now generally available. For more information, see Custom incrementalization .
[Launched] Generally Available: Claude Opus 5 on Azure Databricks
Azure Databricks now supports Anthropic Claude Opus 5 through AI Model Serving. Claude Opus 5 is Anthropic's latest model for advanced reasoning, coding, agentic workflows, and professional knowledge work. Claude Opus 5 is designed for complex tasks requi
GLM 4.7 reasoning_logprobs default will not ship before deprecation zai-glm-4.7 is scheduled for deprecation...
GLM 4.7 reasoning_logprobs default will not ship before deprecation zai-glm-4.7 is scheduled for deprecation on August 17, 2026 and will keep its existing default logprobs response shape until then. Requests that explicitly set the X-Cerebras-Version-Patch: 2 header still receive the separated reasoning_logprobs field.
Image Generation Models on OpenRouter
OpenRouter has introduced a dedicated /api/v1/images endpoint for image generation models, using the same billing and keys as chat completions.
Administration
AI credit controls for embed entity groups are now generally available. AI Fixed an issue where the Workload Identity Federation (WIF) role prefix wasn't properly configured across all AI-calling services, which could cause authentication failures when using Google Gemini Enterprise Platform (Vertex) as a custom AI model provider.
More from AlloyDBEvery AlloyDB release →
AlloyDB write endpoints are now available in Preview
AlloyDB write endpoints are now available in Preview . Write endpoints simplify database connection management by providing a stable domain name service (DNS) name for your applications, decoupling them from instance IP addresses.
External search with AlloyDB now supports OpenSearch in Preview
External search with AlloyDB now supports OpenSearch in Preview . You can use the external_search_fdw extension to connect to an OpenSearch cluster and query its data directly from your database.
Note: IAM group authentication is available in Preview for new AlloyDB clusters
Note: IAM group authentication is available in Preview for new AlloyDB clusters. To enable this feature on an existing cluster, contact your Google Cloud account team. IAM group authentication for AlloyDB is available in Preview for new clusters running PostgreSQL 15 and later.
Transparent query forwarding is now available in Preview for clusters compatible with PostgreSQL 17 and 18
Transparent query forwarding is now available in Preview for clusters compatible with PostgreSQL 17 and 18. With this feature, the primary node in a cluster intercepts read-only queries and selectively forwards them to read pool instances while maintaining read-your-writes consistency.
AlloyDB now supports Best Matching 25 (BM25) indexes for full-text search in Preview
AlloyDB now supports Best Matching 25 (BM25) indexes for full-text search in Preview . You can use the pg_textsearch extension to create BM25 indexes and optimize probabilistic ranking of full-text search. This feature is supported on AlloyDB instances running PostgreSQL 17 or 18. For more information, see Create and manage a BM25 index .
AlloyDB can sync BigQuery tables in preview
BigQuery tables can be synced into AlloyDB once or on a periodic schedule, giving operational analytics low-latency transactional access to data lake data.
AlloyDB integration with BigQuery enters preview
AlloyDB can connect operational and analytical data through real-time lakehouse federation to BigQuery, periodic data synchronization and one-time table syncs, all in preview.
External search with AlloyDB now supports Apache Solr in Preview
External search with AlloyDB now supports Apache Solr in Preview . You can use the external_search_fdw extension to connect to a Solr cluster and query its data directly from your database.