Databases
Managed databases provisioned inside your cluster. One click, zero config.
Supported engines
Full-featured relational database. Best for most applications — structured data, transactions, and complex queries.
In-memory key-value store. Use for caching, sessions, rate limiting, and pub/sub messaging.
Document database. Ideal for flexible schemas, rapid prototyping, and JSON-heavy workloads.
Provisioning
From the dashboard, navigate to Databases and click New Database. Choose an engine, give it a name, and click Create. Launchmatic deploys a StatefulSet with persistent storage in your project namespace.
Databases are only accessible from within the cluster — they are not exposed to the public internet.
Connection strings
When you provision a database, the connection URL is automatically available as an environment variable in any service in the same project. The variable name follows the pattern:
DATABASE_URL=postgresql://user:pass@my-db-postgresql:5432/mydb REDIS_URL=redis://my-cache-redis:6379 MONGODB_URL=mongodb://user:pass@my-mongo-mongodb:27017/mydb
Persistence & backups
All databases use Kubernetes PersistentVolumeClaims with the default storage class. Data persists across pod restarts. For production workloads on GCP, consider using Cloud SQL via the cloudSqlProxy Helm value for managed backups, HA, and point-in-time recovery.
Deleting a database
Deleting a database permanently removes the StatefulSet and its persistent volume. This action is irreversible — all data will be lost. Export your data before deleting if needed.