Managed databases on blitz.cloud - PostgreSQL, MariaDB, Redis
Create managed PostgreSQL 17, MariaDB 11.4 or Redis (Valkey 8) databases on blitz.cloud, connected to your app automatically and backed up every night.
blitz.cloud offers managed PostgreSQL 17, MariaDB 11.4 and Redis, served by Valkey 8. A database is created for you when an app needs one, or from the Databases page, and its connection details are injected into the app as environment variables. Databases are only reachable from your own apps and are backed up every night.
Engines
| Engine | Version | Port | Connection string |
|---|---|---|---|
| PostgreSQL | 17 | 5432 | postgresql://user:password@host:5432/name |
| MariaDB | 11.4 | 3306 | mysql://user:password@host:3306/name |
| Redis (Valkey) | 8 | 6379 | redis://:password@host:6379/0 |
Redis is served by Valkey, the open-source fork. It speaks the same protocol, so Redis clients and redis:// URLs work unchanged.
MongoDB is not offered. Its licence, the SSPL, is written to stop exactly the kind of hosted offering blitz.cloud would be. An app that needs MongoDB says so before you install it.
Not sure which one to pick? PostgreSQL is the right answer for almost everything.
Creating a database
There are three ways a database gets created:
- You install an App Store app that needs one. Nextcloud gets MariaDB, for example.
- You deploy a Docker image and blitz.cloud detects that it needs one, or you turn on "Needs a database" under Advanced settings in the wizard.
- You create one on the Databases page by choosing an engine and a name, then connect it to an app.
A new database is usually ready in under a minute. The card shows the engine, how much data it holds, which app uses it, and the connection string. The string is hidden until you click Show.
How the app gets the connection details
When an app's variable names are known, blitz.cloud fills them in. Nextcloud gets MYSQL_HOST, MYSQL_DATABASE, MYSQL_USER and MYSQL_PASSWORD, for example. The wizard lists these before it applies anything.
When nothing is known about the app, it gets a single DATABASE_URL with the full connection string. Many tools read that name by convention, among them Rails, Prisma schemas and Django with dj-database-url.
The host in the connection string is a short internal name. It resolves inside your account and nowhere else.
One database per app
Each database belongs to one app, and each app has at most one database. Two apps sharing a database would overwrite each other's tables; two WordPress sites on one database destroy each other's posts. The database is named after the app and renamed along with it.
Network access
Databases have no public address and no open port on the internet. Only apps in your own account can connect to them. That also means you can't connect from your laptop with psql or a GUI client today.
Deleting
A database that an app uses can't be deleted on its own. It goes when the app goes. When you delete the app, after typing its name, you are asked what to do with the database: keep it for another app, or delete it together with every nightly copy. There is no default answer.
Backups
Every running database is copied off our servers every night: 7 nights are kept on the free plan. Restoring a PostgreSQL or MariaDB database to a night is one button. Details in backups.
Limits
The free plan includes one database. Each database reserves 1 GB of storage (Redis: 0.5 GB) and some memory from your pool: 128 MB for PostgreSQL, 192 MB for MariaDB, 64 MB for Redis. See limits.
Database versions are fixed at the versions above. There are no automatic major-version upgrades.
Put your first app online today.
Free plan, no credit card, no waiting list.
Create a free account