​
Managed Databases

Uncloud provides managed database instances with automated provisioning, backups, and connection management. Supported engines include PostgreSQL, MySQL, Redis, and MongoDB.

​
Supported Engines

EngineOperatorUse Case
PostgreSQLCloudNativePGRelational data, ACID transactions
MySQLStatefulSetWeb applications, WordPress
RedisStatefulSetCaching, sessions, queues
MongoDBStatefulSetDocument storage, flexible schemas

​
How It Works

When you create a managed database:
  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

PlanSpecsStorage
db-s-1vcpu-1gb1 vCPU, 1 GB RAM10 GB
db-s-2vcpu-4gb2 vCPU, 4 GB RAM50 GB
db-s-4vcpu-8gb-ha4 vCPU, 8 GB RAM, HA100 GB

​
Connection Details

Retrieve connection credentials via the API: 
GET /api/v1/databases/{id}/credentials
Response: 
{
  "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

PostgreSQL databases use the CloudNativePG operator for advanced features:
  • 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