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.
- The managed database bills on top of this estimate.
The official medium-SaaS example is about $53.90 in usage; add the $20 Growth fee and subtract its $5 usage credit.
- Free option
- New Starter subscriptions get their first month free; after that, Starter costs $5/month and includes $5 in monthly usage credit.
- Why it fits
- Laravel teams that want the framework, database, queues, scheduler, cache, and deploy workflow managed as one platform.
- How deploys work
- Connect a Git repository or run cloud ship; Laravel Cloud builds the supported runtime and deploys every push with zero downtime.
- The tradeoff
- The excellent Laravel experience comes from an opinionated runtime, so arbitrary containers and server-level access are out.
- The managed database bills on top of this estimate.
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.
- The managed database bills on top of this estimate.
