Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Google Spanner Omni became generally available on September 30, 2026. It brings Spanner to customer-managed infrastructure by replacing dependencies on Google’s atomic-clock timekeeping and Colossus storage with software-based alternatives. Omni still needs suitable customer hardware and careful operations; it is not the same as using fully managed Spanner on Google Cloud.

What GA means for Spanner Omni

Google’s GA announcement describes Spanner Omni as ready for production workloads on premises or in other clouds. The corresponding long-term support release is 2026.r4-lts; Google says that release receives security fixes for up to one year. Those details apply to the September 30, 2026 launch and release, and may change with later releases. See Google Cloud’s GA announcement and the Spanner release notes.

Google also reported more than 2 million downloads since launch. That is the company’s figure in its GA post; it does not specify whether downloads represent unique users or production deployments.

How Omni handles time without atomic clocks

Managed Spanner on Google Cloud uses TrueTime, which relies on time servers synchronized with physical GPS receivers and atomic clocks. Omni cannot assume those Google-operated components are present in a customer data center or another cloud.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Instead, Omni provides a software-defined TrueTime API. Google’s documentation describes a primary time server and host clients that calculate bounded time intervals using network latency and clock drift. Spanner can account for the uncertainty in those intervals to preserve external consistency—the guarantee that transactions appear in an order consistent with their real-time ordering. This is Google’s description of the design, not an independent performance assessment. Details are in the TrueTime and external consistency documentation and the Spanner Omni FAQ.

How Omni provides storage without Colossus

Colossus is Google’s distributed file system and is not available for customers to run in their own environments. Omni replaces that dependency with a software storage abstraction layered over customer-provided storage. It can use local block devices or SAN storage formatted with standard filesystems; Google recommends ext4. The software makes storage available across nodes and handles shard splitting and rebalancing.

This is not storage without disks or filesystems. Customers still provide and operate the underlying storage, and its capacity and interface must suit the deployment. Google explains the design in its Spanner Omni introduction and FAQ.

Where Omni runs and what it supports

Google documents deployment on premises, in public clouds, across clouds, in hybrid or air-gapped environments, and on a laptop for development. Supported environments include Linux and macOS, virtual machines, containers, Kubernetes, Google Cloud, AWS EKS and EC2, and local development. Omni supports relational, graph, vector, key-value, full-text search, and operational analytics capabilities, with GoogleSQL, PostgreSQL, and Spanner Graph Language. Consult the Spanner Omni overview for current platform details.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Published system recommendations

Google’s overview gives recommendations, not one universal minimum for every production architecture:

  • On-premises Linux: RHEL 9 or Ubuntu 22, 4 GB RAM per vCPU, and at least 20 GB of disk.
  • Cloud VMs or Kubernetes pods: 4 vCPUs and 16 GB RAM.
  • Developer machines: Mac with M1, M2, or M3 and 4 GB RAM plus 10 GB of disk.

Google recommends dedicated SSD storage formatted with ext4 for server deployments. Confirm current requirements and check that the storage connection, available capacity, and host environment fit your design.

Availability depends on topology

Google documents multi-zone and multi-cluster architectures. Its overview recommends at least three zones for a multi-zone deployment, and three zones across two or more clusters for a multi-cluster deployment; server counts also depend on the chosen topology. A single-zone deployment has lower availability targets. Merely installing Omni on several machines does not, by itself, create a highly available system.

What changes compared with managed Spanner

Omni shares Spanner’s database engine and core techniques, which Google identifies as Paxos consensus, automatic sharding, synchronous replication, and strong consistency. The major difference is who provides and operates the infrastructure.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Area Spanner Omni Managed Spanner on Google Cloud
Infrastructure and operations Customer provides and manages the environment, including infrastructure design, security, upgrades, and monitoring. Google provides the managed service on Google Cloud.
Deployment location On premises, other clouds, hybrid, air-gapped configurations, and local development are documented options. Runs as a Google Cloud service.
Availability commitment Google does not provide an availability SLA for customer-managed Omni infrastructure. Reference architectures can help customers pursue their own availability goals. Omni’s GA announcement does not state managed Spanner’s SLA terms; refer to the applicable Google Cloud service terms.
Google Cloud integrations and feature coverage Some managed-service features that depend on Google Cloud are unavailable, including native integrations with BigQuery, Knowledge Catalog, Gemini Enterprise, and other Google Cloud services. Google says feature gaps remain and are being addressed over time. Includes Google Cloud integrations that are not included in Omni, subject to the service’s current feature set.
Performance comparison No general benchmark establishing equivalent performance for every workload was published in the cited launch material. No general benchmark comparing every workload with Omni was published in the cited launch material.

Google quotes Mercado Libre’s Diego Oscar Narducci, a senior technical manager, saying Omni enables a cross-cloud resilience strategy that would otherwise be significantly more complex. That is a customer testimonial reproduced by Google, not an independent comparative study or a guarantee of resilience for every deployment.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Developer and commercial editions

Google says the developer edition is for non-commercial development and testing. For production or other commercial use, Google directs prospective customers to contact it about a commercial license; the GA announcement points to a Google Cloud account team or consulting. The official pages cited here do not publish a price or specific contract terms. See the Spanner product page.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.