Side-by-side comparison of 10+ database free tiers in 2026. Compare Supabase, Neon, Firebase, Turso, MongoDB, CockroachDB, Upstash, Cloudflare D1, and more — storage, compute, connections, and lock-in risk.

Database Free Tier Comparison 2026

Published 2026-03-31 · Reviewed 2026-10-19 · Figures compiled 2026-03-31, last checked 2026-10-19 · 115 of 147 figures in the tables below come from our records for 1,498 developer tools · 19 database services compared

📂 Browse all 45 Databases services with free tiers → Databases Category Hub
44
Database Services
All-in-One
Serverless Postgres with branching
Free Tier Removed

Quick verdict: Supabase's Free plan includes 500 MB Postgres, auth, storage, and realtime. Choose Neon for serverless Postgres with branching and scale-to-zero. Both Neon and Supabase now include auth and storage on their free plans. Firebase has auth, hosting, and Cloud Functions but locks you into Google. Turso is the edge play — SQLite with embedded replicas for ultra-low-latency reads. PlanetScale removed its free tier in April 2024, making it a cautionary tale for relying on free database hosting.

The database landscape has shifted: Serverless Postgres (Neon, Supabase) has won the developer mindshare battle. Edge databases (Turso, Cloudflare D1) are the new frontier. Traditional managed databases (RDS, Cloud SQL) are being replaced by platform-specific alternatives. And the PlanetScale free tier removal showed that even popular free tiers can disappear overnight.

Jump to section

  1. Main Comparison Table
  2. Postgres-Compatible
  3. Firebase / BaaS
  4. Edge / Embedded
  5. Key-Value / Cache
  6. Vector Databases
  7. By Use Case
  8. The PlanetScale Cautionary Tale
  9. Pricing Change Timeline
  10. Data Source

Main Comparison Table

Side-by-side comparison of the top 10 database free tiers.

Database Type Free Storage Compute / Connections Special Limits Branching Always Free? Lock-in Risk
Supabase Source ↗ Postgres + BaaS 500 MB Unlimited API requests, pooled connections 50K MAU, 1 GB file storage, 5 GB egress No Yes Low (standard Postgres)
  • Supabase makes daily backups only for Pro, Team and Enterprise projects, so a free project has none, and Supabase recommends exporting it yourself with the CLI's db dump command. (From supabase.com/docs/guides/platform/backups, read 2026-10-05.)
  • A paused project can be restored from the dashboard for 1 year. After that, only its backup file and Storage objects can be downloaded. (From supabase.com/docs/guides/platform/upgrading, read 2026-10-05.)
  • Supabase notifies you when you exceed the Free Plan quota. Continued overuse brings restrictions that can include a read-only database, 402 responses to every API request, or paused projects. They lift when the quota refills next billing cycle or on upgrade to Pro. (From supabase.com/docs/guides/platform/billing-faq, read 2026-10-05.)
  • Supabase's Free Plan needs no credit card; paid plans require one on file. (From supabase.com/docs/guides/platform/get-set-up-for-billing, read 2026-10-22.)
