You’ve outgrown the database box.
The PostgreSQL server someone set up two years ago is now running your business. Balta takes over the backups, the patching and the worrying — for a price that fits in a budget.
Example view with sample data.
Sound familiar?
| The situation | With Balta |
|---|---|
| Nobody has ever tested a restore | Automatic restore tests, with results in your dashboard. |
| The person who set it up has moved on | Backups, patching and monitoring handled for you. |
| You’re two major versions behind | Minor updates applied for you, and major upgrades when you choose. |
| The disk is filling up | Dedicated storage you can expand online, without downtime. |
| Nobody knows how much data you’d lose | Your recovery point, shown for every service. |
Moving over
Moving over is standard PostgreSQL.
Dump your database with pg_dump, restore it into Balta with pg_restore, and point your application at the new connection string. During early access, our engineers will help you plan the move and the cut-over.
# 1. Export from your current provider pg_dump --format=custom --no-owner --no-acl \ --dbname "$SOURCE_DATABASE_URL" --file app.dump # 2. Restore into Balta over the direct endpoint pg_restore --no-owner --no-acl --jobs 4 \ --dbname "$BALTA_DIRECT_URL" app.dump
Commitments, in writing.
Every figure here is part of our SLA or our published plans. The reliability figures are measured continuously, per service, and shown in your dashboard.
Backed by service credits — including when the outage is our provider's fault.
Monitored continuously and shown for every service.
Written independently to Germany and to France, so a problem in one country can't reach both.
One flat price. No compute units, no egress fees.