Managed Postgres,
fully accounted for.
Production PostgreSQL on dedicated European hardware. Your CPU and memory are reserved for you and enforced by the kernel, your backups are proven by restoring them on a schedule, and you pay one flat monthly price — without running a single server.
- PostgreSQL 16, 17 and 18
- From €39 a month
- No compute units, no egress fees
Managed Postgres shouldn't be a gamble.
Most teams choose a database platform on features. They find out what they actually bought later — on the invoice, in the latency graph, or in the middle of an incident.
The bill moves with your traffic.
Compute units, per-query pricing and egress fees turn your best month into your biggest surprise. Finance asks for a forecast; you send them a range.
Your latency depends on strangers.
On shared and burstable platforms, another customer's batch job becomes your slow checkout. You can't see it, and you can't fix it.
Nobody has restored the backup.
A job that succeeds every night proves a job ran. Whether your data actually comes back is usually discovered during the incident.
Balta is built to take all three off the table.
Guaranteed resources
Performance that doesn't depend on your neighbours.
Every Balta service runs in its own control group, with hard limits set in the Linux kernel. The memory on your plan is memory no other customer can touch, and a host's CPU allocations never add up to more than the host actually has.
So the performance you measured in staging is the performance you get in production — at three on a Tuesday afternoon, and during someone else’s launch.
- CPU
- 4 vCPU, with a hard ceiling
- Memory
- 8 GiB, enforced by the kernel
- Storage
- 160 GiB dedicated volume on mirrored NVMe
- Connections
- 150, plus a pooled endpoint
- Databases
- 25, all included
Backups & recovery
Backups you've actually seen work.
Every change your database makes is archived as it happens and written to two independent repositories, in two EU countries — neither one a copy of the other. Then Balta does what most platforms skip: it restores your backups into an isolated environment on a schedule, replays every change, starts PostgreSQL and checks it.
| Database size | Full restore test |
|---|---|
| Up to 50 GiB | Every 7 days |
| 50 to 250 GiB | Every 14 days |
| 250 GiB to 1 TiB | Every 30 days |
| Over 1 TiB | Every 60 days, plus a monthly point-in-time test |
A test also runs within 48 hours of your first backup, and after every plan, storage or major version change.
Example view with sample data.
- A full backup weekly, a differential daily, and every change archived in between.
- Encrypted with a key unique to your service. Your database never holds a storage credential.
- Keep 7, 30, 90 or 365 days of history. 30 days is the default.
Point-in-time recovery
Undo the bad migration. To the second.
Someone ran the wrong migration. A customer deleted the wrong records. Pick the exact second before it happened, and Balta restores your data into a new service — while production keeps serving everyone else.
Copy back the rows you need, then delete the copy. No overwritten production, no guesswork about which nightly snapshot is close enough.
- Any second inside your retention window
- A new service with its own connection address
- Rewinding production is a separate, deliberate path
Example view with sample data.
Data browser & SQL editor
Your data, without a desktop client.
Browse schemas and tables, follow foreign keys, and page through millions of rows right in your dashboard. Write SQL with completion from your live schema, read execution plans as a tree, and save the queries your team runs every week.
SELECT c.name, date_trunc('month', i.issued_at) AS month, sum(i.total) AS revenue FROM invoices i JOIN customers c ON c.id = i.customer_id WHERE i.issued_at >= now() - interval '6 months' GROUP BY 1, 2 ORDER BY revenue DESC;
| name | month | revenue |
|---|---|---|
| Kestrel Studio | 2026-09-01 | 18,420.00 |
| Aurora Freight | 2026-09-01 | 12,905.50 |
| Vela Analytics | 2026-08-01 | 9,860.00 |
| Harbor & Pine | 2026-08-01 | 7,312.25 |
Example view with sample data.
Writes are switched on deliberately, per session. Nobody drops a table by accident.
Every statement runs with a timeout, so one heavy query can't slow your application.
Editor sessions use a separate budget and never take connections from your app.
Who ran what, when, and how long it took — in your audit log.
Security & access
Isolation you can explain to your auditor.
- Every service runs as its own operating-system user, with its own isolated resources and storage volume.
- A managed admin role for your team — never superuser, never host access.
- Multi-factor authentication and five team roles, from Owner to Viewer.
- Revealing credentials, deleting a service or changing payment details asks you to confirm your identity again.
- When a Balta engineer needs access, they record a reason, the access expires on its own, and you see it in your audit log.
- TLS is required on every connection to your database.
Example view with sample data.
No lock-in
Standard Postgres in. Standard Postgres out.
Balta runs unmodified PostgreSQL — no proprietary storage engine, no forked protocol, no extension you can only get here. Moving in takes two commands.
Leaving takes the same two. Or one click in your dashboard, which produces a complete export — even while your account is suspended, and on the day you cancel.
# 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
Four steps to a production database.
- 01Choose
Pick a location, a PostgreSQL version, a plan and how much backup history to keep.
- 02Reserve
Your CPU, memory, storage and I/O are reserved on a host before anything is built.
- 03Build
Your service gets its own operating-system user, isolated resources and storage volume.
- 04Connect
Copy your pooled or direct connection string. Your first backup is already running.
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.
How Balta compares.
Against the three ways teams usually run PostgreSQL today.
| Usage-based serverless | Hyperscaler managed | Self-hosted | Balta DB | |
|---|---|---|---|---|
| Pricing | Billed by compute usage | Many separately billed items | Server plus engineering time | One flat monthly price |
| Egress fees | Varies by provider | Typically charged | Depends on your host | None |
| Resources | Shared or burstable | Varies by instance type | Yours to manage | Dedicated, kernel-enforced |
| Restore-verified backups | Varies | Varies | You build it | Automatic, in your dashboard |
| Data residency | Varies | Region-dependent | Your choice | Databases and backups in the EU |
| Built-in SQL editor | Varies | Varies | You install one | Included |
Predictable pricing, from €39 a month.
One price per service, per month, with every database inside it included. No compute units, no per-query charges, no egress fees. Pick the size you need, and change it whenever you outgrow it.
Development, staging and early-stage apps.
- vCPU
- 2
- Memory
- 4 GiB
- Storage
- 80 GiB
- Connections
- 100
- Databases
- 10
Production SaaS and web applications.
- vCPU
- 4
- Memory
- 8 GiB
- Storage
- 160 GiB
- Connections
- 150
- Databases
- 25
Growing products with real traffic.
- vCPU
- 8
- Memory
- 16 GiB
- Storage
- 320 GiB
- Connections
- 250
- Databases
- 50
Memory-intensive workloads and analytics.
- vCPU
- 8
- Memory
- 32 GiB
- Storage
- 500 GiB
- Connections
- 400
- Databases
- 50
Large, business-critical databases.
- vCPU
- 16
- Memory
- 64 GiB
- Storage
- 1 TiB
- Connections
- 600
- Databases
- 100
Questions teams ask before they switch.
Something else on your mind? Talk to our engineers.
What exactly is a service?
Do you offer high availability?
Where is my data stored?
How do I move my existing database?
Can I get my data out?
Is there a free trial?
Early access is open. Tell us about your workload and we'll reserve your place — and help you plan the move.