Neon CHANGED OCT 1 Source ↗ Serverless Postgres 1 GB/project 100 CU-hours/mo, scale-to-zero 100 projects, 10 branches/project Yes (10/project) Yes Low (standard Postgres)
  • Neon's Free plan needs no credit card. (From neon.com/pricing, read 2026-10-22.)
  • An agent can create a Neon Postgres project without a Neon account. Unclaimed projects expire in 72 hours and are limited to 100 MB storage and 1 GB transfer. A person claims the project to keep it. (From neon.com/docs/reference/claimable-neon, read 2026-10-22.)
  • On the Free plan, scale to zero can't be disabled: computes suspend after 5 minutes of inactivity. (From neon.com/docs/introduction/plans, read 2026-10-04.)
  • Neon doesn't pause Free projects for inactivity: an idle database starts again on the next query, with no restore step. (From neon.com/pricing, read 2026-11-01.)
  • If a Neon Free plan project's allowance of 100 CU-hours or 5 GB of network transfer is used up, its compute suspends until the next billing period or an upgrade. (From neon.com/pricing, read 2026-11-14.)
  • Neon's Free plan provides 100 CU-hours per project per month. One CU allocates about 4 GB of RAM, and 100 CU-hours is enough to run a 0.25 CU compute (about 1 GB of RAM) for 400 hours, about 17 days of continuous running. All computes in a project count toward usage, including those for each branch and any read replicas. (From neon.com/docs/introduction/plans, read 2026-11-03.)
  • At the storage cap, inserts, updates and deletes fail until space is freed or the plan is upgraded. (From neon.com/docs/introduction/plans, read 2026-10-04.)
  • Neon's Azure East US 2, West US 3, and Germany West Central regions no longer accept new projects as of April 7, 2026; Free-plan projects there inactive for 90+ days may be deleted after October 5, 2026. (From neon.com/docs/import/azure-regions-deprecation, read 2026-10-07.)
  • Platforms that create databases for their users can apply for the Agent Plan. You must have a Neon Scale plan with a credit card on file and get Neon's approval. Neon sponsors the databases for your free-tier users. Paid usage gets up to $25,000 in credits and compute at $0.106 per compute-unit hour. (From neon.com/docs/introduction/agent-plan.md, read 2026-10-11.)
  • Neon gives $20 in free credits to try paid features, claimed through a promo link in the Neon Console. (From neon.com/pricing.md, read 2026-10-11.)
  • Neon's pricing page offers startups up to $100k in credits. The startup page describes the Databricks Startup Program, up to $200K in credits for Neon and Databricks for qualifying startups. (From neon.com/startups, read 2026-10-11.)
  • Neon's open source programme: Neon reviews each application and decides per project whether to support it with a monthly cash sponsorship through GitHub Sponsors, Neon credits, or both, and how much. Cash sponsorships come from a pool of at least $200,000 a year and run for six-month terms that do not renew automatically. Supported projects can receive up to $5,000 in Neon credits and up to $5,000 in Neon AI Gateway credits. It requires an OSI-approved license and a GitHub Sponsors profile. (From neon.com/programs/open-source.md, read 2026-10-29.)
  • After the free plan, Neon's paid plans bill only for usage, with no monthly minimum: Launch charges $0.106 per CU-hour of compute and Scale $0.222, both charge $0.35 per GB-month of storage, extra branches cost $1.50 per branch-month, and network transfer beyond 500 GB per project costs $0.10 per GB. (From neon.com/pricing.md, read 2026-10-15.)
  • Upgrading to Launch does not raise the 100-project limit. Scale includes 1,000 projects, with more on request. (From neon.com/pricing, read 2026-11-14.)
  • Neon Realtime has been in public beta since 2026-10-15. It provides live updates from SQL queries without polling and is free during the beta. Compute and egress are billed under the plan; beta runs in four AWS regions: us-east-1, us-east-2, eu-central-1 and ap-southeast-1. (From neon.com/docs/realtime/overview, read 2026-10-16.)
  • Neon archives branches older than 14 days and not accessed for 24 hours. Unarchiving happens automatically when a branch is connected to or queried. Branches with large amounts of data may connect and query slower while unarchiving. (From neon.com/docs/guides/branch-archiving, read 2026-10-29.)
Firebase CHANGED SEP 1 Source ↗ NoSQL (Firestore) + BaaS 1 GiB 50K reads/day, 20K writes/day 50K MAU auth No Mostly (Storage removed Feb 2026) High (proprietary)
  • If a Spark project exceeds a no-cost quota, that product is shut off for the project (all its apps) for the rest of the calendar month, unless you upgrade to Blaze. (From firebase.google.com/docs/projects/billing/firebase-pricing-plans, read 2026-10-05.)
  • A Spark account can create a small number of projects, usually about 5-10. (From firebase.google.com/support/faq, read 2026-10-05.)
  • Linking a Cloud Billing account to a Spark project, including one with $300 Google Cloud free trial credits, automatically upgrades it to the pay-as-you-go Blaze plan. (From firebase.google.com/docs/projects/billing/firebase-pricing-plans, read 2026-10-05.)
  • On Spark, email-link sign-in is limited to 5 emails a day; sending more needs a billing account (Blaze). (From firebase.google.com/docs/auth/limits, read 2026-10-07.)
  • Phone (SMS) sign-in is not available on the Spark plan; on Blaze each SMS sent is billed. (From firebase.google.com/pricing, read 2026-10-20.)
  • Since September 1, 2026, Remote Config allows up to 100,000 fetch requests a day per Spark project at no cost. A Spark project that exceeds this limit gets 30 days of normal service, then is throttled unless it upgrades to Blaze. Blaze projects pay $0.06 per 10,000 requests above 100,000 a day, up to 10,000,000, and $0.01 per 10,000 above that. (From firebase.google.com/docs/remote-config/pricing, read 2026-10-17.)
  • Spark projects that used Remote Config before September 1, 2026 are subject to the 100,000-fetches-a-day limit from December 1, 2026 until they upgrade to Blaze. Blaze projects that used Remote Config before September 1, 2026 start Remote Config billing on February 1, 2027. A Spark project that used Remote Config before September 1, 2026 and upgrades to Blaze before November 15, 2026 starts Remote Config billing on February 1, 2027. (From firebase.google.com/docs/remote-config/pricing, read 2026-10-17.)
  • On the Blaze plan, all Gemini Developer API usage, including calls through Firebase AI Logic, is pay-as-you-go, and most projects must prepay. A project with no billing account (on Spark) can use the Gemini Developer API's free tier with no payment method. (From firebase.google.com/docs/ai-logic/pricing, read 2026-10-21.)
  • From November 2, 2026, Firebase AI Logic requires App Check enforcement. (From firebase.google.com/docs/ai-logic/pricing, read 2026-10-21.)
  • Firebase's Spark plan needs no credit card or other payment method. (From firebase.google.com/pricing, read 2026-10-22.)
