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 $20 fee plus typical usage overages; heavy traffic or extra seats push it higher.
- 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.
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.
