Create a database
The database qube provisions a managed database server in the EU and gives you a connection string. You pick the engine, the size, and the region.
-
Add the database qube
From your project dashboard, click Add qube and pick Database.
-
Pick an engine
- MariaDB 11 for general-purpose relational workloads. Recommended default.
- PostgreSQL 16 for advanced relational workloads (JSON, full-text search, partitioning).
You can run both side by side on the same project if you really want; they are independent qubes.
-
Pick a size
The qube shows three sizes (small, medium, large) with daily prices. Most early-stage projects fit in small.
-
Pick a region
EU regions only. Pick the one closest to your container or your users.
-
Provision
Provisioning takes 60 to 90 seconds (databases are stateful; cold start is slower than stateless qubes). The qube updates the dashboard once the server is reachable.
-
Copy the connection string
Open the database qube on your dashboard. The connection string is shown with a copy button. It includes the host, port, database name, user, and password.
What you get
Section titled “What you get”- A single instance of the engine you picked, in the region you picked.
- Daily automated backups, retained for 7 days, restorable from the dashboard.
- A public endpoint with TLS. The endpoint is rate-limited to your project’s allowlist of IPs (any container qube on the same project is allowlisted automatically).
- Suspension when your prepaid balance hits zero, no data loss; topping up resumes the database.
What you do not get (yet)
Section titled “What you do not get (yet)”- Read replicas. Single-instance only at v1.
- Automatic failover. Manual restore from backup.
- Multi-region. Single region per database.
If you need any of these, the WordPress qube and the SaaS-starter template both ship with single-instance databases sized for early-stage projects; once you outgrow that, contact support to discuss a managed migration.