Laravel Cloud plans
Laravel Cloud sells four plans. All of them allow unlimited applications, environments, builds and team members, so the plan fee is not per site. What changes between plans is compute class, autoscaling, security and limits. These figures come from the Laravel Cloud pricing page, checked in November 2026.
| Plan | Monthly fee | Compute | Autoscaling | Custom domains | Log retention |
|---|---|---|---|---|---|
| Starter | 5 USD | Flex only, up to 2 GiB | None, 1 replica | 10 | 1 day |
| Growth | 20 USD | Flex and Pro, up to 32 GiB | Up to 10 replicas | 50 | 7 days |
| Business | 200 USD | Flex and Pro, largest sizes | Unlimited and scheduled | 250 | 30 days |
| Enterprise | Custom | Dedicated compute | Unlimited | Custom | 30 days |
Every paid plan includes 5 USD of usage credit that resets each billing period, and the first month on Starter is free. Growth also adds a basic web application firewall, team roles and unlimited preview environments, which is why most business apps start there rather than on Starter. Business adds custom roles and an advanced firewall, and private networking as an add-on.
Laravel Cloud compute prices
Compute runs on AWS Graviton instances and is billed per second while a replica runs. Each replica is billed for at most 28 days a month, so an always-on instance costs exactly the monthly cap below. Flex instances can scale to zero and wake in a median of about 500 ms. Pro instances are meant to stay on.
| Size | vCPU | Memory | Monthly cap | Available on |
|---|---|---|---|---|
| Flex 512 MiB | 1 | 512 MiB | 6 USD | All plans |
| Flex 1 GiB | 1 | 1 GiB | 12 USD | All plans |
| Flex 2 GiB | 1 | 2 GiB | 24 USD | All plans |
| Pro 4 GiB | 1 | 4 GiB | 32 USD | Growth and up |
| Pro 8 GiB | 2 | 8 GiB | 64 USD | Growth and up |
| Pro 16 GiB | 4 | 16 GiB | 128 USD | Growth and up |
| Pro 32 GiB | 8 | 32 GiB | 256 USD | Growth and up |
Two things are easy to miss. Every replica is a full extra line, so an app autoscaled to three Pro 4 GiB replicas around the clock costs 96 USD for compute alone. And worker clusters are separate compute, priced at the same rates, so a queue worker that runs all day is another instance on the bill.
Database, cache and queue prices
Databases are where an always-on bill grows. The rates below are the US East figures Laravel uses in its pricing documentation.
| Resource | Rate | Always on per month |
|---|---|---|
| Laravel MySQL Flex 2 GB | 0.03274 USD an hour | 22 USD |
| Laravel MySQL Pro 4 GB | 0.07143 USD an hour | 48 USD |
| MySQL storage | 0.10 USD per GB a month | Billed even while asleep |
| Serverless Postgres | 0.106 USD per compute unit hour | Scales to zero when idle |
| Serverless Postgres storage | 0.50 USD per GB a month | Billed continuously |
| Valkey 250 MB Flex | 0.00893 USD an hour | 6 USD |
| Valkey 1 GB Flex | 0.03571 USD an hour | 24 USD |
| Valkey 2.5 GB Flex | 0.07143 USD an hour | 48 USD |
| Managed queue operations | 1 USD per million | Plus worker time from 0.00548 USD an hour |
| Object storage | 0.02 USD per GB a month | No charge for data transfer out |
If your app still uses the older Redis by Upstash cache, check your invoice in December. Laravel Cloud has deprecated it, and from November 30, 2026 the 250 MB size goes from 5 to 10 USD and the 2.5 GB size from 40 to 50 USD. The documented path is a move to Valkey. Managed WebSockets through Reverb are priced separately, from 5 USD a month for 100 concurrent connections to 200 USD for 5,000.
Bandwidth and add-ons
Data transfer is earned rather than bought. Every second an instance runs adds to a pooled allowance for the whole organization, for example 100 GB a month for a Flex 1 GiB instance kept on, and about 100 GB for each Pro 4 GiB replica. Anything beyond the pooled allowance costs 0.10 USD per GB at the end of the billing period. Traffic between your app and Laravel MySQL, Valkey or Reverb stays inside the Cloud network and does not count. An extra custom domain beyond the plan limit is 0.25 USD a month.
The catch with earned bandwidth is that apps which scale to zero earn very little of it. A busy marketing site that sleeps between bursts but serves large images can run past its allowance while a quiet always-on app never comes close.
What a real Laravel app costs
Take a SaaS product on Laravel with paying customers, hosted in US East. Production runs on Growth with two Pro 4 GiB replicas kept on, one Flex 1 GiB queue worker running all day, Laravel MySQL Pro 4 GB with 30 GB of data and a 1 GB Valkey cache for sessions and cache. Staging runs one Flex 1 GiB instance and a MySQL Flex 2 GB database that are awake about 200 hours a month while the team works, with 5 GB of data. Traffic of 250 GB stays inside the earned allowance. Prices in USD.
| Item | Quantity | Monthly cost |
|---|---|---|
| Growth plan | 1 | 20.00 |
| Production web, Pro 4 GiB | 2 x 32 | 64.00 |
| Queue worker, Flex 1 GiB | 1 | 12.00 |
| Laravel MySQL Pro 4 GB | 1 | 48.00 |
| MySQL storage | 30 GB x 0.10 | 3.00 |
| Valkey 1 GB, always on | 672 hours x 0.03571 | 24.00 |
| Staging web, Flex 1 GiB | 200 hours x 0.01786 | 3.57 |
| Staging MySQL Flex 2 GB and storage | 200 hours x 0.03274 + 5 GB x 0.10 | 7.05 |
| Monthly usage credit | minus 5.00 | |
| Total | 176.62 |
Production compute is 76 USD, the database and cache together are 75 USD, and staging is barely 11 USD because it sleeps. Scale to zero saves real money on staging and preview environments. It saves nothing on production, which is where most of this bill sits. A third replica during a busy season adds 32 USD, and moving the cache to 2.5 GB adds another 24.
Finance teams that reconcile these usage invoices next to the ones from their other cloud vendors each month often pull the line items into a spreadsheet with a tool like Invoicexlsx, which makes month over month growth in each line obvious.
Laravel Cloud vs Forge and other server panels
Laravel Cloud and Forge come from the same company but sell different things. Cloud sells the whole platform, so you pay per resource and never see a server. Forge and other panels sell server management, so you pay the panel fee plus whatever server you rent, and every app, database and cache on that server shares one price. The Laravel Forge pricing breakdown lists the Forge plans.
For the app above, one 8 GB, 4 vCPU cloud server at 25 to 50 USD a month holds production, the worker, MySQL, Redis and staging with room to spare. With Deployment Starter at 49 USD the total is 74 to 99 USD.
| Setup | Platform or panel fee | Infrastructure | Monthly total |
|---|---|---|---|
| Laravel Cloud, the stack above | 20 | 156.62 after credit | 176.62 |
| One own server with Deployment Starter | 49 | 25 to 50 | 74 to 99 |
| Same, Starter billed yearly | 24 | 25 to 50 | 49 to 74 |
The comparison is not free of trade-offs. On one server you own database backups, upgrades and capacity, and a single server is not high availability. Deployment schedules backups off the box, patches the server and restarts Horizon, workers and the scheduler on every release, and you add a second server when uptime is worth more than the saving.
When Laravel Cloud is the right buy
Laravel Cloud wins clearly for small and idle apps. Laravel's own examples put a rarely used side project at about 0.40 USD and a cached blog at about 5.70 USD a month, both inside the credit. It also wins for apps with sharp, unpredictable spikes, where automatic replicas matter more than the monthly bill, and for teams that have nobody who wants to own a server. Spending limits with alerts at 50, 80, 90 and 100 percent make the usage model safer than it used to be.
When your own servers fit better
Own servers win when apps stay awake. An agency with ten client sites pays for ten sets of compute and database lines on Laravel Cloud, while on Deployment Starter fifteen sites on three servers cost one 49 USD subscription plus the servers. They also win when a client wants the app inside its own cloud account, or when Laravel sits next to a Next.js front end or a Python worker that Laravel Cloud does not host.
| Deployment plan | Monthly price | Servers | Sites | Members or enterprise features |
|---|---|---|---|---|
| Starter | 49 USD | 3 | 15 | 1 member |
| Team | 199 USD | 15 | 100 | 10 members, roles and audit log |
| Agency | 499 USD | 60 | Unlimited | 30 members |
| Enterprise | 1 499 USD | 250 | See plan details | SLA and invoicing |
Yearly billing is half price. The Laravel Cloud alternative comparison prices eight client apps on both and covers the move in four steps, the Laravel hosting page shows what Deployment installs for Horizon, Octane and the scheduler, and the Deployment plans page lists every limit. You can run one of your repositories through the demo above before choosing.