Aiven
aiven.io · 3 records in Compute, Databases and KV, Storage · JSON
Records 3
- caveatAiven
Databases and KVfree tieridentity emailno cardlimit retention-clampedevidence documentedstale on 2026-11-22
- trialAiven (USD 300 trial)
Computefree tieridentity emailno cardlimit volume-quotaevidence documentedstale on 2026-11-23
- fails: quotaAiven free tier (PostgreSQL / MySQL / Valkey / OpenSearch / Kafka)
Storagefree tieridentity card?card?evidence reportedstale on 2026-11-05
Aiven
Databases and KV- Free allowance
- Free plan with 1 GB RAM and 1 GB total storage per service, on Postgres, MySQL, Valkey, Kafka and OpenSearch; free indefinitely with no time limit, but the service powers off after a period of inactivity
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- retention-clampedthe free service powers off after a period of inactivity; a service powered off for more than 180 days is automatically deleted
- Evidence
- documented6 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | Free plan with 1 GB RAM and 1 GB total storage per service, on Postgres, MySQL, Valkey, Kafka and OpenSearch; free indefinitely with no time limit, but the service powers off after a period of inactivity unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
|
| Binding | retention-clamped 1 GB of storage is small, but the inactivity power-off is what defeats the use a reader would pick this for: an unattended job that runs less often than the inactivity window. The 180-day deletion sets the outer limit. |
| Identity | email email signup; no card on the Free plan |
| Egress | no egress allowance, quota or per-GB rate is published on the free-plan pages or the PostgreSQL pricing table; recorded as a gap after checking both |
| Per-object cap | 1 GB total storage per service |
| Retention | the service powers off after a period of inactivity, on three triggers: no initial usage in the first few hours, or no continuative activity later; a powered-off service is deleted after 180 days. The Free plan is the exception to 'data retention is only limited by storage' (180 days) |
| Interface | rest, cli the Postgres wire protocol; an API and the avn CLI |
| Tooling | psql and any Postgres client; the avn CLI |
| Composes with | no longer a candidate for a weekly or monthly job: the free service powers off on inactivity and is deleted 180 days after it powers off, so a keep-alive is required and the paid Developer tier is what removes the clock |
| Reliability | free services power off on inactivity and a service powered off for more than 180 days is automatically deleted; a powered-off service for a version past end of life is deleted within 7… |
| Notes | 1 GB is the smallest free Postgres storage in this class, and the free plan powers off on inactivity, so it does not answer the question the class was formed to ask. 5 GB is what the plan used to give and several comparison pages still print it. The paid Developer tier at USD 5 a month is the version of this that stays up: 'Developer tier services are not automatically powered off when inactive'. |
| Evidence note | documented three first-party Aiven pages were read: the pricing page for 1 GB RAM and 1 GB storage, the free-PostgreSQL page for the inactivity power-off, and the service power-cycle page for the 180-day deletion. |
| Parsed numbers |
|
Evidence 6
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | aiven.io/pricing/postgresql | Free column: RAM per VM 1 GB, Total storage 1 GB; Developer USD 5 with 8 GB; Hobbyist from USD 12; 'Data retention is only limited by storage, with the exception of Free plan' |
| 2026-10-22 | aiven.io/free-postgresql-database | 'Service powers off after a period of inactivity (you'll be notified by email and in-platform beforehand)'; 'It's free indefinitely with no time limit, but the service is automatically powered off after a period of inactivity' |
| 2026-10-22 | aiven.io/docs/products/postgresql/concepts/pg-free-tier | two power-off triggers: 'Power off free services with no initial usage within the first few hours after the service is running' and 'Power off free services with no continuative activity on the service' |
| 2026-10-22 | aiven.io/docs/platform/concepts/service-power-cycle | 'Services powered off for more than 180 days are automatically deleted'; the 180-day grace does not apply to an end-of-life version, which is deleted within 7 days |
| 2026-10-22 | aiven.io/docs/platform/concepts/free-plan | 'Developer tier services are not automatically powered off when inactive'; the paid step is what removes the clock |
| 2026-10-22 | aiven.io/docs/products/postgresql/concepts/pg-free-tier | 'No connection pooling' and 'max_connections limit set to 20' on the free tier |
Corrections
- 2026-10-22 Aiven's free plan was recorded as the one that never pauses, and it powers off on inactivity
Aiven (USD 300 trial)
Compute- Free allowance
- New accounts include $300 in free credits and no payment details are required to sign up.
- Verdict
- triala time-boxed or one-time trial, not a recurring allowance
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- volume-quotaUSD 300 of credit over a 30-day trial
- Evidence
- documented3 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | New accounts include $300 in free credits and no payment details are required to sign up. The documentation states 'Aiven offers a free trial for 30 days with credits you can use to explore the Aiven Platform. You don't need a credit card to sign up.' The amount and the duration are on two different pages. unit mixed; metered on wall-clock |
|---|---|
| Price | none stated |
| Limits |
the amount is published on the developer-tier page and the 30 days on the service-pricing documentation; the /free-trial/ path returns 404 |
| Binding | volume-quota USD 300 over 30 days is 41.7 cents an hour, and the balance is the only thing that ends the trial |
| Identity | email no payment details are required to sign up; Google, Microsoft, GitHub or email; the console is JavaScript-only so the form fields were not observed live |
| Egress | not stated on the pages read |
| Per-object cap | not applicable: the offer is a spending balance, not a stored object |
| Retention | the trial runs 30 days; the free service tier is separate and unlimited (30 days) |
| Interface | rest, cli the Aiven console, the Aiven CLI and per-service connection URIs; no general-purpose VM |
| Tooling | the Aiven CLI, the Terraform provider, and each service's native client |
| Composes with | the credit pays for managed PostgreSQL, Kafka, Valkey and the rest at list price; it does not buy a machine that runs arbitrary software |
| Reliability | the free service tier continues indefinitely and is separate from the trial credit, so a service can outlive the balance on the Free plan |
| Notes | The credit buys managed services only. The smallest paid plans are Developer at $5 a month (1 CPU, 1 GiB, 8 GB) and Hobbyist at $12 a month or $0.02 an hour (1 CPU, 1 GiB, 8 GB). A general-purpose process cannot be hosted here. |
| Evidence note | documented two first-party Aiven pages were read on 2026-10-23; the trial URL carried by the search index is dead, so the amount and the duration are each sourced from the page that still carries them |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | aiven.io/developer-tier | quoted: 'New accounts include $300 in free credits and no payment details are required to sign up.' |
| 2026-10-23 | aiven.io/docs/platform/concepts/service-pricing | quoted: 'Aiven offers a free trial for 30 days with credits you can use to explore the Aiven Platform. You don't need a credit card to sign up.' |
| 2026-10-23 | aiven.io/free-trial | 404 on 2026-10-23; no Wayback capture for 2026-10, so the indexed trial URL proves nothing |
More fields 4
| credit usd | 300 |
|---|---|
| trial days | 30 |
| smallest paid plan usd month | 5 |
| hobbyist hourly usd | 0.02 |
Unknown values 1
- egress metered: egress metering was not published
- Free allowance
- 1 GB disk each for PostgreSQL, MySQL and Valkey (Valkey maxmemory = 50% of 1 GB RAM = 512 MB usable); 20 GB storage for OpenSearch; Kafka free tier is throughput-capped at 250 KiB/s.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- free tier
- Identity
- card?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported6 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 1 GB disk each for PostgreSQL, MySQL and Valkey (Valkey maxmemory = 50% of 1 GB RAM = 512 MB usable); 20 GB storage for OpenSearch; Kafka free tier is throughput-capped at 250 KiB/s. 'Only one service of each service type in your organization.' No time limit, no credit card. unit GB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Identity | card (inferred, not read) not published |
| Egress | Free — 'Network traffic is not charged separately' (Aiven service pricing doc). This is the best egress term of any structured store here, which makes the tiny byte quotas the only blocker. |
| Per-object cap | not stated |
| Retention | not stated |
| Interface | rest, cli rest |
| Tooling | psql / mysql / redis-cli / OpenSearch REST API / any Kafka client; Aiven Terraform provider and avn CLI for provisioning; PG-wire and RESP protocols unchanged |
| Composes with | One service of each type per ORG (verified in the Valkey free-tier doc: 'Only one service of each service type in your organization'). So one org yields ~1 + 1 + 0.5 + 20 GB = ~22.5 GB across four services, plus Kafka. 23 orgs would reach 500 GB — the best per-org yield of any structured store found, and the only one where egress is genuinely free. |
| Reliability | Aiven 'reserves the right to power off free services with no initial usage in the first few hours' and to power off services with no continuing activity. For a cold archive that means keep-alive traffic is mandatory or the service sleeps. No data loss reported, just power-off. |
| Parsed numbers |
|
Evidence 6
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | aiven.io/docs/platform/concepts/free-plan | 'The Free tier is available for the following service types: Apache Kafka, MySQL, OpenSearch, PostgreSQL, Valkey'; 'You don't need a credit card ... use them indefinitely free of charge'; 'Aiven reserves the right to power off free services with no initial usage ... Power off free services with no continuative activity' |
| 2026-10-21 | aiven.io/docs/products/postgresql/concepts/pg-free-tier | '1 GB RAM', '1 GB disk storage' |
| 2026-10-21 | aiven.io/docs/products/mysql/concepts/mysql-free-tier | '1 GB disk storage'; https://aiven.io/docs/products/valkey/concepts/valkey-free-tier — '1 GB RAM', 'maxmemory set to 50%', 'Only one service of each service type in your organization' |
| 2026-10-21 | aiven.io/docs/products/opensearch/concepts/opensearch-free-t | '4 GB RAM, 20 GB storage', '2 shards', 'Max 20 shards per node', '50 concurrent connections' |
| 2026-10-21 | aiven.io/docs/products/kafka/free-tier/kafka-free-tier | 'Streaming throughput up to 250 KiB/s ingress and 250 KiB/s egress', 'Up to 5 topics, each with two partitions' |
| 2026-10-21 | aiven.io/docs/platform/concepts/service-pricing | 'Network traffic is not charged separately' |
More fields 1
| dead end | {"failure_class": "quota","why": "1 GB disk each for PostgreSQL, MySQL and Valkey (Valkey maxmemory = 50% of 1 GB RAM = 512 MB usable); 20 GB storage for OpenSearch; Kafka free tier is throughput-capped at 250 KiB/s. 'Only one service of each service type in your organization.' No time limit, no credit card.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read