Turso Source ↗ Edge SQLite 5 GB 500M rows read/mo, 10M rows written/mo 100 databases No Yes Medium (libSQL fork)
  • Turso's free plan needs no credit card. (From turso.tech/pricing, read 2026-10-22.)
  • The Developer plan costs $5.99 per month, or $4.99 per month when billed yearly. It includes 9GB storage, 2.5 billion rows read, 25 million rows written and 10GB syncs per month. Overage rates are $0.75 per GB storage, $1 per billion rows read, $1 per million rows written and $0.35 per GB syncs. (From turso.tech/pricing.md, read 2026-10-29.)
  • Overage billing on a paid plan is off by default. Enabling it lets you go over your plan's included limits and pay per usage. (From turso.tech/pricing.md, read 2026-10-29.)
  • On the Free plan, or on a paid plan with Overages off, your databases are blocked once you exceed the limit on any single metric. (From turso.tech/pricing, read 2026-10-29.)
  • Databases on the free plan are archived after 10 days of inactivity. The CLI command turso group unarchive <group-name> unarchives them. (From docs.turso.tech/cli/group/unarchive, read 2026-10-29.)
MongoDB Atlas Source ↗ Document NoSQL 512 MB Shared cluster (M0), 500 connections AWS/Azure/GCP regions No Yes Medium (MongoDB query language)
Cloudflare D1 Source ↗ Edge SQLite 5 GB 5M rows read/day, 100K rows written/day Resets daily at midnight UTC No Yes Medium (Cloudflare ecosystem)
Upstash Source ↗ Serverless Redis + KV 256 MB 500K commands/mo QStash: 1K messages/day No Yes Low (Redis-compatible)
  • Free Redis databases unused for at least 30 days are archived after warning emails. Their data is backed up and can be restored into a new database from the console. (From upstash.com/docs/redis/help/faq, read 2026-10-06.)
  • Adding the first payment method moves every free resource on the account to its paid plan: all Redis databases, plus QStash, Vector, Search and Blob. An account with a payment method cannot have free databases. (From upstash.com/docs/redis/overall/billing, read 2026-10-29.)
  • Paid databases do not get the Free plan's data and command allowance. (From upstash.com/pricing/redis, read 2026-10-29.)
  • Pay as You Go costs $0.20 per 100K commands. Storage past each database's first 1 GB is $0.25 per GB. Bandwidth past 200 GB a month is $0.03 per GB. (From upstash.com/pricing/redis, read 2026-10-29.)
  • A Pay as You Go database can have a monthly budget. When the budget is reached the database is rate-limited rather than continuing to bill. Budgets are set per database; there is no account-wide budget. (From upstash.com/docs/redis/overall/billing, read 2026-10-29.)
  • A free Upstash Redis database returns "ReplyError: ERR max requests limit exceeded" once it passes the monthly command limit. (From upstash.com/docs/redis/troubleshooting/max_requests_limit, read 2026-10-29.)
  • An agent can create an Upstash Redis database with no signup, card or API key by a POST request to upstash.com/start-redis. It is deleted after 3 days unless a person claims it from the console link in the response. (From upstash.com/pricing, read 2026-10-22.)
Convex Source ↗ Reactive backend 0.5 GB 1M function calls/mo 1 GB file storage, real-time sync No Yes High (proprietary)
PlanetScale FREE REMOVED Ended Serverless MySQL Was 5 GB Was 1B row reads/mo Removed April 2024 Was included No (removed) High (proprietary Vitess)
No longer free for new users: CockroachDB (September 2026), Momento (November 2025), PlanetScale (April 2024). Turso and Cloudflare D1 give 5 GB of free storage each. Supabase's free plan bundles Postgres with auth, file storage, edge functions and realtime; Neon's bundles Postgres with auth, object storage and Functions. Neon lets you create up to 100 projects with 1 GB each, 20 GB in total — ideal for microservices or per-client databases. PlanetScale's free tier removal in April 2024 was one of the most impactful such changes in developer tooling history.

Postgres-Compatible Databases

Postgres is the developer favorite for relational data. Four major managed Postgres options offer free tiers with very different trade-offs.

Provider Storage Compute Branching Scale-to-Zero Extra Features Best For
Supabase Source ↗ 500 MB Shared instance, always-on No Pauses after 1 week inactive Auth (50K MAU), Storage (1 GB), Real-time, Edge Functions Full-stack apps
Neon CHANGED OCT 1 Source ↗ 1 GB/project 100 CU-hours/mo, auto-scales 10 branches/project Yes (instant resume) Database branching, point-in-time restore, connection pooling Postgres purists, CI/CD preview DBs
Nile Source ↗ 1 GB 50M query tokens, 500 max connections No Always-on (no cold starts) Built-in multi-tenancy, unlimited tenant DBs SaaS / multi-tenant apps
Supabase vs Neon: The most common comparison. Choose Supabase if you want a Firebase-like experience with auth, storage, and real-time built in. Choose Neon for serverless Postgres with branching and scale-to-zero. Supabase projects pause after 1 week of inactivity; Neon scales to zero but resumes instantly. See our detailed Neon vs Supabase comparison.

Firebase / BaaS Databases

Backend-as-a-Service platforms bundle a database with auth, hosting, and serverless functions. Great for getting started fast, but watch for lock-in.

