Neon or Supabase: Where to Move After PlanetScale Dropped Its Free Tier
This is not a best-of list. Those answer a question you didn’t ask. You are not here to crown a winner in the abstract; you are here because PlanetScale eliminated its free Hobby tier in April 2024, and now you need a new home for your database—likely with a free tier intact, possibly with branching, and definitely without a surprise re-entry fee you weren’t planning for.
Step 1: Deconstruct Your Actual Situation
You fit one of three profiles coming out of PlanetScale:
- Solo developers and side-project builders: You had a free MySQL database that slept when idle. Your budget ceiling is zero dollars, or close to it. Compliance regimes do not apply.
- Small teams shipping production apps: You need PostgreSQL now (PlanetScale was MySQL-only), or you want to stay on a familiar relational model but need more than raw database access. You have some budget, but you want predictable costs.
- Teams with existing backend infrastructure: You already run auth, storage, and API layers elsewhere—AWS, Vercel, Cloudflare. You need a database that plugs in, not a platform that replaces your stack.
Your existing stack matters enormously here. If you are all-in on Vercel serverless functions, your cold-start tolerance and connection-pooling needs differ from a team running persistent containers on DigitalOcean.
Step 2: Segment Into Real Sub-Decisions
The market presents two serverless Postgres options that dominate migration conversations. But “Neon vs. Supabase” is not one decision. It is three:
| Sub-decision | Neon posture | Supabase posture |
|---|---|---|
| Database-only vs. bundled backend | Pure PostgreSQL with compute/storage separation | Managed Postgres + auth + storage + realtime + edge functions |
| Branching model | Instant copy-on-write branches (data + schema) | Migration-based branching with per-branch compute billing |
| Scale-to-zero behavior | Suspends compute after inactivity; wakes on request | Free-tier projects pause after 7 days inactivity; paid plans stay always-on |
Step 3: Diagnose the Bottleneck
The actual bottleneck for most PlanetScale migrants is not pricing precision or branching speed. It is platform boundary: Do you want a database, or do you want a backend?
PlanetScale gave you a database and nothing else. That purity was the point. If you built your own auth layer, your own file handling, your own realtime notifications, you may resent Supabase bundling those as tightly coupled services. Conversely, if you are starting fresh and need to ship a full-stack feature this week, Supabase’s bundled backend-as-a-service platform compresses your timeline dramatically.
Decide database-purity vs. bundled-backend first. Everything else follows.
Step 4: Prescribe a Specific Path
Choose Neon if you want a standalone PostgreSQL database with serverless scaling, instant branching, and scale-to-zero economics. Accept the trade-off: you assemble or maintain your own auth, storage, and realtime infrastructure.
Choose Supabase if you want a managed Postgres instance wrapped in a backend platform with ready-built auth, storage, and realtime APIs. Accept the trade-off: you live inside Supabase’s architectural opinions, and escaping them later requires replatforming work.
Neon: PostgreSQL, Decomposed
Neon’s architecture separates storage and compute. Vendor documentation states this enables three headline capabilities: autoscaling, scale-to-zero, and instant branching. The storage engine is open-source and available on GitHub.
What you get
- Scale-to-zero: Compute suspends after a period of inactivity. The first request after suspension incurs a cold-start latency—published third-party benchmarks report noticeable latency after several quiet minutes. You pay nothing for compute while suspended.
- Instant branching: Copy-on-write storage creates isolated schema-and-data branches without duplicating the full dataset. This is genuinely impossible in traditional PostgreSQL architectures.
- Free tier limits: The vendor’s official pricing page lists 1 GB of Postgres storage per project and 100 projects included on the Free plan, following a major update.
Who Neon is wrong for
Neon is wrong for teams that need bundled backend services today and do not want to assemble auth, file storage, or realtime infrastructure themselves. It is wrong for teams that cannot tolerate cold-start latency on their first database request after idle periods—if your workload demands sub-100ms consistency at all times, scale-to-zero is not your model. It is wrong for teams seeking a drop-in replacement for PlanetScale’s Vitess-based MySQL compatibility; Neon is PostgreSQL-only, and migration requires schema and query adaptation.
Supabase: Postgres as Platform Core
Supabase begins with a dedicated PostgreSQL instance per project—every project on the Supabase Platform comes with its own dedicated Postgres instance, per vendor documentation. But the database is the foundation of a broader backend platform.
What you get
- Bundled services: Authentication (with multiple providers), file storage, realtime subscriptions, and edge functions. Published third-party benchmarks note that if you need these services, the value proposition is strong compared to assembling them separately.
- Always-on paid plans: Projects on paid plans are not paused for inactivity. Free-tier projects, however, pause after seven days of inactivity and require manual reactivation.
- Free tier limits: Published third-party benchmarks report 500 MB database storage on the Free plan, with 50,000 monthly active users and unlimited API requests. The Pro plan starts at $25/month per organization, with $10/month in compute credits included; additional projects on paid plans start at approximately $10 per month billed hourly.
- Branching: Migration-based branching with per-branch compute billing—published third-party benchmarks cite per-branch hourly rates plus compute costs.
Who Supabase is wrong for
Supabase is wrong for teams that want database purity and minimal surface area. If you already run Auth0, S3-compatible storage, or custom realtime infrastructure, Supabase’s bundled services become overlap, not value. It is wrong for teams that need instant data-branching for CI/CD pipelines; Supabase’s migration-based branching is slower and more expensive per branch-hour than Neon’s copy-on-write approach. It is wrong for teams that want to avoid platform lock-in on auxiliary services; extracting your data is straightforward, but extracting your auth configuration, storage policies, and edge functions requires deliberate migration work.
Visit Supabase’s official site
The PlanetScale Migration Context
PlanetScale’s Hobby plan deprecation was abrupt. Vendor documentation states the Hobby plan was deprecated on April 8, 2024, with all existing databases required to upgrade to a paid plan by that date. The Hobby plan was later reintroduced at a monthly cost—no longer free, no longer the zero-cost entry point that attracted solo developers.
For teams comparing costs: the vendor’s official pricing page indicates PlanetScale’s cheapest non-HA Postgres offering starts at a low monthly rate. But the free tier is gone, and that entry point is not the full story for production workloads. Neon and Supabase both offer functional free tiers with real storage allocations—Neon at 1 GB per project, Supabase at 500 MB—making them the practical destinations for zero-budget migrations.
Security and Compliance Notes
Neither Neon nor Supabase is a compliance shortcut. Both offer SOC 2 Type II reports and standard encryption practices, but applicability boundaries matter: your regulatory regime, data residency requirements, and access-control model determine whether either platform fits. This is not security advice. Evaluate against your specific compliance framework, and verify current certification status on vendor documentation rather than relying on general platform claims.
Direct Recommendation with Named Trade-Off
| Your situation | Pick | Trade-off you accept |
|---|---|---|
| Solo dev, zero budget, need branching for preview deploys | Neon Free | You build or wire your own auth and storage |
| Small team shipping fast, need auth + storage + realtime this month | Supabase Free or Pro | You live inside Supabase’s platform boundaries and branching costs |
| Existing backend infrastructure, just need better Postgres | Neon | Cold-start latency; you manage integration complexity |
| Production workload requiring always-on, predictable latency | Supabase paid plan | Higher baseline cost; platform coupling |
Commercial Disclosure
WeTooling has no affiliate relationships with Neon, Supabase, PlanetScale, or any vendor discussed here. We earn no commission from any platform mentioned. This phase of WeTooling is funded independently, and our recommendations carry no referral incentive. Treat any external ranking or review that does not disclose affiliate relationships as a trust hazard.
Visit DigitalOcean’s official site
Final Word
The PlanetScale free-tier elimination forced a decision. Do not let the urgency of that migration obscure the deeper choice: database as component, or database as platform anchor. Neon and Supabase are both competent managed PostgreSQL options. Neither is universally correct. The wrong choice is the one that solves your immediate pricing problem while creating an architectural mismatch you will pay for in integration work six months from now.
Pick based on your stack boundary, not your budget panic.
