Managed Databases

​

Supported Engines

​

How It Works

1. Uncloud stores the configuration in SQLite
2. A Kubernetes StatefulSet (or operator CR for PostgreSQL) is created
3. Persistent storage is provisioned via PVCs
4. Connection credentials are generated and stored securely
5. The database becomes accessible within the project’s network

​

Database Lifecycle

​

Plans

​

Connection Details

GET /api/v1/databases/{id}/credentials

{
  "host": "main-pg.production.svc.cluster.local",
  "port": 5432,
  "username": "app_user",
  "password": "generated-secure-password",
  "database": "main_pg",
  "connection_string": "postgresql://app_user:pass@host:5432/main_pg"
}

​

Features

• Automatic provisioning — Databases are ready in seconds
• Persistent storage — Data survives pod restarts
• In-cluster networking — Accessible from any resource in the same project
• Connection pooling — Built-in for PostgreSQL (via CloudNativePG)
• Credential rotation — Generate new passwords without downtime

​

PostgreSQL with CloudNativePG

• High Availability — Automatic failover with streaming replication
• Point-in-Time Recovery — Restore to any second
• Backup integration — Automated WAL archiving
• Connection pooling — Built-in PgBouncer integration