Provider Database Type Free Storage Auth Functions Real-time Lock-in
Firebase ECOSYSTEM LOCK-IN CHANGED SEP 1 Source ↗ Firestore (document) 1 GiB 50K MAU None on Spark (Blaze only) Yes High — proprietary API, hard to migrate
Supabase OPEN SOURCE Source ↗ Postgres (relational) 500 MB 50K MAU Edge Functions Yes Low — standard Postgres, self-hostable
Appwrite Cloud CHANGED JUN 29 Source ↗ Document-based 2 GB across 2 projects 75K MAU 750K executions/mo Yes Low — fully open-source, self-hostable
  • The Free plan's resources are shared across the account's 2 projects, which draw on one allowance. Paid plans give each project its own resources. (From appwrite.io/docs/advanced/billing/free, read 2026-10-11.)
  • A Free project with no development activity in the Appwrite Console for 7 days is paused. User traffic does not prevent pausing. The project becomes inaccessible to users and stops running backups, cron jobs, and scheduled functions until reactivated in the Console. (From appwrite.io/changelog/entry/2026-02-20-1, read 2026-10-11.)
  • Free projects are deleted after 90 days paused. (From appwrite.io/changelog/entry/2026-06-29, read 2026-10-05.)
  • From October 19, 2026, cron schedules for functions on Appwrite Cloud need a paid plan. On the Free and Education plans, functions run only on an interval of 60 minutes or longer. Existing cron schedules become intervals close to how often they ran. (From appwrite.io/changelog/entry/2026-10-15-1, read 2026-10-19.)
  • If a Free project reaches any resource limit, such as function executions or monthly active users, it freezes and the Console becomes read-only until the next billing cycle, or the owner upgrades to Pro or removes the resources over the limit. (From appwrite.io/pricing, read 2026-10-05.)
  • From November 5, 2026, Appwrite Cloud deletes inactive function and site deployments more than 30 days old by default. A deployment's age counts from the day it was created. The active deployment and any deployment a custom domain points to are kept. On the Free plan, retention can be raised to at most 90 days and each function or site keeps at most its 100 newest inactive deployments. (From appwrite.io/blog/post/default-deployment-retention, read 2026-10-22.)
  • On the Free plan, inactive deployments count toward the same 2 GB of storage as files and databases. (From appwrite.io/blog/post/default-deployment-retention, read 2026-10-22.)
  • Pro starts at $25 a month. It includes one project with 2TB bandwidth, 150GB storage, 3.5M executions and 200K monthly active users. Each additional project costs $15. (From appwrite.io/pricing, read 2026-10-29.)
  • Additional API bandwidth costs $15 per 100GB a month. Additional storage costs $2.8 per 100GB. Additional executions cost $2 per 1m. Additional users cost $3 per 1,000 users. Additional reads cost $0.060 per 100k and writes $0.10 per 100k. (From appwrite.io/pricing, read 2026-10-29.)
  • On Pro, Appwrite automatically buys extra resources when an organization exceeds its limits. The budget cap limits how much it can scale. (From appwrite.io/docs/advanced/billing/pro, read 2026-10-29.)
Convex Source ↗ Reactive document 0.5 GB Via Clerk/Auth0 integration 1M calls/mo Yes (built-in) High — proprietary query language
Firebase had major free tier changes in early 2026: Cloud Storage was removed from the Spark (free) plan in February 2026, and Google announced in March that Firebase Studio (formerly Project IDX) will shut down on March 22, 2027. If you're starting new, Supabase gives you a similar feature set on standard Postgres with no lock-in. Appwrite has the most generous free tier (75K MAU) and is fully open-source, with two constraints its plan card states: the free plan is limited to 2 projects, and a free project is paused after 1 week of inactivity. See our Supabase vs Firebase comparison.

Edge / Embedded Databases

Edge databases replicate data close to users for ultra-low-latency reads. The new frontier in database architecture.

Provider Engine Free Storage Read Limits Write Limits Best For
Turso Source ↗ libSQL (SQLite fork) 5 GB 500M rows/mo 10M rows/mo Multi-region reads, mobile/IoT
Cloudflare D1 Source ↗ SQLite 5 GB 5M rows/day 100K rows/day Cloudflare Workers ecosystem
PocketBase Unconfirmed SQLite Unlimited (self-hosted) Unlimited Unlimited Single-binary backend, hobby projects
Turso leads edge databases with 5 GB storage and 500M rows read/month on the free tier. Cloudflare D1 matches on storage but has daily read/write resets (useful for batch workloads, limiting for sustained traffic). PocketBase is free and unlimited but requires self-hosting — it's a single Go binary with SQLite, auth, and real-time built in.

Key-Value / Cache Databases

For caching, session storage, rate limiting, and real-time counters. Redis-compatible options dominate this category.

