Dashboard
Home/Managed Postgres

◆ 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
$ simplifyd postgres create --name orders
› 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 full backups shipped to encrypted object storage on a cadence and retention window you control.
▲
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

One env var.
That’s it.

Bind a Postgres cluster to a service and Simplifyd injects $DATABASE_URL into its environment. Standard Postgres tooling just works — no proxies, no special drivers.

Attach a database
to a service.

Bind any Postgres cluster to any service in your project. We provision a role for that service, store its password as an encrypted secret, and inject the connection string 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.

$ simplifyd postgres attach orders --service api
› Creating role api_orders
› Granting CONNECT, USAGE
✔ DATABASE_URL injected into 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.006 / vCPU / s
Memory
Allocate what your working set needs and no more.
₦0.003 / GB / s
Storage
SSD-backed volumes. Includes write-ahead logs.
₦0.0001 / 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, and the write-ahead-log archive is available in object storage 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?
Yes. You can restore from a pg_dump at create time, or stream changes from a Postgres 14+ source using logical replication until you’re ready to cut over.

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.