Dashboard
Home/Managed Postgres

Postgres
you don’t
have to babysit.

Production-grade Postgres clusters in one command. We handle backups, restores and standby failover — you get a connection string and ship.

~/my-app — simplifyd
$ edge service create --name orders \
--type postgres --storage 20
› Provisioning Postgres cluster…
› Scheduling automated backups
› Attaching to project network
✔ Database ready

# Connection string
postgres://app:•••@orders.db.
simplifyd.com:5432/orders

# Injected into your services
# as $DATABASE_URL
✔ Ready to connect
Latest stable
Postgres versions
Point in time
Restore granularity
Automatic
Standby failover

Capabilities

The boring parts.
Handled.

Everything you’d build yourself the first time and regret the second time — done, tested, and metered like everything else on Simplifyd.

Automated backups
Scheduled base backups plus continuous WAL archiving, to a bucket you nominate — ours or S3, Azure or GCS. You set the schedule and the retention window.
Point-in-time recovery
Restore a new cluster to any moment within your retention window — by timestamp, transaction ID, or the latest consistent state.
Standby failover
Optional hot standby kept in sync with the primary. If the primary fails, traffic moves to the standby automatically.
Replicas
Scale read traffic by adding replicas to your cluster. Continuously streamed from the primary.
Private networking
Clusters live on your project’s private network by default. No public exposure unless you flip a flag.
Multiple databases & roles
Declare extra databases and login roles per cluster. Passwords are stored as encrypted secrets and rotated on demand.

From your app

Just a
connection string.

Your cluster is reachable from every service in the project over the private network. Set the connection string as a variable — we store it encrypted — and standard Postgres tooling just works. No proxies, no special drivers.

Wire it into
a service.

Read the cluster’s host and credentials, then set them as a variable on the service that needs them. Variables are encrypted at rest with your project key and injected into the container at deploy time.

Switching from your local Postgres is a one-line change in your env file. Your queries don’t care which side of the wire they’re on.

$ edge service get orders
› host orders.cloud-instances
› user app · db orders

$ edge variables set --service api \
DATABASE_URL='postgres://app:•••@orders…'
✔ Variable set on api

# in your code:
const pg = require('pg');
const db = new pg.Pool({
connectionString:
process.env.DATABASE_URL,
});

# that’s the whole integration.

Pricing

Per second.
Like everything
else.

Same model as the rest of Simplifyd — pay for the CPU, RAM and storage your cluster actually consumes, per second. No tiers, no minimums.

vCPU
Burstable or dedicated cores. Same per-second compute rate as your services.
₦0.0096 / vCPU / s
Memory
Allocate what your working set needs and no more.
₦0.0048 / GB / s
Storage
SSD-backed volumes. Includes write-ahead logs.
₦0.0002 / GB / s
Standby
Adds a hot standby. Billed at primary’s compute + storage rates.
2× primary

FAQ

Common questions.

Can I run my own backup tooling?
Yes. You can run a standard pg_dump against your cluster at any time. Backups and WAL archiving go to a bucket you own and hold the credentials for, so the archive is yours to read directly if you’d rather build your own restore flow.
Which Postgres versions are supported?
We track the actively supported upstream major versions. New clusters default to the latest stable release; existing clusters keep their pinned version until you choose to upgrade.
Can I create more than one database in a cluster?
Yes. Declare extra databases and login roles on the cluster; we provision them on first reconcile and keep their state in sync with what you’ve configured.
Can I migrate from another provider?
A new cluster can bootstrap from an existing WAL archive in object storage, recovering to any point in its window. If what you have is a dump rather than an archive, create the cluster first and load it with pg_restore over the connection string — the usual way.

Fast deploys.
#Zerodata access.

Install the CLI, run one command, and your app is live on Simplifyd’s infrastructure — the meter only ticks while it’s running.