Provider Engine Free Storage Free Operations Persistence Best For
Upstash Source ↗ Redis-compatible 256 MB 500K commands/mo Yes Serverless apps, rate limiting
Cloudflare KV Source ↗ Key-value 1 GB 100K reads/day, 1K writes/day Yes (eventually consistent) Edge config, feature flags
Momento FREE REMOVED Ended Cache + pub/sub No free tier. Ended November 2025. First 5M operations/month free until November 2025. Cache only High-throughput caching
Redis Cloud Source ↗ Redis 30 MB 100 ops/sec, 30 connections No (not on the free plan) Dev/test Redis instances
Upstash is the standout for serverless Redis — 256 MB data and 500K commands/month with true pay-per-request pricing beyond the free tier. Cloudflare KV has more storage (1 GB) but very low write limits (1K/day) making it best for read-heavy config data. Redis Cloud's 30 MB free tier is tiny but useful for development. Note: Redis 8 added AGPLv3, an open-source license, besides RSALv2 and SSPLv1. Valkey is the leading open-source alternative, and Dragonfly a source-available one.

Vector Databases

Essential for AI/ML workloads — similarity search, RAG pipelines, and embedding storage. The fastest-growing database category in 2026.

Provider Free Vectors Free Storage Deployment Best For
Weaviate CHANGED JUN 17 Source ↗ Unlimited self-hosted. Cloud: 100,000 objects Unlimited self-hosted. Cloud: 1 GB memory, 10 GB disk OSS: free. Cloud: Free Forever, 1 cluster, 1 collection Self-hosted vector search
Zilliz Cloud Source ↗ Up to 5 collections 5 GB Free tier, no credit card Managed Milvus, large-scale vector search
LanceDB Source ↗ Unlimited (embedded) Unlimited (embedded) OSS: free. Cloud: closed to new accounts Embedded vector search, local development
Upstash Vector Source ↗ 200M vectors × dimensions 1 GB, up to 1,536 dimensions Serverless, no credit card. 10K queries or updates a day Lightweight RAG, serverless apps
For self-hosted: Weaviate and LanceDB are both fully open-source with no limits when you run them yourself — Weaviate Cloud's Free Forever tier is a separate, bounded offer (1 cluster, 100,000 objects, 1 collection). For managed: Zilliz Cloud has the most generous free tier (5 GB storage, 5 collections). Upstash Vector is the simplest to set up (serverless, 200M vectors × dimensions free) but its 10K daily query and update cap is what limits it for production workloads. If you're building RAG pipelines, Zilliz or self-hosted Weaviate are the strongest options.

By Use Case

When to Pick Each Database

Side project / hobby app → Supabase

Postgres + auth (50K MAU) + file storage (1 GB) + real-time + Edge Functions. Everything you need in one service with standard Postgres underneath. View Supabase details →

Pure Postgres / CI preview DBs → Neon

Best developer experience for Postgres. Branching lets you create instant database copies for CI/CD preview environments. Scale-to-zero means you only pay compute when queries run. Up to 100 free projects. Neon vs Supabase comparison →

Real-time mobile app → Firebase

Unmatched mobile SDK ecosystem. Firestore real-time sync, Firebase Auth, Cloud Messaging, and Crashlytics — all free tier. Just be aware of the proprietary lock-in and the Feb 2026 Storage removal from Spark plan. Supabase vs Firebase comparison →

Edge / low-latency reads → Turso

5 GB storage with embedded replicas for reads at the edge. libSQL (SQLite fork) means familiar SQL with no ORM required. Best for apps where read latency matters more than write throughput. View Turso details →

AI / vector workloads → Zilliz Cloud or Weaviate

Zilliz Cloud: 5 GB free managed Milvus with up to 5 collections. Weaviate: unlimited self-hosted. For simple RAG prototypes, Upstash Vector (200M vectors × dimensions free) gets you started fastest. AI/ML tools guide →

Startup scaling to production → CockroachDB or Neon

CockroachDB: CockroachDB closed its free Basic plan to new deployments on 2026-09-15; new Cloud organizations get a 30-day free trial with $400 in credit. Neon: serverless Postgres with usage-based pricing beyond free tier. Both have Postgres-compatible wire protocols for easy migration.

The PlanetScale Cautionary Tale

In April 2024, PlanetScale removed its free Hobby plan — one of the most impactful free tier removals in developer tooling history.

What happened April 2024

PlanetScale retired its Hobby plan on April 8, 2024. Its FAQ: "Databases which are not upgraded by April 8th will be put into sleep mode. If you need to retrieve your data after April 8th, you will be able to temporarily wake your database for 24 hours." The free tier had been generous: 5 GB storage, 1 billion row reads/month, 10 million row writes/month, and database branching. Thousands of developers had to migrate overnight.

Why it matters

PlanetScale's free tier, removed in April 2024, was widely recommended in tutorials, courses, and starter templates. Its removal broke thousands of hobby projects and forced a mass migration to Neon, Supabase, and Turso. It demonstrated that even popular, well-funded companies can eliminate free tiers when business priorities shift.

Lessons for choosing a database

1. Prefer standard Postgres. If you use standard SQL, migration is straightforward. PlanetScale's Vitess-based MySQL with custom branching was harder to migrate from.
2. Check our Free Tier Risk Index — we score 37 vendors by free tier sustainability risk.
3. Have a migration plan. Export your schema and data regularly. Test imports on your backup database provider.
4. Watch for signals: funding changes, pricing restructuring, reduced limits. We track all of these in our pricing changes timeline.

