Free tier vs paid tier: when to upgrade
Status: 🟩 COMPLETE (🟦 LIVING — pricing tiers shift; verify current limits) Last updated: 2026-06-21 Plain-English tagline: Vercel, Supabase, GitHub, and most modern services have generous free tiers. Knowing when each one stops being enough saves money before you need it and prevents nasty surprises after you do.
What this decides
For each service in your stack, you choose between staying on the free tier or upgrading to paid. Different services have different inflection points.
This framework covers the three core services for the Next.js + Supabase + Vercel stack:
- Vercel (hosting)
- Supabase (database + auth)
- GitHub (source code + CI)
Plus a brief look at when you might pay for other tools.
The short answer for the typical solo project
Start everything on free. Upgrade in this order when you hit the trigger:
- Vercel Hobby → Pro when the project becomes commercial (takes any money). Hobby’s “non-commercial only” rule is enforced.
- Supabase Free → Pro when you outgrow 500MB database OR the project needs to stay always-warm OR you need daily backups.
- GitHub Free → Pro — rarely needed for solo. Free covers private repos + 2000 CI minutes/month. You hit limits late, if ever.
Bible Quest is currently on Vercel Hobby (non-commercial, free for users) and Supabase Free. Both work fine; the constraint would be activity-based pausing if traffic ever dipped to zero for a week.
The factors that matter
- Are you generating revenue? Yes → most “non-commercial” free tiers are off-limits. Pay or risk account termination.
- What’s the cost of downtime? A demo can pause; a customer-facing app can’t.
- What’s the data size? Free tiers cap at modest limits; growth is invisible until you blow past them.
- What’s the activity pattern? Free tiers often pause inactive projects.
- Do you need premium features? Custom domains, branching, daily backups, SLAs — some only exist on paid.
- Are you a team or solo? Per-seat pricing changes the math.
Vercel — Hobby vs Pro
| Hobby (Free) | Pro ($20/user/month) | |
|---|---|---|
| Commercial use | ❌ Non-commercial only | ✅ Yes |
| Bandwidth | 100 GB/month | 1 TB/month |
| Function compute | 100 GB-hours/month | 1000 GB-hours/month |
| Function timeout | 10s | 60s default, configurable up to 800s |
| Team members | 1 | Unlimited (charged per seat) |
| Password-protected previews | ❌ | ✅ |
| Concurrent builds | 1 | 12 |
| Custom domains | âś… | âś… |
| SSL | âś… auto | âś… auto |
| Preview URLs | âś… | âś… |
When to upgrade Vercel
- You start charging for the product. Even $1 of revenue triggers Vercel’s commercial-use rule.
- You hit the 100 GB bandwidth cap. Audit traffic — that’s ~10–30k users on a moderate-content site.
- Your function timeouts at 10s aren’t enough. AI-heavy operations (LLM inference, big PDFs) often exceed.
- You want password-protected previews for sharing work with stakeholders.
- You’re collaborating with multiple developers on a real project.
When to stay on Hobby
- Personal projects, learning, hobbyist, non-commercial
- Internal tools used by a fixed group (no public traffic)
- Open-source projects without ads or paid features
Bible Quest situation: Bible Quest is non-commercial (free Bible study for kids), traffic is modest, functions are short — Hobby is correct.
Supabase — Free vs Pro
| Free | Pro ($25/month) | |
|---|---|---|
| Database size | 500 MB | 8 GB included; pay-as-you-go beyond |
| Storage | 1 GB | 100 GB |
| Monthly active users | 50,000 | 100,000 |
| Egress | ~2 GB | 250 GB |
| Project pausing | ⚠️ Paused after 1 week of inactivity | ❌ Never paused |
| Daily backups | ❌ | ✅ 7 days |
| PITR (point-in-time recovery) | ❌ | ✅ available as add-on |
| Branching | ❌ | ✅ |
| Custom SMTP | Required for serious email | âś… supported |
| Log retention | 1 day | 7 days |
When to upgrade Supabase
- Project inactivity pausing becomes a problem. Free-tier projects pause after a week of zero traffic. First request after pause is slow (~1 min cold start) and your data is briefly unavailable.
- You’re near the 500 MB database cap. Audit table sizes in the dashboard. Indexes and unstructured fields (JSONB, text) eat space fast.
- You need branching for safe schema experiments. Pro gives you Vercel-preview-style branches for database changes.
- Daily backups are non-optional. If you can’t tolerate “I lose 24 hours of data” worst-case, you need Pro’s automated backups (or your own backup pipeline).
- You need custom SMTP for auth emails. Free-tier Supabase email is rate-limited and from a Supabase address. Real apps need a custom provider (Resend, Postmark, SendGrid) configured.
When to stay on Free
- Hobby projects, prototypes
- Projects with consistent traffic (never idle for a week)
- Projects where 500 MB / 1 GB storage is plenty
- Anywhere “I can recover from a backup-loss” is acceptable
Bible Quest situation: Bible Quest has steady weekly activity (kids reading daily), well under 500 MB, no critical backups requirement (data is mostly recreatable content). Free works.
GitHub — Free vs Pro vs Team
| Free | Pro ($4/month) | Team ($4/user/month) | |
|---|---|---|---|
| Private repos | âś… unlimited | âś… unlimited | âś… unlimited |
| Collaborators on private repos | unlimited | unlimited | unlimited |
| Actions minutes (private) | 2,000 / month | 3,000 / month | 3,000 / month per seat |
| Codespaces hours | 60 / month | 90 / month | varies |
| Code review tools | basic | required reviewers, etc. | + protected branches per env |
| Issue templates | âś… | âś… | âś… |
| Wiki on private repos | ❌ | ✅ | ✅ |
When to upgrade GitHub
- Heavy CI usage (lots of test runs, big matrix builds). 2000 minutes covers most solo projects easily.
- You need protected branches with required reviewers (Pro on per-repo basis; Team for org-wide).
- You’re growing into a team that needs SAML SSO, audit logs, IP allowlists — Enterprise.
When to stay on Free
- Solo developers (the default for the Bible Quest setup)
- Small teams without strict CI/code-review requirements
- Educational use (GitHub Education is free)
Bible Quest situation: Free GitHub for private repo + light CI is plenty. The Bible Quest repo is private and CI is minimal.
Other services worth considering paying for
- Domain registration — ~$12/year. Pay through Vercel Domains for one-click setup. Bible Quest pays for
stmarkbible.com. - Email provider for transactional email — Resend, Postmark, SendGrid. Free tiers cover hundreds–thousands of emails/month; pay only when you scale.
- Monitoring — Sentry (free for hobby), Logtail, Better Stack. Pay when traffic > a few thousand requests/day or when you genuinely care about incident response time.
- Analytics — Plausible, Fathom, Vercel Analytics. Privacy-respecting paid alternatives to Google Analytics; ~$10–20/month.
- AI APIs — Anthropic, OpenAI. Pay per use; no free tier for production. Budget carefully.
When the answer is “spread across tiers”
Some projects strategically use different tiers across services:
- Vercel Pro + Supabase Free — paid for commercial hosting, frugal on data
- Vercel Hobby + Supabase Pro — non-commercial project, but data is critical (backups matter)
- Free everywhere + paid AI — prototype-tier infrastructure, but Anthropic API costs are unavoidable
This is fine. Match each tier to the actual need.
What if I’ve already chosen?
“I’m on free and just hit a cap”: read the dashboard. The service tells you which limit you hit. Upgrade just that tier; you don’t have to change other services.
“I overpaid”: downgrade if usage justifies. Most services allow it; some have minimum commitment periods. Read the terms.
“My free project is paused”: for Supabase, just visit the dashboard and click Restore. Wait 1–2 minutes. To prevent recurrence: a cron job pinging your app once a day costs nothing.
“I started monetizing without upgrading Vercel”: stop and upgrade before they catch you. Account termination is real for repeated violations.
See also
- Vercel 🟩 🟦 — tier details + pricing
- Supabase 🟩 🟦 — tier details + pricing
- GitHub 🟩 🟦
- Hosting & deployment — broader hosting context
- Cheat sheets — daily-use commands for these services
Sources
- Vercel pricing
- Supabase pricing
- GitHub pricing
- GitHub Education benefits — free upgrades for students