The Databases marketplace offers ready-made templates for popular database engines, with persistent storage, health checks, resource limits and generated passwords kept in an encrypted vault. Your running databases are under My databases.
Deploy a database
- Open Databases → Marketplace and choose an engine.
- Basics — pick the version, an instance name, the server, and the database and administrator names. Choose the Development or Production profile.
- Resources & access — set the port, memory, CPU and storage, and whether the database is reachable only from the server or from the network.
- Backups — choose a schedule and how long to keep backups.
- Review & deploy — check the summary and deploy.
- Development profile — restarts unless stopped, with no backups unless you schedule them.
- Production profile — always restarts, reserves memory, uses stricter health checks and turns scheduled backups on. Your production deployment policy, such as approvals, applies.
Local only binds the database to 127.0.0.1 on the server, so it is reachable only from that machine or through an SSH tunnel. Remote makes it reachable from any network that can reach the server — put a firewall in front of it.
Credentials
Open a database to see its connection details and credentials. You can:
- Reveal or copy a password. Clear your clipboard when you are done.
- Download a credentials file. Each credential version can be downloaded once, so save it in a password manager.
- Rotate a password. Depending on the engine this is done live or with a brief restart; clients must switch to the new value.
- Issue a temporary login — a read-only user that is removed automatically when it expires, after between 1 hour and 30 days.
- Share a credential with other users, optionally until a set date.
Change or remove a database
Change configuration adjusts the image version within the same major version, memory, CPUs and planned storage. Remove deletes the database containers and their stored credentials but keeps named volumes and backup history.