Pricing Change Timeline

Recent database-related pricing changes from our tracker. See the full timeline for all 569 tracked changes.

Date Provider Change Impact
effective Nov 12, 2026 DigitalOcean DigitalOcean Managed Databases keep running. PostgreSQL 14 reached end of life on DigitalOcean on November 12, 2026. From that date DigitalOcean upgrades the remaining PostgreSQL 14 clusters to a supported version outside each cluster's maintenance window. Source ↗ MEDIUM
effective Nov 3, 2026 SurrealDB Cloud On November 3, 2026, with SurrealDB 4, SurrealDB launched SurrealDB Earth, a serverless service on Cloudflare, and moved its free plan there. The Earth Free plan gives 3 million requests, 10 GB storage and 100 database active hours a month, and pauses at a limit. It replaced SurrealDB Cloud's Start plan, which gave one always-free instance with 0.25 vCPU and 1 GB memory and 1 GB of storage. Source ↗ MEDIUM
discovered Oct 4, 2026 · effective date unknown SurrealDB Cloud The free tier now includes a compute instance with 0.25 vCPU and 1 GB memory, but also lists several paid tiers with varying compute and storage options. The free tier is now explicitly a 'Start' plan with hourly billing for additional resources beyond the free limits. Source ↗ MEDIUM
effective Oct 2, 2026 Prisma Accelerate Prisma stopped offering Accelerate for new setups in its Console by 2026-10-02, and Accelerate, including Prisma Postgres connections that go through it, is retired on 2026-12-01. Existing Accelerate connections keep working until then. Prisma Postgres keeps running, and its databases come with connection pooling. Source ↗ HIGH
effective Oct 1, 2026 Neon Neon raised the Free plan's Postgres storage from 0.5 GB to 1 GB per project and added a limit of 20 GB across all of an account's projects. Source ↗ MEDIUM
effective Sep 15, 2026 CockroachDB CockroachDB stopped offering its free Basic plan (50 million RUs and 10 GiB of storage free per month) to new deployments on 2026-09-15, when it moved new clusters to Cockroach Continuum pricing. New Cloud organizations now get a 30-day free trial with $400 in credit. Clusters created before 2026-09-15 stay on their existing plans during their current term. Source ↗ HIGH
discovered Sep 7, 2026 · effective date unknown Chroma The free tier has changed. The current pricing page shows a Starter plan with $5 in free credits and usage-based pricing for writes, storage, and queries. Unconfirmed. We could not check this change against an archived copy of Chroma's page, so it does not count toward the rating. Source ↗ HIGH
effective between Jul 31, 2026 and Aug 27, 2026 Prisma Accelerate The free tier now offers 200,000 operations/month for Prisma Postgres, not 100,000 operations/month. The free tier also includes 1M requests/month for Prisma Compute, 360 GB-hours memory, 4 active vCPU-hours, and 10 GB outbound bandwidth. Source ↗ MEDIUM
effective Sep 1, 2026 Firebase From September 1, 2026, Firebase limits Remote Config on the no-cost Spark plan to 100,000 fetch requests a day per project. A Spark project over the limit keeps full service for 30 days from the first day it goes over, and after that requests above the limit are throttled unless it upgrades to Blaze. Blaze has the same 100,000 a day at no cost and then $0.06 per 10,000 requests. Firebase's pricing page had listed Remote Config as no-cost before. This applies to projects that enable Remote Config on or after September 1, 2026. Older Spark projects follow on December 1, 2026. Source ↗ MEDIUM
effective between Jul 11, 2026 and Aug 28, 2026 codehooks.io The free tier now has significantly reduced API call limits (1/sec, 500/day). Previously 60/minute. Source ↗ HIGH
discovered Aug 28, 2026 · effective date unknown ScaleGrid Startup Program The deal now has specific eligibility criteria (less than $1.5M in revenue and funding, new to ScaleGrid). The discount is now tiered: 50% off for 12 months on BYOC plans (medium or larger) and 25% off dedicated hosting (medium or larger). Small plans get 50% off BYOC and 25% off dedicated for 3 months. Previously 'up to $50,000 for a year with 50% off'. Unconfirmed. We could not check this change against an archived copy of ScaleGrid Startup Program's page, so it does not count toward the rating. Source ↗ MEDIUM
effective between Jun 18, 2026 and Jun 30, 2026 Turbopuffer Turbopuffer cut the Launch plan's monthly minimum from $64 to $16. Its changelog dates the cut to June 2026, and the Internet Archive's copy of 2026-06-18 still shows $64. Scale's minimum stays $256 a month. Source ↗ LOW

Upcoming Changes

These are announced changes that have not taken effect yet, listed soonest first.

