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.
- The managed database bills on top of this estimate.
Option 2 App platform
Render
≈$7/mo Starter
Move to Standard ($25, 1 CPU / 2 GB) if 512 MB gets tight; a managed database adds more.
- Free option
- Hobby workspace: $0 — static sites, free web services (0.1 CPU, 512 MB), a 30-day free Postgres, a 25 MB free key-value store, 5 GB bandwidth, 500 build minutes, 1 seat.
- Why it fits
- Apps and APIs that want git-push deploys with a fixed, understandable instance price.
- How deploys work
- Connect the Git repo; Render builds and deploys on push, with Docker support and instant rollbacks.
- The tradeoff
- The workspace-plus-services model means several line items, and bandwidth overage is pricey.
- The managed database bills on top of this estimate.
Option 3 App platform
Railway
≈$10/mo Hobby + usage
Roughly a quarter vCPU and 512 MB always on; a small database adds a few dollars.
- 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.
- The managed database bills on top of this estimate.
