Aiven
Managed open-source data services across AWS, Google Cloud and Azure, including PostgreSQL on plans that differ by node count and backup history.
- Managed databases
- Yes — indefinite, but idle services are powered off
- $5 a month for Developer — one VM, 1 CPU, 1 GB RAM, 8 GB storage, with no choice of cloud or region and no connection pooling. The first plan that behaves like a production service is Startup at $75 a month or $0.10 an hour, which is where the uptime SLA and multi-CPU sizing begin; Hobbyist sits between them at $12.
- 153 regions across six clouds — AWS 25, Google 42, Azure 39, OVH 22, UpCloud 16, DigitalOcean 9 — counted from Aiven's own reference list, which publishes the regions and no total. No magnitude is recorded, because Aiven states on that same page that the list differs per project and that not all service types are available in every cloud and region: the number is the platform's reach, not PostgreSQL's, and a bar drawn from it would be compared against providers whose counts are engine-specific.
Who it suits.
Teams who want more than one open-source data service from one vendor and one bill — Postgres beside Kafka, ClickHouse or OpenSearch — with the availability tier chosen per service rather than fixed.
Consider something else if…
You want long recovery history on a cheap plan. Backup history is what the plan tiers buy here: two days on the entry paid plan against thirty at the top.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Aiven does not publish are not listed.
Pricing
Free tier
Yes — indefinite, but idle services are powered off
Sources (1) →Sources ↓
- Free plans — Aiven docs ↗
“You don't need a credit card to create a free service and you can use them indefinitely free of charge. Free services do not have any time limitations. However, Aiven reserves the right to: Power off free services with no initial usage within the first few hours after the service is running. [...] Power off free services with no continuative activity on the service.”
Read 2026-09-09 · official docs
Entry paid plan
$5 a month for Developer — one VM, 1 CPU, 1 GB RAM, 8 GB storage, with no choice of cloud or region and no connection pooling. The first plan that behaves like a production service is Startup at $75 a month or $0.10 an hour, which is where the uptime SLA and multi-CPU sizing begin; Hobbyist sits between them at $12.
Sources (1) →Sources ↓
- Plans & Pricing — Aiven ↗
“Free $0 / month [...] 1 GB total storage Cannot select a specific cloud or region No integrations or connection pooling Developer $5 / month [...] 8 GB total storage Cannot select a specific cloud or region No integrations or connection pooling Hobbyist starting from $12 / month $0.02 / hour [...] Startup starting from $75 / month $0.10 / hour [...] 99.99% uptime SLA Business starting from $180 / month $0.25 / hour”
Read 2026-09-09 · official pricing
Pricing model
Fixed plans quoted both monthly and hourly, with the plan setting CPU, RAM and storage together rather than metering them separately. Aiven describes the pricing as all-inclusive: backups, monitoring and support come with the plan instead of appearing as line items. Higher tiers buy node count and backup history — Business adds a standby node, Premium a second.
Sources (1) →Sources ↓
- Plans & Pricing — Aiven ↗
“Aiven's pricing is all-inclusive and transparent, providing you with the confidence [...] Startup starting from $75 / month $0.10 / hour [...] Business starting from $180 / month $0.25 / hour [...] Everything in Startup, plus high availability Premium starting from $270 / month $0.37 / hour”
Read 2026-09-09 · official pricing
Execution
Managed connection pooling
Supported — not on the Free or Developer tiers
Sources (1) →Sources ↓
- Aiven for PostgreSQL® connection pooling with PgBouncer — Aiven docs ↗
“Without a connection pooler, the database connections are handled directly by PostgreSQL backend processes, with one process per connection: Adding a PgBouncer pooler that utilizes fewer backend connections frees up server resources for more important uses, such as disk caching: Instead of having dedicated connections per client, now PgBouncer manages the connections assignment optimising them based on client request and settings like the pooling modes.”
Read 2026-09-09 · official docs
Infrastructure
Regions
153 regions across six clouds — AWS 25, Google 42, Azure 39, OVH 22, UpCloud 16, DigitalOcean 9 — counted from Aiven's own reference list, which publishes the regions and no total. No magnitude is recorded, because Aiven states on that same page that the list differs per project and that not all service types are available in every cloud and region: the number is the platform's reach, not PostgreSQL's, and a bar drawn from it would be compared against providers whose counts are engine-specific.
Sources (1) →Sources ↓
- Available cloud regions — Aiven docs ↗
“This is a reference list of the default cloud regions available per provider on the Aiven Platform. note The list of available clouds can differ per project. Not all Aiven service types are available for all cloud providers and regions.”
Read 2026-09-09 · official docs
Data
Engine
PostgreSQL, alongside MySQL, ClickHouse, OpenSearch, Valkey, Kafka, Flink and Grafana. Aiven runs the upstream projects rather than a compatible reimplementation, which is why its own docs point at postgresql.org for per-release detail.
Sources (1) →Sources ↓
- Aiven for PostgreSQL® — Aiven docs ↗
“Aiven for PostgreSQL is the perfect fit for your relational data. A scalable SQL database solution that can be up and running within a few minutes. [...] Find a comprehensive per-release documentation on the PostgreSQL project website.”
Read 2026-09-09 · official docs
Connection limit
Set per plan, not by a formula: 100 on the entry paid plan (Startup-4), rising to 200, 400, 800 and 1000 as the plan grows, with 25 on Hobbyist, 20 on Free and 15 on Developer. Aiven states plainly that it does not apply a per-GiB formula, and that some of the allowance is used by Aiven itself to manage the service.
Sources (1) →Sources ↓
- Connection limits per plan for Aiven for PostgreSQL® — Aiven docs ↗
“Default values of the max_connections setting vary according to the service plan: Plan Max connections Developer 15 Free 20 Hobbyist 25 Startup/Business/Premium-4 100 Startup/Business/Premium-8 200 Startup/Business/Premium-16 400 Startup/Business/Premium-32 800 Startup/Business/Premium-64 and above 1000 note Aiven can utilize any number of the connections for managing the service. Aiven for PostgreSQL doesn't apply a fixed per-GiB connection formula”
Read 2026-09-09 · official docs
Database branching
Limited — a full copy from the latest backup, not copy-on-write
Sources (1) →Sources ↓
- Fork a service — Aiven for PostgreSQL® — Aiven docs ↗
“Fork your Aiven for PostgreSQL® service to create an independent copy for testing, debugging, or development without affecting the original service. Fork an Aiven service to create a complete copy of it from its latest backup. Forked services are independent and don't share resources with or increase the load on the original service. Common use cases for forking include: Creating a snapshot to analyze an issue. Creating a development copy of your production environment.”
Read 2026-09-09 · official docs
Point-in-time recovery
Bounded by the plan's backup history, so 2 days on the entry paid plan and 30 at the top. Granularity is fine within that: full backups daily with write-ahead logs copied every 5 minutes or per new file, whichever comes first.
Sources (1) →Sources ↓
- Aiven for PostgreSQL® backups — Aiven docs ↗
“Aiven for PostgreSQL® databases are automatically backed up, with full backups made daily, and write-ahead logs (WAL) copied at 5 minute intervals, or for every new file generated. All backups are encrypted using pghoard, an open source tool developed and maintained by Aiven.”
Read 2026-09-09 · official docs
Read replicas
Supported
Sources (1) →Sources ↓
- Use read replicas — Aiven for PostgreSQL® — Aiven docs ↗
“Create and use Aiven for PostgreSQL® read-only replicas Use Aiven for PostgreSQL® read-only replicas to reduce the load on the primary server and optimize query response”
Read 2026-09-09 · official docs
Backup retention
By plan: none on Hobbyist, 2 days on Startup, 14 on Business, 30 on Premium. The magnitude is Startup's 2 days, the entry paid plan. Aiven's high-availability page states 2 days for Hobbyist where the backups page states none — the backups page is the more specific of the two and is what is recorded here.
Sources (1) →Sources ↓
- Aiven for PostgreSQL® backups — Aiven docs ↗
“Backup retention time by plan The number of stored backups and the backup retention time depends on the service plan that you have selected. Plan Type Backup Retention Time Hobbyist None Startup 2 days Business 14 days Premium 30 days”
Read 2026-09-09 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.