← Directory

AlloyDB Omni

AlloyDB Omni is a portable, PostgreSQL-compatible relational database that runs in your data center, on your laptop, at the edge, or in any cloud, giving…

  • Tools & Utilities
AlloyDB Omni is a portable, PostgreSQL-compatible relational database that runs in your data center, on your laptop, at the edge, or in any cloud, giving teams a managed-database-like experience.

Platform availability

Available on 0 of 6 install platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

38/100 Low

Maintained
69last commit 112 days ago
Popular
2110 GitHub stars
Easy to install
100 install platforms, Docker image
Light to run
208 GB minimum RAM, runs on ARM
How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

GitHub stars
10
Open issues
8
Last commit
2026-06-19
Latest release
v1.1.1
License
Apache-2.0
Activity
stale

Checked 11 days ago - source: GitHub (GoogleCloudPlatform/alloydb-omni-samples)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 11 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Container quickstart Start from the container quickstart for Debian or Ubuntu, and check the hardware requirements before deployment. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I deploy AlloyDB Omni using Kubernetes?

Use the provided Helm charts and ArgoCD configurations to install the operator and database workloads. You can also apply the sample base v1_dbcluster manifest to deploy a minimal database once the operator is running.

What backup and recovery options are available?

You can schedule automated backup plans, push backups to Google Cloud Storage, trigger manual backups, and perform point-in-time recovery clones.

Does the Kubernetes setup support replication and failover?

Yes, the samples show how to configure upstream and downstream replication across clusters. They also cover graceful switchovers and forced failovers for disaster recovery.

What secret configuration change is required for production deployments?

The sample minimal database can be deployed quickly, but you must edit the secret configuration before deploying into production.

Answers sourced from github.com

Community

Collected 5 days ago - public community threads