What this means
What this means
Your app gets its own PostgreSQL 17 database on our managed cluster, with its own login that can reach that database and nothing else. You also get a console in the dashboard for looking at your data, and nightly backups.
Before you start
Before you start
You need an app already deployed on CM Cloud. Know whether your framework runs migrations for you (Django, Rails, Laravel and Spring all do) — the database arrives empty and your migrations create the tables.
Step-by-step guidance
Step-by-step guidance
- Open your app in the portal and choose Open database.
- Select Create database. It takes a few seconds.
- Open the Connection tab and select Show connection details.
- Copy the DATABASE_URL into your app's environment variables.
- Redeploy your app so it picks the variable up.
- Run your migrations, then check the Tables tab — your tables should be listed.
What CM Cloud support will review
What CM Cloud support will review
Support can confirm the database was created, that the connection string reached your app's environment, and whether your storage tier suits what you are storing.
What is not automated yet
What is not automated yet
No tables are created for you. No data is copied from PocketBase — moving an app from PocketBase to Postgres is a separate priced service, because PocketBase is your app's whole backend rather than just its database, and the application has to be changed.
Safety note
Safety note
Creating a database does not touch your application. Nothing reads or writes it until you put the connection string into your app and redeploy, so you can create it and look around first.
Safe next action
Safe next action
Create the database, copy the connection string into your app's environment variables, and redeploy. Then open the Tables tab to confirm your migrations ran.