Hosting for Laravel: what 31 makers' products chose
Among 31 makers' products built with Laravel that we know the hosting of, Vercel leads: 9 of them (29%). Next come Amazon Web Services (9) and DigitalOcean (9).
What shape is your app? A frontend or serverless app fits a frontend cloud. Long-running servers, background workers and databases fit a PaaS or container platform. A hyperscaler cloud has every building block but leaves you to assemble them; a platform or framework that deploys into your own cloud account sits between, with platform-style deploys and the resources on your own cloud bill.
What makers on Laravel chose
| Option | Laravel products | All makers | Free for | Team of 5, 10,000 users |
|---|---|---|---|---|
| 9 (29%) | 57% | None | $120/moPro + Flat Rate CDN 10M | |
| 9 (29%) | 13% | None | $17/moPay as you go (Lambda + EC2 t4g.small) | |
| 9 (29%) | 4% | — | — | |
| 4 (13%) | 11% | ~830 users | $12/moWorkers Paid | |
| 3 (10%) | 3% | None | $13/moCPX12 | |
| 1 (3%) | 5% | — | — | |
| 1 (3%) | 1% | — | — | |
| 1 (3%) | 1% | — | — |
Live makers' products with a source for both: that they're built with Laravel, and what they use for hosting. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You built a Next.js or other frontend-heavy app and want preview URLs on every pull request
Vercel 9 here - Your app is a static site or docs and should cost nothing to host
Cloudflare 4 here - You want a flat monthly bill and full control, and don't mind running one server
Hetzner Cloud 3 here
Vercel
Frontend cloud9 Laravel products here (29%). About $120 a month for a team of 5 with 10,000 users (Pro + Flat Rate CDN 10M).
llms.txtMCPCLIIn v0Best forNext.js apps — zero-config deploys and preview URLs.
Trade-offThe Hobby plan is non-commercial; costs grow with usage.
“Listed in their tool stack on Starter Story (platform)”
- Pushing to Git deploys automatically with zero configuration. 4 sources
- Every commit or pull request gets a preview URL, so changes are reviewed live before release. 4 sources
- Heavy bot traffic, such as Meta's crawler, can multiply the bill with little protection. 3 sources
- Execution limits and middleware quirks need workarounds. 1 source
Status page: 21 incidents in the last 90 days, 12 major (its own page, 2026-10-19).
“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗
Amazon Web Services
Hyperscaler cloud9 Laravel products here (29%). About $17 a month for a team of 5 with 10,000 users (Pay as you go (Lambda + EC2 t4g.small)).
Best forThe widest catalog of building blocks — Lambda, containers, managed databases, queues — to assemble your own infrastructure.
Trade-offYou wire up networking, permissions and deploys yourself; billing is per service and hard to predict.
“AWS for infrastructure, DevOps & monitoring Slack for communications and for alerts Notion for everything else: Roadmap, CMS, Task planning, Coordination with”
- It offers a huge catalog of services in one place, from databases to queues to AI. 4 sources
- It scales up and down with bursty traffic without re-architecting. 3 sources
- Major outages, from long us-east incidents to struck data centers, have taken customer services down. 4 sources
- Its services can be tricky to configure. 1 source
“AWS for infrastructure, DevOps & monitoring Slack for communications and for alerts Notion for everything else: Roadmap, CMS, Task planning, Coordination with”
HostingMaker says so · source ↗“The service is built for scalability, effectively managing numerous simultaneous connections and messages without the need for manual infrastructure oversight. It offers high reliability, ensuring real-time message delivery. Security is robust, featuring SSL/TLS for data protection, and options for private channels and authentication to manage access.”
HostingMaker says so · source ↗“Besides that, our cloud infrastructure of choice is AWS and we use a lot of services: S3, SQS, SES, RDS, Lambda, CloudFront, API Gateway, and so on.”
HostingMaker says so · source ↗“So, here’s what we use; Gmail (obvious) AWS as our cloud of choice Laravel Forge to deploy our product on servers Webflow to power our landing page …”
HostingMaker says so · source ↗“To manage applications that need to scale dynamically with demand, AWS Lambda is the ideal solution. It efficiently handles traffic spikes and periods of inactivity, preventing the wastage of compute resources.”
HostingMaker says so · source ↗All of Amazon Web Services: who uses it, alternatives, pricing →
DigitalOcean
PaaS9 Laravel products here (29%).
llms.txtBest forApp Platform deploys from git next to DigitalOcean's managed databases, storage and droplets.
Trade-offFewer built-in extras than Vercel or Railway, and instances are billed per size, not per request.
“Listed in their tool stack on Starter Story (platform)”
Status page: 16 incidents in the last 90 days, 2 major (its own page, 2026-10-19).
“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so +1 · source ↗“Listed in their tool stack on Starter Story (platform)”
HostingMaker says so · source ↗“- DigitalOcean for servers.”
HostingMaker says so · source ↗“Have used Digital Ocean for all of my products lately. Love how easy it is to get something launched quickly.”
HostingMaker says so · source ↗“DigitalOcean hits that sweet spot between simplicity and control. I love how fast I can spin up a droplet and get real stuff running without jumping through enterprise hoops. Amazing docs and great pricing too.”
HostingMaker says so · source ↗
Cloudflare
Edge platform4 Laravel products here (13%). Free up to about 830 users. About $12 a month for a team of 5 with 10,000 users (Workers Paid).
llms.txtMCPBest forCheap global hosting with Workers, plus database (D1) and storage (R2) on the same platform.
Trade-offThe Workers runtime isn't full Node.js; some libraries need adapting.
“Listed in their tool stack on Starter Story (other)”
- Workers, D1, R2, Durable Objects and more combine as bindings on one platform instead of separate vendors. 4 sources
- The free tier bundles DNS, CDN, TLS and abuse protection in one dashboard. 2 sources
- Bot checks and default AI-crawler blocking get in the way of legitimate users and automation. 4 sources
- The dashboard is slow and buggy, with login and passkey problems. 2 sources
Status page: 48+ incidents in the last 90 days, 5 major (its own page, 2026-10-19).
“Listed in their tool stack on Starter Story”
HostingMaker says so +1 · source ↗“Listed in their tool stack on Starter Story (other)”
HostingMaker says so · source ↗“Listed in their tool stack on Starter Story”
HostingMaker says so · source ↗
Hetzner Cloud
Your own server3 Laravel products here (10%). About $13 a month for a team of 5 with 10,000 users (CPX12).
Best forA lot of CPU and RAM per euro, in European, US and Singapore regions.
Trade-offFewer managed services than big clouds, and account verification can be strict.
- Servers cost a fraction of hyperscaler prices for strong price-to-performance. 3 sources
- Storage Boxes are a cheap offsite target for backups. 4 sources
- Recent price increases have made it less of a bargain. 4 sources
Also chosen, and not seen yet
Fewer Laravel products here: Google Cloud Platform (1), Heroku (1), Hostinger (1).
Real options for hosting not seen among these Laravel products yet: Netlify, Railway, Render, Fly.io, Coolify.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Laravel.
- Vercel → Cloudflare 242 pull requests · how they moved
- Cloudflare → Vercel 83 pull requests · how they moved
- Amazon Web Services → Cloudflare 39+ pull requests · how they moved
- Vercel → Amazon Web Services 38 pull requests · how they moved
- Amazon Web Services → Vercel 15 pull requests
- Vercel → Hetzner Cloud 11 pull requests
Getting hosting right
Connect the repo so every push deploys and every pull request gets a preview URL. Put secrets in the platform's environment variables, never in the repo.
- Leaving a paid platform on its default autoscaling and spend limits, so one viral day or a bot crawl turns into a surprise invoice.
- Putting a long-running job, websocket or large upload behind a serverless function and hitting its time or size limit in production.
- Keeping the database on a different provider or region from the app, so every query crosses the internet and pages get slow.
The rest of the Laravel stack
What makers' Laravel products chose for their other decisions, the most common pick for each:
- Transactional Email: Postmark 11 of 24
- Web Analytics: Google Analytics 16 of 24
- Payments: Stripe 17 of 20
Questions
What do most Laravel apps use for hosting?
Among 31 makers' products built with Laravel that we know the hosting of, Vercel leads: 9 of them (29%). Next come Amazon Web Services (9) and DigitalOcean (9).
What does hosting cost for a Laravel app with 10,000 users?
On our usage model for a team of 5 with 10,000 users, Vercel comes to about $120 a month (Pro + Flat Rate CDN 10M); Amazon Web Services comes to about $17 a month (Pay as you go (Lambda + EC2 t4g.small)); Cloudflare comes to about $12 a month (Workers Paid); Hetzner Cloud comes to about $13 a month (CPX12). Prices are from each vendor's pricing page.
Which hosting option stays free longest for a Laravel app?
Cloudflare: on our usage model its cheapest plan stays free up to about 830 users.
How this is counted: a product is on Laravel when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its hosting. How evidence is collected.