45 days until Aiven free MySQL databases are powered off
Aiven retired the free tier for Aiven for MySQL. Existing free databases get powered off and deleted on December 21, 2026.
Kill posts9 min read
Tim Neunzig
45 days. That is the clock Aiven put on free Aiven for MySQL databases.
On November 6, 2026, Aiven retired the free MySQL tier. You cannot create a new free MySQL service. Existing free services get powered off on December 21, 2026. Their data and backups get deleted.
Aiven says that deletion cannot be undone. That is the whole story if your side project, prototype, or learning app treated a free managed database as storage you controlled.
What happened
Aiven for MySQL is a managed MySQL database service. It runs on AWS, Google Cloud, Azure, DigitalOcean, OVH, and UpCloud. Aiven handles provisioning, backups, high availability, and upgrades. The product ranges from a small virtual machine to high availability clusters with standby nodes.
The free tier was the small end of that machine. Developers used it for hobby projects, prototypes, demos, and learning. The core job was simple: create a MySQL endpoint, connect your app, store data, stop thinking about the database server.
On 2026-11-06, Aiven posted a changelog entry retiring the free tier of Aiven for MySQL. The same day, new free MySQL services stopped being available. Existing free MySQL services got a final date: 2026-12-21.
Aiven states that remaining free services will be powered off on that date. It also states that their data and backups will be deleted. The kill sheet says Aiven says this cannot be undone.
You get three paths. Upgrade to the Developer plan. Move to Aiven's free PostgreSQL tier. Export your data with mysqldump or mydumper and leave.
The paid path starts at the Developer plan, listed at $5 per month. That plan has 1 CPU, 1 GB RAM, and 8 GB storage. It runs on DigitalOcean only. It has no integrations or connection pooling, according to the pricing notes in the kill sheet.
The next public MySQL prices move up fast. Hobbyist starts at $19 per month. Startup starts at $75 per month. Business starts at $180 per month. Premium starts at $270 per month.
Aiven's pricing material still matters here because the promise of a free tier was not framed as a trial clock in the pricing FAQ. The kill sheet says the pricing FAQ still says free plans do not have time limitations. The operational reality changed anyway. Free MySQL is being retired, and the free database gets deleted if you do not act before 2026-12-21.
This is not a complex vendor failure. It is simpler. A free tier is not an ownership model. It is a permission slip. The permission changed.
What it actually did for you
You did not use Aiven for MySQL because you wanted a catalog of database product features. You used it because you wanted MySQL to exist somewhere else.
The daily value was managed provisioning. Click, create, get a MySQL endpoint, copy a connection string, ship the small app. A small project does not need a database program. It needs a reachable database.
The next value was basic storage. The free tier was mostly used for hobby projects, prototypes, and learning. That means the important feature was not high availability architecture. It was keeping application data alive.
Then came automatic backups. Backups are the safety net people expect from a managed database. That expectation now has a hole in it. The retired free services will have both data and backups deleted on 2026-12-21.
Automatic maintenance and upgrades also mattered. Solo developers and small teams do not want to patch a database server for a prototype. They want to avoid becoming the database administrator for a side project.
Monitoring and metrics had some value. You needed to know whether the database was running, reachable, and healthy enough for the app to work.
Now look at the padding.
High availability with standby nodes belongs to Business and Premium. Your tiny free MySQL database did not become mission critical because a pricing page offered standby nodes somewhere else.
Read replicas across regions are useful for a different problem. Most free tier projects do not have a global read load. They have one app and one small database.
Third-party metrics and log integrations are fine when you already have an operations stack. For a hobby project, they are mostly surface area.
Cloud migration between providers sounds useful until your immediate problem is exporting before deletion. At that point, portability means a dump file you can restore.
Choice of cloud and region beyond the Developer plan also stops mattering on the forced upgrade path. The Developer plan is DigitalOcean only, according to the kill sheet.
Connection pooling matters when connection count is a real constraint. A small app with a direct MySQL connection often does not need it. The Developer plan does not include it anyway.
So strip the product down. You needed MySQL, basic backups, restore confidence, a connection string, and a health check. You did not need a platform decision for a side project. You needed a database that would not be deleted because a free tier ended.
The math
The headline rent is not scary. That is the trap. The paid replacement Aiven recommends is cheap enough to look harmless.
| Option | Tier | Price per user per month | Team size | 36 months | Total |
|---|---|---|---|---|---|
| Keep renting Aiven for MySQL | Developer | $5 flat per month, not per user | 10 | $5 × 36 months | $180 |
| Own the replacement | Starter build | $750 to $2,500 one time, not per user | 10 | 1 build | $750 to $2,500 |
You keep control, not short-term cash: against $180 in Developer rent over 36 months, a $750 to $2,500 owned build does not pay back inside 36 months.
The payback is 500 months at the top of the build range, using the $5 per month Developer bill from the kill sheet. The low-end payback is not given in the kill sheet.
That is why this is not a normal subscription math kill. A $180 bill over 3 years is not the wound. The wound is the forced lifecycle. Your database got a deletion date.
If you pay Aiven $5 per month, you avoid the deletion of that free service by moving to the Developer plan. You still rent the database lifecycle. You still accept that the provider can change what exists at the edge of the product.
If you build the owned replacement, you spend more money up front. You stop using a free vendor tier as the thing standing between your app and data loss.
What you would build instead
You do not rebuild Aiven. That would be stupid. You rebuild the small slice you used.
- Database server: one self-hosted MySQL-compatible database running MySQL Community Server, MariaDB Server, or Percona Server for MySQL.
- Migration path: export the Aiven database with mysqldump or mydumper before 2026-12-21, import it into the owned database, then update the application connection string.
- Backup job: scheduled dumps or engine-specific backups, stored away from the live database server.
- Restore check: a scripted restore test so your backup policy is not a superstition.
- Basic health monitoring: process checks, connection checks, and one application-level query that proves the app can reach the database.
- Documentation: the server location, credentials handling, restore command, backup schedule, and cutover notes.
The stack is plain. One self-hosted server. MySQL Community Server, MariaDB Server, or Percona Server for MySQL. mysqldump or mydumper for export and import. Percona XtraBackup if you choose Percona tooling. Simple operational scripts for backup and restore checks.
Hosting is also plain. One self-hosted server controlled by you. The kill sheet does not state the server price, so do not invent one. The point is not that hosting is free. The point is that the database lifecycle is no longer tied to Aiven's retired free tier.
Data migration is the urgent part. Export the Aiven database with mysqldump or mydumper before 2026-12-21. Import it into the self-hosted MySQL-compatible server. Update the application connection details. Verify the data. Verify writes. Verify backups. Then stop the app from depending on a service scheduled for deletion.
The open-source building blocks are boring, which is correct.
MySQL Community Server is GPL-2.0 and serves as the self-hosted MySQL database engine. MariaDB Server is GPL-2.0 and can be used as a MySQL-compatible database engine. Percona Server for MySQL is GPL-2.0 and gives you a MySQL-compatible engine with Percona backup tooling through Percona XtraBackup.
You lose real things. You lose Aiven-managed provisioning and maintenance. You lose Aiven automatic backups. You lose Aiven support for the managed service. You lose Aiven-managed upgrades. You lose Aiven high availability features such as standby nodes on Business and Premium. You lose Aiven cloud and region choice on paid plans above Developer. You lose Aiven third-party metrics and log integrations.
That is acceptable only if your project is small enough. If you need Aiven's operations layer, keep paying. If your database is a prototype data store, a side project backend, or a learning app with modest traffic, the owned version is enough.
Do not confuse enough with glamorous. It is one database server, backups, restore checks, and a connection string. That is the job.
Who should do this
Do this if you run a side project or prototype on the free Aiven for MySQL tier and the data matters. The bill is not the issue. The deletion date is. Export before 2026-12-21 and move to your own MySQL-compatible server.
Do this if you are a small team with a simple internal tool that only needs one MySQL database. A 10-person team does not need per-seat database rent for this use case, and the Developer plan is flat at $5 per month anyway. The better reason to own it is operational control.
Do this if you want to stay on MySQL instead of moving to Aiven's free PostgreSQL tier. A database migration just to remain free is not free work. It is schema work, query work, driver work, and testing work. The kill sheet does not price that work, so treat it as unknown instead of pretending it is zero.
Keep renting if you need managed high availability, standby nodes, paid support, managed upgrades, read replicas, third-party log and metrics integrations, or cloud and region choice. Keep renting if nobody on your side will own backups and restore checks. A self-hosted database without restore discipline is just a slower way to lose data.
Keep renting if $5 per month solves the problem and the database is not worth a migration. That is a valid answer. Just stop calling it free. It is rented infrastructure with a cheap entry plan.
The SaaSKiller Take If your project only needs a small MySQL database, the $180 three-year Developer bill is not the main problem. The problem is that your free database got a 45-day deletion clock. Export it, run your own MySQL-compatible server, and stop treating a vendor free tier as storage you control.
Sources
- https://aiven.io/changelog/507f8b1b-dd8f-4841-ac4a-940ac492b688
- https://aiven.io/pricing/mysql
- https://aiven.io/pricing?product=mysql
AI-generated