Docs — PostgresRun

Quickstart

One command provisions a fully-managed PostgreSQL 17 database with backups, encryption and pooling already on. Pick a tier and a region (US or EU) and you'll have a connection string in about two minutes.

terminal

$ postgresrun create --name app --tier pro --region us-east
# provisioning on local NVMe…
✓ database app ready in 1m 48s
# now connect with any Postgres client
$ psql postgresql://app:••••••@db.postgresrun.com:5432/main

Connecting

Every database exposes a standard PostgreSQL connection string — connect with psql or any driver. TLS is required on every connection; there's nothing to switch on.

Point latency-sensitive direct connections at port 5432. For serverless and high-concurrency apps, use the built-in PgBouncer pooled endpoint on port 6432 so you never exhaust backend connections.

.env

# direct connection
DATABASE_URL=postgresql://app:••••••@db.postgresrun.com:5432/main?sslmode=require
# pooled (PgBouncer) — serverless / high concurrency
DATABASE_URL=postgresql://app:••••••@db.postgresrun.com:6432/main?sslmode=require

CLI

The postgresrun binary drives everything the dashboard does — scriptable, nothing click-only. Install it from your package manager or grab the static binary, then sign in once with postgresrun login.

common commands

$ postgresrun create --name app --tier pro --region us-east
$ postgresrun list
$ postgresrun fork app --name app-staging
$ postgresrun backups list app
$ postgresrun restore app --to '2026-06-10 14:00:00'
$ postgresrun scale app --tier scale

Backups & PITR

We take daily off-site, encrypted base backups and continuously archive write-ahead logs to object storage. That combination lets you restore to any second within your retention window — not just last night's dump.

Restores land in a fresh database by default, so you can inspect the result before cutting over. Recover from a bad migration or an accidental DELETE in minutes, self-serve.

point-in-time recovery

$ postgresrun restore app --to '2026-06-10 14:00:00'
# restores to a fresh database — verify before you cut over
✓ restored to app-restore-1406

Scaling & upgrades

Resize CPU, RAM and disk with one click as you grow — DEV and BUILDER for early projects, PRO at 8 GB for production, SCALE when traffic climbs. Add read replicas to spread read traffic and serve data closer to your users.

Major-version upgrades run online, handled without the downtime drama. Need 32–64 GB, high availability or a dedicated server? Talk to us and we'll size it with you.

Extensions

40+ extensions are available, enabled in one click from the dashboard — no support ticket required.

pgvectorAI PostGIS pgcrypto pg_stat_statements uuid-ossp hstore pg_trgm citext postgres_fdw + 30 more, one click

Open your database in the dashboard, flip on what you need, and it's live on the next connection — no restart, no waiting.

Migrating in

Migration is free and, if you want it, fully assisted. We plan and run the move with you from RDS, Heroku, Supabase or self-hosted Postgres, with minimal downtime.

Tell us what you're running and we'll plan it. Weighing your options first? See how we stack up against AWS RDS, Supabase, Aiven and DigitalOcean.

API & SDKs

Everything in the CLI is backed by a clean REST API, so you can create, fork, scale and back up databases straight from your own tooling and CI. Language SDKs wrap it with typed clients for common stacks.

Want API keys or early access to an SDK for your language? Get in touch and we'll set you up.

Documentation.