PostgreSQL
This page documents how a PostgreSQL database behaves on Runsite: which major versions you can pick, how storage and the lifecycle work, and which of the two connection URLs — internal or external — to use from where.
The server, OS and minor upgrades are handled by the platform; you work with the database itself.
Looking for plans or pricing?
Plans, specs, free-tier limits and pricing are not documented here — they live on the managed PostgreSQL hosting page. This section covers how the database works once it is running.
Supported versions
Section titled “Supported versions”| Version | Notes |
|---|---|
| 14 | Older — pick if you have legacy compatibility needs. |
| 15 | Standard. |
| 16 | Default. Recommended for new databases. |
| 17 | Latest. |
Pick the major version when you create the database. Minor updates are applied automatically during platform maintenance.
Creating a database
Section titled “Creating a database”From the dashboard: pick a project, choose the major version and storage size, hit create. Provisioning takes a few seconds.
When the database is ready, the dashboard shows the credentials and both connection URLs. Copy them now — the password is shown once and cannot be retrieved later (you can only reset it).
Storage
Section titled “Storage”| Setting | Description |
|---|---|
| Storage size | How many GB the volume gets at creation. |
| Storage autoscaling | Optional toggle. When usage approaches the limit, Runsite grows the volume automatically — no downtime, no manual action. |
Lifecycle
Section titled “Lifecycle”| Action | What it does |
|---|---|
| Start | Bring a stopped database back online. Data is preserved. |
| Stop | Shut the database down. Compute is released; storage and data are kept. |
| Delete | Remove the database permanently. There is no undo — make a backup first. |
Can I change the PostgreSQL version after creating the database?
Section titled “Can I change the PostgreSQL version after creating the database?”No. The major version is fixed at creation. To move to a newer version, create a new database on that version and migrate your data across.
Should I use the internal or external connection URL?
Section titled “Should I use the internal or external connection URL?”Use the internal URL from other Runsite services in the same project — it’s faster and never leaves the platform. Use the external URL from anywhere else (your laptop, CI, third-party tools); it’s TLS-encrypted. See Connecting.
What happens to my data when I stop the database?
Section titled “What happens to my data when I stop the database?”It’s preserved. Stopping releases compute but keeps storage and data. Click Start to bring it back online with everything intact.
Can I recover a database after deleting it?
Section titled “Can I recover a database after deleting it?”No. Delete is permanent and there’s no undo. Take a backup before deleting anything you might need.
I lost my database password — can I retrieve it?
Section titled “I lost my database password — can I retrieve it?”No. The password is shown once at creation and can’t be retrieved later. You can reset it from the dashboard, which issues a new one.
Does storage grow on its own?
Section titled “Does storage grow on its own?”Only if you enable storage autoscaling. With it on, Runsite grows the volume automatically as usage nears the limit, with no downtime.
Where to next
Section titled “Where to next”- Connecting — internal vs external URLs and how to use them.
- Dashboard — what each tab does.
- Backups — automatic schedule, on-demand backups and restore.
Need a key-value store?
If you want a fast in-memory cache, queue, or pub/sub channel instead of a relational database, use Redis.