Database Management

Create and manage databases inside your managed PostgreSQL or MySQL instance.

Overview

A single database instance can contain multiple databases. This is useful when you want to separate projects, environments (like staging and production), or services while still using the same instance.

Recommended Approach: Keep production and staging databases separate, and create dedicated users per application with least-privilege permissions.

Creating a Database

You can create additional databases directly from the dashboard. This is helpful for new apps, new environments, or isolating data between services.

• Open your database instance in the dashboard
• Go to Databases
• Click + in the Database Card
• Choose a database name (example: myapp_prod)

Naming Tip: Use clear naming like project_env (example: api_prod).

Deleting a Database

You can delete databases you created when they are no longer needed. Deleting a database permanently removes all data inside it.

• Open your database instance → Databases
• Select the database you want to remove
• Click Trash Icon

Deletion is Permanent: Deleting a database removes tables, rows, and schema permanently. If you’re unsure, export or back up the database first.

Important: Do Not Delete Default Databases

Some databases are created automatically by the database engine or by RunxBuild during provisioning. These default databases are used for internal operations and stability.

Best Practices

• Create separate databases for production and staging
• Use dedicated users per app instead of sharing credentials
• Keep database names consistent and easy to identify
• Back up or export before deleting anything important

Migration-Friendly Setup: Most teams keep a single schema per database and run migrations during deploy to keep the structure consistent across environments.