POSTGRESQL // DATABASES
PostgreSQL on Your Cluster
Provision production-grade PostgreSQL on your own cluster with CloudNativePG. High-availability replicas, connection pooling, continuous backups, point-in-time recovery, and declarative configuration — and your data stays in your cluster.
Powered by CloudNativePG
Available versions
FEATURES // POSTGRESQL
Everything PostgreSQL Needs
Edka provisions PostgreSQL on your own cluster and gives you a clean control surface for day-2 operations. The data stays in your cloud account.
Topology & Storage
Run resilient PostgreSQL sized to your workload.
- 1, 3, or 5 instances for high availability
- Dedicated data and optional pg_wal volumes
- Node-pool placement and taint tolerations
- Sizable storage on your cluster's storage classes
Backups & Recovery
Protect stateful data with continuous backups.
- Continuous backups to S3-compatible or Google Cloud Storage
- Point-in-time recovery (PITR)
- Restore to a new database from a backup
- Import from external PostgreSQL via pg_dump / pg_restore
Connection Pooling
Scale connections with a built in pooler.
- CloudNativePG PgBouncer pooler
- Transaction or session pooling modes
- Configurable max client connections and pool size
Declarative Configuration
Manage PostgreSQL objects and tuning as data.
- Declarative roles, databases, and extensions
- pg_hba and pg_ident rules
- Custom PostgreSQL parameters and preload libraries
Secure Connectivity
Reach PostgreSQL from inside or outside the cluster.
- Public LoadBalancer, private MetalLB, or Tailscale exposure
- Bootstrap database, app user, and superuser credentials
- Auto-provisioned connection details
Runs on Your Cluster
Your database, your infrastructure.
- Powered by the in-cluster CloudNativePG operator
- Runs on your own infrastructure
- You keep full control — no hosted database service
Other engines
MySQL 
ClickHouse 
Valkey GET STARTED // NOW
Provision PostgreSQL
Spin up a production PostgreSQL cluster with HA, pooling, and backups — on your own infrastructure.
Which PostgreSQL versions can I deploy with Edka?
Available versions today: 18.3, 18.1, 17.9, 16.13, 15.17. You pick the version when provisioning the runtime.
Can I run PostgreSQL with high availability on my own cluster?
Yes. Choose 1, 3, or 5 instances. CloudNativePG manages replication and automated failover, with optional dedicated pg_wal volumes and node-pool placement.
How are PostgreSQL backups handled?
Continuous backups go to S3-compatible or Google Cloud Storage with point-in-time recovery. You can restore a backup to a new database or import from an external PostgreSQL via pg_dump and pg_restore.
Does Edka support PostgreSQL connection pooling?
Yes. Each runtime can enable the CloudNativePG PgBouncer pooler in transaction or session mode, with configurable max client connections and pool size.
How do apps connect to PostgreSQL?
Connection details are provisioned automatically, with a bootstrap database, app user, and superuser credentials. Expose the runtime through a public LoadBalancer, private MetalLB, or Tailscale.
Where does my PostgreSQL data live?
In your own Kubernetes cluster, on your own infrastructure. There is no hosted database service in between. You keep full control of the runtime and its storage.