Managed databases

Provision MySQL, PostgreSQL, or MongoDB with backups, health snapshots, and organization-scoped access from the dashboard.

Creating a database

From Databases, choose the engine and plan tier appropriate for your workload. Credentials are generated for you—store connection strings in environment variables for the projects that should consume them.

Attaching at project creation

The project wizard can create a new database or attach an existing one for compatible runtimes (Node SSR/service, custom Dockerfile, PHP, Laravel). Static-only frontends typically talk to APIs hosted elsewhere—attach databases to the backend project instead.

Backups & retention

The platform schedules backups according to policy; download or restore flows depend on what your organization exposes in UI. Plan retention around compliance needs—never rely on a single region for critical data without separate DR testing.

Preview environments should use isolated databases or scrubbed datasets. Pointing preview builds at production connection strings risks data corruption or leakage.

Studio & operations

Where enabled, open the database studio or metrics views from each database detail page to inspect health history and operational signals—pair with Deployments, logs & analyticsfor full-stack debugging.

Laravel — migrations and queues

Environments & variables