Date Vendor Change Impact
effective Dec 1, 2026 Firebase Firebase Spark projects that enabled Remote Config before September 1, 2026 can use it under the old terms until December 1, 2026. From December 1, 2026, the 100,000-fetches-a-day limit applies to them, with 30 days of full service from the first day they go over, then throttling unless they upgrade to Blaze. A Spark project that upgrades to Blaze before November 15, 2026 is not billed for Remote Config until February 1, 2027. Blaze projects from before September 1, 2026 start Remote Config billing on February 1, 2027. Source ↗ MEDIUM
effective Dec 1, 2026 Prisma Accelerate Prisma stopped offering Accelerate for new setups in its Console by 2026-10-02, and Accelerate, including Prisma Postgres connections that go through it, is retired on 2026-12-01. Existing Accelerate connections keep working until then. Prisma Postgres keeps running, and its databases come with connection pooling. Source ↗ HIGH
effective Dec 22, 2026 Chroma On December 7, 2026, Chroma Cloud becomes read-only: applications can no longer create, update or delete data in it. On December 22, 2026, Chroma Cloud stops serving reads, so data must be exported before then. Open-source ChromaDB keeps running under the Apache 2.0 license. Chroma announced the wind-down on 2026-10-23, as it joins Replit. Source ↗ HIGH
effective Dec 31, 2026 Supabase Supabase says it is deprecating its legacy anon and service_role API keys by the end of 2026 and gives no day they stop working. Legacy keys keep working alongside the new keys until then. Replace the anon key with a publishable key (`sb_publishable_...`) and the service_role key with a secret key (`sb_secret_...`). Supabase's announcement says legacy keys will be deleted in late 2026, a date still to be confirmed. Apps that have not migrated will break then. Send the new keys on the apikey header only. The platform rejects them on the Authorization: Bearer header with Invalid JWT. Source ↗ MEDIUM
effective Jan 1, 2027 Google Cloud SQL for MySQL From January 1, 2027, Google charges extended support on every Cloud SQL for MySQL 8.0 instance, on top of the regular instance price. Cloud SQL enrolls them automatically. MySQL 8.4 or later instances are not affected. In Iowa (us-central1), Cloud SQL extended support for MySQL 8.0 costs $0.07 per vCPU-hour in years 1 and 2 and twice that in year 3. High-availability instances pay twice the per-vCPU rate. On shared-core instances the extended support charge is $0.018 an hour for db-f1-micro and $0.035 for db-g1-small. Committed use discounts do not apply. The charge stops when the instance is upgraded. On July 1, 2029, Cloud SQL upgrades remaining MySQL 8.0 instances to the default major version automatically. Source ↗ MEDIUM
effective Feb 1, 2027 AWS Amazon ElastiCache charges an Extended Support premium on every cache still running Redis OSS 6 starting February 1, 2027. Standard support for Redis OSS 6 ends January 31, 2027. Caches move to Extended Support automatically. The premium is 80% of the on-demand node price in years 1 and 2 and 160% in year 3. Reserved node discounts do not apply to the premium. AWS's example: a cache.m5.large node in US East (Ohio) costs $0.156 an hour plus $0.1248 an hour. The premium stops when the cache is upgraded to Valkey or Redis OSS 7 or later, or deleted. Source ↗ MEDIUM
effective Feb 1, 2027 Google Cloud SQL for PostgreSQL From February 1, 2027, Google charges extended support on every Cloud SQL for PostgreSQL 14 instance, on top of the regular instance price. Cloud SQL enrolls them automatically. Databases on PostgreSQL 15 or later are not affected. In Iowa (us-central1), Cloud SQL extended support costs $0.07 per vCPU-hour in years 1 and 2 ($0.14 for HA vCPUs), $0.14 per vCPU-hour in year 3, and $0.018 an hour on a db-f1-micro instance. Committed use discounts do not apply. Read replicas pay the same rate. There is no setting to turn it off. The charge stops when the instance is upgraded. On February 1, 2030, Cloud SQL upgrades remaining PostgreSQL 14 instances to the default major version automatically. Source ↗ MEDIUM
effective Feb 1, 2027 Azure Azure Database for PostgreSQL flexible server 14 leaves standard support on January 31, 2027. From February 1, 2027 every server still on PostgreSQL 14 is enrolled in Extended Support automatically. Servers on PostgreSQL 15 or later are not affected. There is no opt-out. Charges stop only when the server is upgraded to a supported version. Azure charges $0.07 per vCore-hour in East US in years 1 and 2. Year 3 is charged at twice the year 1 and 2 rate. Only running servers are charged. Stopped servers are not charged. Extended Support for PostgreSQL 14 ends November 11, 2029. Source ↗ MEDIUM
effective Feb 1, 2027 Azure Azure charges Extended Support on every Azure Database for MySQL flexible server 8.0 server starting February 1, 2027, after standard support ends on January 31, 2027. Azure enrolls them automatically. Servers on MySQL 8.4 or later are not affected. Azure charges $0.07 per vCore-hour in East US in years 1 and 2, and twice that in year 3. Stopped servers are not charged for Extended Support. There is no opt-out: the charge stops when the server is upgraded to a supported major version. Extended Support for MySQL 8.0 ends May 31, 2029. Source ↗ MEDIUM
effective Feb 28, 2027 Heroku Heroku is retiring Postgres 15 on Heroku Postgres. Databases still on Postgres 15 face forced upgrades from January 28, 2027, and after February 28, 2027, Heroku starts restricting access to them and deleting them, including followers. New Postgres 15 databases cannot be created since November 11, 2026, though forks and followers of existing ones can. Heroku asks users to upgrade to a newer Postgres version as soon as possible. Postgres 16, 17 and 18 remain available on Heroku Postgres. Source ↗ MEDIUM
effective Mar 1, 2027 AWS On March 1, 2027, AWS charges for RDS Extended Support on Amazon RDS for PostgreSQL 14 and Aurora PostgreSQL 14 databases that are enrolled and still on version 14. Standard support for PostgreSQL 14 on RDS and Aurora ends February 28, 2027. Databases on PostgreSQL 15 or later are not affected. Each database's RDS Extended Support setting decides what happens: an enrolled PostgreSQL 14 database is charged, and a PostgreSQL 14 database with it disabled is upgraded to a supported version on or shortly after February 28, 2027. The AWS CLI, the RDS API and CloudFormation enable it by default, and the console does not select it for new databases. The charge stops when the database is upgraded to a version under standard support or deleted. For earlier versions AWS charges $0.10 per vCPU-hour in years 1 and 2 in US East (Ohio), and Aurora Serverless v2 on PostgreSQL 14 is $0.085 per ACU-hour in years 1 and 2. On the same date RDS for PostgreSQL 12 moves from $0.100 to $0.200 per vCPU-hour in US East (Ohio). Source ↗ MEDIUM
effective Mar 31, 2027 Firebase Firebase keeps running. The Firebase Extensions service can be used until March 31, 2027. Installed extensions keep running after that date. After March 31, 2027, they cannot be updated, reconfigured or uninstalled, and their configuration cannot be downloaded. Google's replacement is function kits in Cloud Functions for Firebase (2nd gen). Source ↗ MEDIUM
effective Mar 31, 2027 Azure Microsoft retires two tiers of Azure Cache for Redis on March 31, 2027: Enterprise and Enterprise Flash. The Basic, Standard and Premium tiers retire later, on September 30, 2028. From April 1, 2027 every remaining Enterprise cache and every remaining Enterprise Flash cache is disabled. Creating new Enterprise or Enterprise Flash caches has been blocked since April 1, 2026. Reservations for both tiers are supported until March 30, 2027. Microsoft's replacement is Azure Managed Redis. Applications must switch to the new cache's hostname and access credentials. Azure Managed Redis is clustered by default, so applications should check that their client library works with a clustered cache. New customers cannot create Basic, Standard or Premium caches either. Since April 1, 2026, in Azure's public cloud, only a tenant that had any Azure Cache for Redis instance before that date can create them. Source ↗ MEDIUM
effective Sep 30, 2027 Firebase Firebase keeps running. Firebase Test Lab can be used until September 30, 2027. After that date, no tests can run. Google's replacement is the Developer Device Platform on Google Cloud. The Developer Device Platform requires billing. The no-cost Spark plan includes 10 virtual-device tests a day and 5 physical-device tests a day. Source ↗ MEDIUM
effective Sep 30, 2028 Azure Microsoft retires the Basic, Standard and Premium tiers of Azure Cache for Redis on September 30, 2028. From October 1, 2028 every remaining Basic, Standard or Premium cache is disabled. Since April 1, 2026 new customers in Azure's public cloud cannot create caches in these tiers. A tenant that had any Azure Cache for Redis instance before April 1, 2026 can keep creating them until the retirement. Reservations are supported until September 30, 2028. Microsoft's replacement is Azure Managed Redis. Applications must switch to the new cache's hostname and access key. Azure Managed Redis is clustered by default, so the client library must be set up for a clustered cache. Source ↗ MEDIUM

