Google Puts Spanner Omni in Preview, Letting Enterprises Run Its Distributed Database Outside Its Own Cloud
Google announced a downloadable edition of Cloud Spanner that runs on-premises, on rival clouds, or on a laptop, dismantling a dependency on proprietary infrastructure that its engineers once thought impossible to remove.
Overview
Google unveiled Spanner Omni at Cloud Next ‘26 in Las Vegas on April 22, 2026, as part of a wave of 260 announcements at the conference. The product is a downloadable edition of Cloud Spanner — Google’s globally distributed, strongly consistent database — that can run on virtual machines, Linux containers, and Kubernetes clusters, whether on-premises, across rival cloud platforms, or on a developer’s laptop. The Developer Edition is now available in preview.
What It Is and What Changed
Cloud Spanner has long been architected around proprietary Google infrastructure. Two components in particular made it inseparable from Google Cloud: Colossus, Google’s internal distributed file system, and TrueTime, a time-synchronization service backed by GPS receivers and atomic clocks that underpins Spanner’s external consistency guarantees.
According to the official Google Cloud Blog post authored by Wenzhe Cao, Group Product Manager, and Chris Taylor, Google Fellow, the Spanner Omni team replaced both components. A new software layer now “writes to attached local file systems and makes them available across the network to other nodes,” with automatic shard splitting and rebalancing to distribute storage across servers. The post notes that “while Spanner Omni’s file layer isn’t Colossus, it’s a sufficient stand-in to allow Spanner Omni to perform comparably to the Spanner managed service for most workloads.”
For timekeeping, the team developed “a software-based TrueTime alternative, which — like TrueTime in Google Cloud — provides highly reliable, error-bounded time synchronization across servers in a Spanner Omni deployment.” The announcement says the software uses “this flexibility to provide timekeeping across diverse and heterogeneous environments without limiting Spanner’s availability or performance.” Core Spanner technologies — Paxos consensus, automatic sharding, and synchronous replication — remain intact.
Andi Gutmans, General Manager and Vice-President for Data Cloud at Google, acknowledged the scale of the engineering challenge in comments reported by Computer Weekly: “Three to four years ago, no one, including us, believed we could disconnect Spanner from Google Cloud.”
Deployment Options and Configurations
The official Google Cloud documentation describes four deployment topologies. A single-server configuration is suited to local development but is prone to downtime during upgrades. A single-zone topology requires a minimum of three servers. Multi-zone deployments require at least three zones with one or more servers each, with three servers per zone recommended for enhanced availability. Multi-cluster configurations distribute across multiple clusters and require three or more zones with three or more servers per zone for optimal resilience.
Supported platforms include Red Hat Enterprise Linux 9 and Ubuntu 22 for on-premises deployments, as well as Google Kubernetes Engine and Amazon EKS for containerized environments. The documentation lists minimum on-premises requirements of 4 GB of RAM per vCPU and 20 or more gigabytes of disk storage. Spanner Omni supports GoogleSQL, PostgreSQL, and Spanner Graph Language dialects.
Preview Limitations
The Developer Edition released in preview carries several restrictions. Enterprise security features and TLS encryption are not supported. Per the documentation, data writing stops 90 days after a deployment is created. Backups and restores are unavailable. A Commercial Edition offering full enterprise security and support is available through early access by contacting Google.
Who It Is For
The Google Cloud Blog outlines three intended use patterns: hybrid and multicloud resilience architectures where Spanner Omni operates as a secondary tier for disaster recovery; unified application stacks where teams want to develop against a consistent database interface regardless of environment; and on-premises modernization for organizations that need to run AI-enabled workloads on existing data center hardware.
Gutmans cited on-premises fraud detection as a primary use case in regulated industries. He also drew a distinction between deployment strategies in comments to Computer Weekly: “It’s very important to note that the term ‘cross-cloud’ is distinct from ‘multicloud’; those who refer to multicloud are just talking about multiple single-cloud environments.”
Mercado Libre, which operates Fury, an internal developer gateway offering a NewSQL service built on Spanner, described its interest in the new product. Diego Oscar Narducci, Senior Technical Manager at Mercado Libre, said in the announcement post: “Spanner Omni enables true cross-cloud resilience, providing a robust and differentiated strategy that would be significantly more complex to implement with other cloud providers.”
What We Don’t Know
Google has not disclosed pricing for the Commercial Edition. The company has not provided a timeline for when enterprise security features or backup capabilities will be added to the preview. The long-term performance characteristics of the software-based TrueTime substitute relative to the atomic-clock-backed original in high-latency or high-contention scenarios have not been independently benchmarked.
Analyst reaction to the broader Agentic Data Cloud launch that Spanner Omni is part of was cautious. Moutusi Sau of Gartner noted, per Computer Weekly, that “without disciplined governance, enterprises risk scaling ambiguity and mistrust faster than agents scale productivity.”