Databases
Deploy Postgres, MySQL, MongoDB, Redis, or MSSQL on a server, and check their health.
The Databases page manages standalone database engines running alongside your apps — separate from any database a template bundles for itself.
Deploying a database
- Go to Databases → Deploy.
- Pick an engine: Postgres, MySQL, MongoDB, Redis, or MSSQL.
- Pick the target server.
DeployOS deploys it as a container on that server, generates credentials, and stores the password in your OS keychain — never in a plaintext file.
Health checks
Each database on the list shows live health — for Redis this parses the actual INFO output rather than just checking the container is running, so a Redis instance that's up but misbehaving still shows as unhealthy.
Connecting your app to it
Add the database's connection string as an environment variable on the app that needs it — either per-app, or as a global secret if several apps share the same database.
Adopted databases
A database DeployOS discovered on an already-running server (see Adopting an Existing Server) defaults to a deployos user. If the real database actually uses different credentials, set the correct ones from the database's card — this is required for its backups and health checks to work correctly, since DeployOS can't guess a password it never generated.
Moving a database to another server
Use Migrate on the database's card: it dumps the database, transfers the dump to the target server, and restores it there — the same underlying mechanism as Backups, just pointed at a second server instead of your Downloads folder.
Next: Browsing Database Data to explore tables and run queries without leaving the app.