Data Source

Powered by AgentDeals. The tables on this page were compiled by hand from official pricing pages and have not been re-checked since. We track pricing changes across all major database providers. The pricing changes we track are updated continuously; the tables above are not.

Related guides: Database Alternatives · Neon vs Supabase · Supabase vs Firebase · Cloud Free Tier Comparison

Query database pricing programmatically via our MCP tools — compare databases, track pricing changes, or plan your data stack from your AI coding assistant.

A source check reads each cited page for that service's name and a price. The figures in the tables above are from our own records, except for the services whose entry below dates them to a read of the vendor's own page.

Frequently Asked Questions

What is the best free database service in 2026?

We publish no ranking of these. Nothing we record measures popularity or generosity, so naming a best or a top few would be our preference rather than our data. We hold 45 Databases services in our catalogue, each with the free tier terms. This page compares them on free tier limits, what each charges past them, and lock-in risk; the table above carries the figures side by side. Our ranking rule is published at /criteria.

Which database free tier is most generous?

We name no most generous free tier here, because generosity is not one quantity: the columns above measure different things and a tier that leads one trails another.

How do database free tiers compare on limits?

Each provider structures free tier limits differently — some cap storage, others cap requests or compute hours. Our comparison table provides exact numbers for each provider. Check the growth cost analysis section to understand what you'll pay when you exceed free tier limits.

Related Comparisons

Related Guides

Explore all 1,498 developer tool deals → Browse the full index or connect via MCP