What the Neon free tier actually caps, and what hitting it looks like
Neon's docs state the Free plan limits in one table, but the practical question is what happens the moment you cross one: does the app go down, does the branch stop creating, does the bill start? Here is each cap and its real behavior, not just the number.
Last checked November 18, 2026.
The five numbers
| Cap | Free plan limit |
|---|---|
| Storage | 1 GB per project, 20 GB per account total |
| Compute | 100 CU-hours per project per month |
| Projects / branches | 100 projects, 10 branches per project |
| Data transfer (egress) | 5 GB per project included |
| Autosuspend | After 5 minutes idle, cannot be disabled on Free |
Sources: Neon: Plans
What each cap looks like when you hit it
- Storage at 1 GB per project: new writes start failing once the project's data (not the account total) is full. A 20 GB account cap on top of that means a lot of small Free projects on one account run into the account cap before any single one hits its own 1 GB.
- 100 CU-hours a month is enough to run a 0.25 CU instance for roughly 400 hours — a project with real daytime traffic can burn through that well before the month ends if it never scales to zero between requests.
- Autosuspend after 5 minutes idle is fixed on Free: every request after an idle gap pays a cold-start reconnect, and there is no toggle to keep it always-on without upgrading.
- 10 branches per project is a hard ceiling, not a soft warning — branch creation fails outright past it, which bites CI setups that create one preview branch per pull request and never clean old ones up.
Sources: Neon: Plans
The per-project tradeoff instead of a per-account cap
Scribase bills per project, not per account: $5 a month on Hobby or $25 on Pro per project, so there is no account-wide storage ceiling that multiple small projects compete for the way Neon's 20 GB account total works. Idle Scribase projects scale compute to zero the same way Neon's do; the tradeoff is the opposite direction — no project-count cap, but also no $0 compute tier at all, since every project carries its own flat monthly price from day one.
Branches are not capped at 10 the way they are on Neon Free; the real ceiling today is the hosted backend, not the number itself — see the branch CLI reference for how creation, merge and TTL work.
Sources: Scribase pricing
Questions people ask
Can I pay for more storage without upgrading the whole project?
Neon's own docs describe Free as a fixed plan, not a pay-as-you-go add-on tier; the documented path past any of its five caps is moving to a paid plan, not buying one cap in isolation.
Does autosuspend ever turn off on Free?
No. Neon's Plans documentation states the 5-minute autosuspend on Free cannot be disabled; disabling it is a feature of paid plans.
Is the 20 GB account cap shared across every project I create?
Yes, per the Plans page: 1 GB is the per-project limit, 20 GB is the account total across every project on that account.
What happens to branches past the 10-per-project limit?
Branch creation is refused once a project is at its 10-branch cap on Free; deleting an old branch (or moving to a paid plan) is what frees a slot, per Neon's own documented limits.