How it works

Managed databases and connection details

Use the database already linked to the project; do not install PostgreSQL or MySQL inside the application container. Managed data infrastructure is separate from app replicas. Add a database only when the project needs one and does not already have it. Available engines: PostgreSQL, MySQL, MariaDB, MongoDB and Redis. Automatic backups exist for PostgreSQL only, and only on plans with backup (Pro 7 days, Enterprise 30 days; Hobby has none).

When a database is linked from the project, its encrypted connection variable is added automatically and the app is redeployed to receive it. Use the supplied variable and private host. Table creation and schema migrations remain part of your application deployment process.

Database high availability requires database replication and failover in the configured data service. Application replicas do not create database replicas. Reconnect after a failover; replication does not replace backups or undo accidental deletion. Check the conditions of the service.

Public access is optional and should only be enabled when needed for an external SQL client. Before deleting a database, export any data you need to keep. Do not delete it to troubleshoot a connection.