Browse docs
Create and connect to a database
Run PostgreSQL, MySQL, MongoDB or Redis, find the connection details, and restrict who can connect.
Updated
BitQate runs PostgreSQL, MySQL, MongoDB and Redis as managed containers. Each gets a generated password, persistent storage and its own management tabs in the dashboard.
Create it
- Go to New deployment and pick Containers.
- Under Popular images, choose PostgreSQL (
postgres:16), MySQL (mysql:8), MongoDB (mongo:7) or Redis (redis:7). You can switch to another tag of the same image if you need a different version. - Pick Resources and a Location, then press and hold Hold to deploy container.
You don't need to set passwords or volume mounts:
- A strong password is generated automatically. PostgreSQL also requires
scram-sha-256authentication. - The data directory is stored on the persistent volume, so it survives restarts.
- The database listens on your server's assigned port.
Find the connection details
Open the server and go to its Databases tab (Keys for Redis). It shows the host, port, user, password and default database, plus a ready-made connection string. Reveal it, then copy it. Rotate password generates a new one; update your apps afterwards.
Connecting from a terminal:
psql "postgresql://USER:PASSWORD@HOST:PORT/DATABASE"
mysql -h HOST -P PORT -u USER -p
mongosh "mongodb://USER:PASSWORD@HOST:PORT/?authSource=admin"
redis-cli -u "redis://:PASSWORD@HOST:PORT"
Most frameworks accept the connection string directly, usually through a DATABASE_URL environment variable.
Manage it from the dashboard
Secure it
- Restrict access by IP. On the Access tab, the allowlist starts as Open to all IPs. Add the addresses that need to connect (your app server, your office) as single IPs or CIDR ranges such as
203.0.113.0/24. The tab shows your current IP for convenience. The status then changes to Restricted. - Give each app its own user with only the rights it needs, instead of using the admin user everywhere. Use Roles & Users (PostgreSQL) or Users (MySQL, MongoDB).
- Keep the connection string secret. Store it in environment variables, not in your repository.
- Take backups before migrations and upgrades.
Still stuck?
Our team can look at your specific setup.