Plans and pricing
Is there a free plan?
No. The free tier was replaced by the Dev plan, a small paid database for development and testing: 0.5 shared vCPU, 1 GB RAM and 5 GB of storage on a single server. It needs a card like every plan, you can have up to 2 Dev databases per account, and it has no SLA. The price is on the pricing page.
What is the difference between high-availability and single-node plans?
A high-availability plan runs your database on two servers in different sites of the same region: a primary and a standby that takes over automatically if the primary's server fails. A single-node plan has the same size, backups and 7-day restore on one server, for 30% less. If that server fails, the database is restored from backup on another server: it is down while that happens and can lose up to about the last minute of writes. See High availability and replication.
Can I change plans without downtime?
Yes, between high-availability plans. Each server is rebuilt at the new size from backups and then takes over, so the database stays online and the connection string does not change; open connections are closed at each switchover, so your app should reconnect. To move to a plan with less storage, your data must be under 85% of the new plan's storage. Dev and single-node databases change plan by restoring into a new database on the plan you want.
How does billing work?
Each database is billed monthly in advance, in euros, through Stripe. Billing is prorated to the day when you create, resize or delete a database, and a day is billed at the largest plan the database had that day. Prices exclude VAT. Storage, backups, 7-day restore and traffic are included in the plan price, with no egress fees.
What happens to my bill if I delete a database mid-month?
Billing for that database stops. The days from the next day on are credited to your next invoice or your account balance.
Is there a money-back guarantee?
Yes. If you are not satisfied in the first 15 days after your first payment, tell us and we refund what you paid. The details are in the Terms of Service.
How do I cancel?
Delete your databases from the dashboard or the API: billing stops with the last one. The account owner can also close the account in Settings, which deletes every database and ends all sessions and API keys. Backups of deleted databases are kept for 7 days, then deleted permanently.
Availability and replication
Is my database highly available?
On high-availability plans, yes: a synchronous standby runs in a second site of the same region and failover is automatic, around the clock. Your hostname stays the same after a failover, because every server routes connections to the current primary. Dev and single-node plans run on one server.
What does synchronous vs asynchronous replication mean for my writes?
On high-availability plans you choose how each commit is copied to the standby. Synchronous (the default) waits until the standby has the commit on disk, so a failover loses no committed data. Write-synchronous waits until the standby has received it: faster commits, and data is lost only if both servers fail at the same moment. Asynchronous does not wait: fastest, but a failover can lose the last commits.
What uptime do you commit to?
99% monthly uptime for every paid database, high-availability and single-node, backed by service credits. Dev databases are not covered. Each database's page shows its measured uptime this month; the full terms are in the SLA.
Do I get a read replica?
Every high-availability database has a read-only endpoint on the same hostname and credentials, on a second port. It reads from the standby, which can be slightly behind the primary, and falls back to the primary if the standby is unavailable. Extra replicas beyond the standby are not offered yet.
Backups and restore
How are backups done?
Every change is archived continuously and a full backup runs daily. Backups are encrypted before they leave the server, with a separate key per database, and stored in the database's region. They are included in every plan, and we run automated restore tests every week.
How far back can I restore?
To any second of the last 7 days, starting one minute after the database's first backup. A restore creates a new database on the same plan, in the same region, with a new hostname and port; your original keeps running. See Backups and point-in-time restore.
Can I restore a database I deleted?
Yes, for 7 days after you delete it. After that its backups are deleted permanently and it cannot be restored. To avoid accidents, turn on deletion protection: a database labelled "production" starts with it on.
Versions, regions and data
Which PostgreSQL versions do you support?
PostgreSQL 17 is the default. Where PostgreSQL 18 is offered, you can pick it when you create a database; the create form and GET /api/v1/engines list the versions available.
Where is my data stored?
You pick a region for each database: the EU, the US or Asia. The database, its standby and its backups stay in that region, never on another continent. The companies and locations involved are listed on the Sub-processors page. See Regions and data residency.
Can I keep my data in the EU?
Yes. Databases in the EU region, and their backups, stay in the EU. Personal data in your databases is covered by our Data Processing Agreement under article 28 GDPR.
How do I choose a region?
On the create page, enter your server's public IP address and our servers in each region ping it, so you see the round-trip time before you choose. Your server must answer ICMP echo (ping) for this to work.
Security and access
How do I connect securely?
Every connection string uses TLS with sslmode=verify-full, which checks that the certificate belongs to your database's hostname. The certificate comes from a public certificate authority, so your system's trusted authorities are enough: with psql and other libpq tools (version 16 or later), add sslrootcert=system. See Security.
Can I restrict access by IP address?
Yes. Each database has an IP allowlist of up to 50 addresses or CIDR ranges, set in the dashboard or the API. An empty list allows all addresses.
Do I get superuser access?
No. You get an owner role on the app database, without superuser or the right to create other databases. As the owner of app you can create schemas, tables and indexes in it.
What happens when my storage is full?
The database becomes read-only: reads keep working and writes are refused. You get emails at 85% and 95% of the plan's storage and when it becomes read-only. Free space or move to a bigger plan, and writes come back by themselves; see When your database is full.
Will you tell me when something goes wrong?
Yes. You get an email when a database has been down for 2 minutes, when storage reaches 85% and 95%, and when it becomes read-only. You can also send these alerts to Slack, Discord or your own webhook, and the status page shows each region's health.
API
Do you have an API?
Yes. A REST API at /api/v1 lets you create, resize, restore and delete databases, change the allowlist and replication mode, and read metrics and events. You authenticate with API keys (Authorization: Bearer dbk_…), with full or read-only access. Creating a database accepts an Idempotency-Key header, so a retried request never makes a second database.