1,000 credits/month; extra 500-credit packs cost $5.
- Free option
- Free: 300 credits per month with a hard stop. Commercial use is allowed; enough for a small site with modest traffic and few production deploys.
- Why it fits
- Static sites and frontend apps that deploy from Git and want a generous, mature workflow.
- How deploys work
- Connect the Git repo; pushes build and deploy automatically with previews for every pull request.
- The tradeoff
- The credit system makes bills hard to predict — traffic, deploys, and compute all drain one pool.
Includes $20/month of usage credit, which covers modest traffic.
- Free option
- Hobby: free for personal, non-commercial projects — 100 GB data transfer, 1M function invocations, and 4 active CPU hours per month.
- Why it fits
- Next.js and frontend apps where you want deploys and previews to just work.
- How deploys work
- Connect the Git repo; every push builds and deploys with a preview URL per branch.
- The tradeoff
- Usage pricing past the credit can climb fast with real traffic, especially data transfer.
Includes 10M requests and 30M CPU-milliseconds per month.
- Free option
- Free: unlimited static requests and bandwidth, 100,000 Worker requests per day, 3,000 build minutes per month.
- Why it fits
- Static sites and JS/TS apps where bandwidth costs matter or a global edge is a plus.
- How deploys work
- Deploy from Git or with the wrangler CLI; framework adapters handle SSR apps.
- The tradeoff
- More platform-specific setup than the git-push hosts — adapters, wrangler config, and Workers-flavored storage.
