YugabyteDB Aeon
Limit of one single node YugabyteDB cluster per account. Free Forever. No credit card information required.
Cluster size:
- Up to 2 vCPU, 4 GB memory, 10 GB storage, 3000 disk IOPS
- Up to 500 tables or 12.5 million rows
- Up to 15 simultaneous DB connections
- data out transfers: free allowance is 10GB per month for every 1 vCPU per month used in a cluster.
Inactive database policy:
Sandbox clusters are paused after 10 days of inactivity. When a cluster is paused, you receive an email notification. You need to resume the paused cluster before you can perform any operations on it. If you don’t resume your cluster, a second notification is sent after 13 days of inactivity, notifying you that the cluster will be deleted in 48 hours.
Backup: no backups.
PostgreSQL version: 11-compatible.
v2.25 preview release is 15-compatible. https://docs.yugabyte.com/preview/develop/pg15-features/
YugabyteDB now supports in-place zero downtime upgrade from a PostgreSQL 11-compatible (v2024.2.2) release to a PostgreSQL 15-compatible (v2.25.1) release.
Aiven
https://aiven.io/docs/platform/concepts/free-plan#free-plan-features-and-limitations https://aiven.io/docs/platform/concepts/service-power-cycle
- 1 dedicated VM
- 1 CPU per VM
- 1 GB RAM per VM
- 5 GB total storage
Inactive database policy:
- Free plans will be automatically powered off if they aren’t actively used.
- Services powered off for more than 180 consecutive days are automatically deleted. A notification is sent before the deletion.
Backup: included, but subject to inactive database policy.
PostgreSQL version: up to 17
Neon
https://neon.tech/docs/introduction/plans#free-plan-allowances
- Storage: 0.5 GB-month
- Compute: 191.9 compute hrs, enough to run a primary 0.25 CU compute 24/7.
- 0.25 CU is 0.25 vCPU, 1 GB RAM.
- Data transfer (egress): 5 GB per month
Inactive database policy:
Neon automatically archives branches that are:
- Older than 14 days.
- Have not been accessed for the past 24 hours.
Data is never deleted automatically.
PostgreSQL version: up to 17
Supabase
- 500 MB database size
- Shared CPU • 500 MB RAM
- 5 GB bandwidth
- 1 GB file storage
- 200 simultaneous DB connections to pooler in transaction mode without prepared statement support, or 15 in session mode
Inactive database policy:
- To save on cloud resources we’re currently pausing free-tier projects that are inactive for more than 7 days.
- Paused Free projects are restorable for 90 days following their pause date.
- Once a project is no longer restorable, the “restore” option is replaced with an option to download the latest logical backup, taken right before the project is paused, and all Storage objects.
PostgreSQL version: 15
Note: Supabase documentation states that transaction mode pooler endpoints don’t support prepared statements yet, but supavisor 1.0 has implemented support for it albeit in an inefficient way. What is going on?