- The four flavours of 'free' - permanent tier, expiring database, trial credit, and self-hosting
- What Neon, Supabase, Aiven, Render and Railway actually include at $0
- The caps that bite in practice: storage, auto-suspend cold starts, connections, and backups
- How to run a prototype on a free tier without losing data when it pauses
- The signals that mean it is time to move to a paid plan
Free PostgreSQL hosting still exists in 2026, but the list gets shorter every year. Heroku's free tier is gone, ElephantSQL shut down completely, and several providers that used to hand out small databases now hand out expiring trials instead. What is left falls into four categories, and knowing which category a provider belongs to matters more than its feature list, because the category tells you when and how the free ride ends.
This guide covers every option that is genuinely free right now, what each one actually includes, and - just as important - the caps that decide when a free tier stops being the right tool.
The four flavours of free
Permanent free tiers. Neon, Supabase and Aiven will host a small Postgres database indefinitely at $0. These are real free tiers: no card, no clock.
Expiring free databases. Render will give you a free Postgres instance, but it is deleted after 30 days unless you upgrade. Fine for a demo, dangerous for anything else.
Trial credits. Railway gives new accounts a one-time credit; once it is burned, the database bills normally. This is a paid product with a free first month, not free hosting.
Hardware you already pay for. If a VPS is already running your app, Postgres in Docker on that VPS costs nothing extra. It is the only 'free' option with no storage cap - and the only one where backups are entirely your problem.
The permanent free tiers, compared
Provider | Storage | Compute | The catch |
|---|---|---|---|
Neon | 0.5 GB | Auto-scales to 2 CU, suspends when idle | Cold start after idle; 0.5 GB fills fast |
Supabase | 0.5 GB database | Shared; project pauses after ~1 week idle | Paused projects must be manually restored; 2 free projects max |
Aiven | 5 GB | 1 vCPU / 1 GB RAM, single node | Single node, no failover; limited connections |
Render | 1 GB | 256 MB RAM | Database is deleted after 30 days |
Railway | Trial credit only | Usage-based | Credit is one-time; then it bills per GB/CPU-hour |
Self-hosted VPS | Whatever your disk holds | Whatever the box has spare | Backups, upgrades and security are all yours |
Two names people still search for deserve a explicit mention: ElephantSQL announced end-of-life and shut down (its famous 20 MB 'Tiny Turtle' plan with it), and Heroku removed all free plans in November 2022. Any tutorial that wires a free app to a free Heroku or ElephantSQL database is describing a world that no longer exists.
The caps that actually bite
Storage is the hard wall
0.5 GB sounds like plenty until you remember that indexes, WAL and dead tuples all count. A modest table with a few million rows and two indexes will hit the Neon or Supabase cap. When you hit it, writes start failing - usually while you are demoing the thing to someone.
Auto-suspend means cold starts
Free compute suspends when idle - that is how providers afford to give it away. The first query after a suspend pays a resume penalty of a few hundred milliseconds to several seconds. Harmless for a portfolio project, deadly for a webhook endpoint that has to answer in two seconds.
Pauses can become deletions
Supabase pauses free projects after about a week of inactivity, and paused projects that are never restored are eventually removed. Render's free database is simply deleted at day 30. If the data matters at all, put
pg_dump "$DATABASE_URL" | gzip > backup-$(date +%F).sql.gz
Connections are tighter than you think
Free tiers cap concurrent connections aggressively, and serverless runtimes (Vercel, Lambda) open connections per invocation. If your free database starts throwing connection errors under trivial load, that is the cap - pool your connections or use the provider's built-in pooler.
Where free stops being the right answer
The honest rule: a free tier is the right home for a database exactly as long as losing that database would cost you nothing but a redeploy. The moment real users write real data, three things start to matter that no free tier provides - automated verified backups, compute that never suspends, and someone to escalate to when the database misbehaves.
The signals that it is time to pay: you have hit the storage cap once, you have noticed a cold start in front of a user, or you have thought 'I should really back this up' twice in the same week.
The paid floor: what $19 buys instead
Full disclosure: Swyftstack is our product, so weigh this recommendation accordingly. We built it for exactly the moment described above - a managed PostgreSQL database with automated backups, connection pooling and no auto-suspend, at a flat $19/month that does not meter compute-hours or egress. There is a 14-day free trial with no credit card, which is deliberately the same shape as a free tier: try it, keep the dump if you leave.
If flat pricing is not your preference, the paid entry points of the free-tier providers above are all reasonable too - we compared the usage-based ones in our Supabase pricing breakdown and Neon pricing breakdown.
How to leave a free tier without drama
One of Postgres's underrated features is that leaving any host is the same three commands. Dump from the free tier, restore to the new home, update the connection string:
pg_dump "$FREE_TIER_URL" -Fc -f app.dump
pg_restore -d "$NEW_DATABASE_URL" --no-owner app.dump
# then point DATABASE_URL at the new host and redeploy
Because that exit door is always open, there is no lock-in penalty for starting free. Pick whichever tier fits today; the migration when you outgrow it is an afternoon, not a project. The only unrecoverable mistake is having no dump when a paused project is finally removed.
Recommendations by situation
Learning SQL or Postgres itself: Neon. Scales to zero, nothing to maintain, and the 0.5 GB cap is irrelevant for exercises.
A prototype that needs auth and storage too: Supabase. The free tier includes the whole backend, not just the database.
The biggest free database: Aiven's 5 GB free plan - ten times the storage of the others.
A weekend demo: Render is fine; it will outlive the demo but not the month.
Anything with real users: a paid plan - flat-priced if you value a predictable bill, usage-based if your traffic is genuinely spiky.
Prices quoted here were checked in July 2026. Vendors change them; treat the structure as the durable part and re-check the current numbers before you budget.
Frequently asked questions
Is there a completely free PostgreSQL hosting service?
Yes. Neon, Supabase and Aiven all run permanent free tiers with no credit card. The trade-offs are small storage caps (0.5 - 5 GB), compute that suspends when idle, and limited or no automated backups.
What happened to ElephantSQL and Heroku's free Postgres?
ElephantSQL shut down entirely, and Heroku removed its free plans in late 2022. Guides that recommend either are out of date - the current free options are Neon, Supabase and Aiven.
Can I run a production app on a free Postgres tier?
You can, but you are accepting cold starts after idle periods, hard storage ceilings, and weak backup guarantees. The usual failure mode is not the database breaking - it is a paused project or an exceeded cap at the worst possible moment.
Is self-hosting PostgreSQL cheaper than a free tier?
If you already pay for a VPS, running Postgres on it adds no new cost and removes every free-tier cap. In exchange you own backups, upgrades and security patching yourself - that time is the real price.