3,000 credits/month; extra 1,500-credit packs cost $10.
- 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.
Extra requests cost $0.30 per million; bandwidth remains free.
- 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.
Option 3 App platform
Railway
≈$20/mo Pro
$20 minimum with higher resource limits and unlimited team seats.
- Free option
- Free: $1 of monthly usage credits, capped at 1 vCPU / 0.5 GB per service, one replica, and 3-day log history.
- Why it fits
- Full-stack apps and APIs where you want the app and its database running in minutes.
- How deploys work
- Connect a repo or image; Railway detects the build, deploys it, and adds databases with one click.
- The tradeoff
- Pure usage billing means the bill moves with your traffic — predictable only while the app is small.
