What We've Corrected
Free-tier terms move fast, and providers don't always update their marketing pages to match. When we find a stale claim, we fix it — and log it here. A site that documents its own corrections is one you can trust to tell you when it's wrong.
We earn commissions when you shop through the links below.
September 2026 — full-cycle verification pass
In our first complete verification cycle (2026-09-26/27), all 69 provider entries were re-checked against official vendor pages. Roughly 40 entries had stale claims. The significant corrections:
- Netlify (all entries): the classic "300 build minutes + 100 GB bandwidth" free tier is gone — replaced by a 300-credit monthly pool (≈15 GB bandwidth, ~20 production deploys).
- Fly.io (hosting + VMs): free tier removed; new users get a 7-day, 2-VM-hour trial only.
- Railway free plan: now $1/month in credits with no custom domains on free (previously listed as more generous).
- Render: free bandwidth corrected 100 GB → 5 GB; free Postgres expiry clarified (30 days after creation, 14-day grace).
- Vercel: build/compute metering clarified (1M invocations, 100 GB transfer, builds on Basic machines with no fixed minute cap).
- Cloudflare Pages: 100-project cap confirmed.
- AWS Free Tier: restructured to a credit-based program (up to $200 / 6 months) for new accounts since July 2025 — applied to S3, App Runner, EBS, RDS, CloudFront entries.
- Google Cloud SQL: always-free tier discontinued; 30-day trial only.
- Google Cloud Run / Cloud Functions / CDN: free-tier numbers updated to current documented limits.
- Auth0: 25K MAU free tier; Cognito Essentials 10K MAU.
- Database entries (Neon, Supabase): project/limit details corrected (Neon 0.5 GB + 100 CU-hrs per project; Supabase 500 MB / 2 projects).
- Messaging/email: Twilio trial units, Pusher plan rename, AWS SNS email price, SMTP2GO/Mailgun limits refreshed.
- GitHub Pages: published site limits corrected.
Full per-entry records — provider, exact source URL, last-verified date, status — live in the public data registry.
How corrections work
- We (or a reader) spot a claim that doesn't match the official page.
- We open the provider's own pricing/docs page and confirm the current terms.
- We update the entry, bump its ✓ verified date, and record the change here.
- All affected articles get checked for the same stale claim.
Found something off? Tell us at @FreeCloudZone on X — we'll verify and log it.