Postgres
Create a managed PostgreSQL database, add databases and users, tune parameters, and resize storage.
A Postgres service is a PostgreSQL database that Simplifyd Cloud runs and maintains for you.
Creating a database
- Click + Add and choose Postgres Database.
- Set the name and the storage size.
- Click Apply in the Apply Changes bar.
The database takes a couple of minutes to come up. While it does, the node shows as pending.
Connecting
Open the service panel → Settings tab → Connection. You get a Connection URL you can paste into a client.
Simplifyd Cloud also sets DATABASE_URL on the service. Any other service in the same environment can pull it in with a reference variable:
DATABASE_URL=${{postgres.DATABASE_URL}}The connection uses the private network, so nothing is exposed to the internet.
Rotating the password
Open the service panel → Settings tab and click Rotate password. A new password is generated and DATABASE_URL is updated.
Services holding the old password keep using it until they are redeployed. Redeploy anything that connects to this database after rotating.
Additional databases and users
A Postgres service starts with one database and one user. You can add more from the service panel → Settings tab → Database Users.
Adding a database
- Click Add database.
- Enter a name — lowercase letters, digits, and underscores.
- Pick an owner from the existing users. The owner gets all privileges on that database.
Adding a user
- Click Add user.
- Enter a username — lowercase letters, digits, and underscores.
- Optionally give the user role memberships, including replication if the user needs to read the change stream. Change-data-capture tools and external replicas need this; ordinary application users do not.
- Click Add user.
The password is shown once, right after the user is created. Copy it before closing the dialog — it cannot be shown again. Users with replication rights are marked with a badge in the list.
You can rotate a user's password or delete a user from the menu on their row.
Resizing storage
Open the service panel → Settings tab and change the Storage value, then apply the change.
Storage can only be increased, never decreased. The maximum is 500 GB.
The resize happens while the database keeps running. Storage is billed at the new size from the moment it applies.
Tuning parameters
Open the service panel → Settings tab → Parameters to change PostgreSQL settings without a restart in most cases. They are grouped by what they affect:
| Group | Example settings | What it changes |
|---|---|---|
| Query timeouts | Statement timeout, lock timeout, idle-in-transaction timeout | How long a single statement or transaction may hold resources before it is cancelled. |
| Per-operation memory | Work memory, maintenance work memory | How much memory a sort, join, or index build may use. |
| Autovacuum | Vacuum and analyze scale factors, cost limit, max workers | How aggressively dead rows are cleaned up. |
| Parallelism | Max parallel workers, max parallel workers per gather, max worker processes | How much of a query the planner may run in parallel. |
| Archiving | Archive timeout, max slot WAL keep size | How much recent history is kept, which affects how far back you can recover. |
Each field validates its format — durations like 30s or 5min, sizes like 64MB or 10GB, fractions between 0 and 1.
Raising memory settings raises how much memory the database uses under load. If you increase work memory a lot, increase the service's memory allocation too, or queries will be killed.
Backups and restore
Postgres services can take continuous backups to a bucket you own, and restore from a backup or from any point in time. See Backup & restore.
Stopping, starting, and restarting
Postgres services have lifecycle controls that other service types do not. See Stopping, starting, and restarting.
Logs
Deployment logs are not available for Postgres services — the database process is managed by the platform. Use the Metrics tab to see load, and the parameters above to change behaviour.
