Laravel Cloud: More Features, Smarter Pricing

Laravel Cloud: More Features, Smarter Pricing

We’re rolling out updates to Laravel Cloud to help you scale faster and skip the guesswork. You’ll get predictable usage-based pricing, better defaults, improved security, and new powerful features in some plans, like Preview Environments and MySQL database support.

The tl;dr

  • Your pricing plan will change, starting August 13. Plans still have the same base prices, but included features and how usage is billed have improved. These changes will come into effect today, August 13.
  • You’ll get more value from your current plan: Each plan now includes more entitlements, like custom domains on Starter (formerly Sandbox), Pro compute on Growth (formerly Production), and networking upgrades on Business.
  • Your bill will be smarter, clearer, and more predictable: Bandwidth allowances now scale with actual compute usage, reducing waste and better aligning cost with value.
  • You don’t have to change plans; we’ll do that for you: All existing customers will be automatically moved to the new pricing structure.
  • Your app will run as usual: Your applications will continue running as-is. No migration steps required.
  • You’ll see the changes on your next invoice: The new billing structure will be reflected on your next invoice.

What’s Changing in my Pricing Plan?

If you’re on Sandbox or Production plans, the first change you’ll notice is the new name. We’ve updated our plan names to better reflect what they offer:

  • Sandbox is now Starter.
  • Production is now Growth.
  • Business remains Business.

Starter Plan: Now with Custom Domains

The Starter plan is still usage-based with no base monthly fee, but now includes custom domains by default. It’s a great choice for side projects, portfolios, and hobby applications that need a real-world domain without needing to upgrade.

Key highlights:

  • No monthly subscription fee; you pay only for what you use.
  • Custom domains are included.
  • Hibernation is now enabled by default to minimize costs.
  • You can keep costs in check with resource size caps.

Choose this if: Starter is the ideal plan for developers who are just getting started. Running multiple side projects with hibernation enabled and a custom domain is amazingly cheap.

Some use cases:

  • Ship five side projects, each with custom domains, and hibernation with a shared MySQL cluster for $11/month.
  • Host your static blog with 25,000 monthly visitors for $4/month.
  • Run your pre-scale startup with flexible App compute, MySQL, and Redis for $16/month.
  • Launch a Statamic CMS site for $7/month.

Growth Plan: Built for Development Teams

The Growth plan now starts at $20/month and comes with powerful new features that improve your ability to develop, test, and ship applications.

Check out the new features:

  • Preview Environments: For every pull request, Laravel Cloud automatically spins up a fully-isolated, production-like environment.
  • Queue and Worker clusters: On top of App clusters, Growth plan users will also get access to Queue and Worker clusters.
    • Queue clusters are a new type of cluster for queue workloads. They fully manage and autoscale queue workers, tracking CPU, memory, job throughput, and backlog in real time to determine how many workers and replicas your application needs. No more guesswork of sizing queue workers manually; the autoscaling capability will depend on latency so you can save even more on compute.
    • Worker clusters can be independently sized to run custom queue workers or background processes without affecting the main App compute.
  • More MySQL sizes and Pro compute: Laravel MySQL comes with two classes of compute (Flex and Pro), each with multiple CPU and RAM sizes. The Growth plan is equipped with Pro compute, which is designed to sustain heavy utilization and is capable of handling your large-scale, mission-critical workloads. Read our docs to see the complete list of CPU and RAM options and the respective price per GB per month.
  • Security upgrades: Growth plan users will benefit from stronger security and faster delivery with Basic Web Application Firewall.

Choose this if: Growth is built to scale with your application and your team. It’s perfect if you need production-grade performance, preview environments for every pull request, and advanced queue or background processing without the operational overhead.

Business Plan: Upgrading Soon

The Business plan ($200/month) will soon deliver a full suite of enterprise-grade features designed for high-compliance workloads and complex, organization-wide infrastructure.

Check out what’s coming:

  • Team collaboration:
    • Teams: Organize and manage members across projects.
    • Role-Based Access Control (RBAC): Assign granular permissions to match team responsibilities.
    • SAML SSO: Integrate with your identity provider for secure, centralized authentication.
    • SCIM provisioning: Automate user lifecycle management at scale.
  • Advanced security:
    • Advanced Networking: Gain fine-grained control over network security.
    • Advanced DDoS Protection: Customize thresholds for detecting and mitigating denial-of-service attacks.
    • Advanced WAF: Protect your apps with customizable, enterprise-level firewall rules.

Choose this if: Business is for teams that need larger resources, higher autoscaling limits, enterprise-grade security, strict compliance controls, and the ability to manage large, distributed teams with precision.

The updated Business plan will be available soon. Reach out to learn more or request early access.

Predictable Bandwidth Pricing

These changes were only possible because we’ve completely redesigned how bandwidth works to better reflect actual usage:

  • Bandwidth now scales with your compute usage. The more compute you use, the more data transfer you earn.
  • Bandwidth allowances are shared across all environments in your organization.
  • This model eliminates the waste of unused allowances and makes overages more predictable and accurate.

This results in transparent costs, fewer surprises, and pricing that aligns directly with the value you get.

Why Upgrade?

Laravel Cloud’s new pricing and features are built to give you more control (default hibernation, autoscaling), better performance, and a predictable billing model that provides added value. We heard what the community had to say, and our aim is for every developer, whether starting out, scaling a growing application, or managing complex infrastructure, to find a plan that fits their needs.

Spin up your next project on Laravel Cloud or consider upgrading for advanced features and better control with smarter pricing.

By the way, in case you missed it, MySQL backups are now available. As of yesterday, storage is also cheaper ($0.10/GB-mo in U.S. regions and $0.12/GB-mo elsewhere). Backups are billed separately at the same rate, and you get full control over retention (up to 30 days).

Keep reading

Laravel Cloud February 20, 2026

Laravel Cloud Incident Report: February 20, 2026

## Summary On February 20, 2026, Laravel Cloud experienced a connectivity outage lasting approximately 3 hours and 15 minutes. The disruption was caused by an [incident at Cloudflare](https://blog.cloudflare.com/cloudflare-outage-february-20-2026/), one of our infrastructure partners, which resulted in the withdrawal of IP prefix advertisements that route traffic to Laravel Cloud services. During this time, customers were unable to reach the Laravel Cloud control panel or some of their applications hosted on Laravel Cloud. No customer data was lost or compromised, and no deployments in progress were affected. The issue was entirely network-level — applications and their underlying infrastructure remained healthy throughout. While redundancy generally exists throughout our infrastructure, we have not yet extended that same protection to our IP announcement layer. Closing that gap is now a top engineering priority. Our goal is to implement additional failover protection so that no single upstream dependency can cause a prolonged outage for our customers. ## Timeline (UTC) | Time | Event | |------|-------| | **18:42** | Laravel Cloud monitoring detects connectivity failures. Incident declared and response team assembled immediately. | | **18:45** | Cloudflare begins investigating issues with their services and network. | | **18:48** | Laravel Cloud status page updated and notification posted to Twitter/X. | | **19:09** | Cloudflare identifies impact to a subset of BYOIP (Bring Your Own IP) prefixes. Reports the underlying issue as mitigated and begins working to restore affected advertisements. | | **~19:40** | Laravel Cloud attempts to re-advertise prefixes via the Cloudflare dashboard. The option is unavailable — prefixes are locked in a "Withdrawn" state requiring Cloudflare to unlock. We communicate this to Cloudflare via our shared support channel. | | **20:50** | Cloudflare acknowledges that some customers are unable to re-advertise their prefixes through the dashboard and begins working on a fix. | | **21:57** | Full connectivity to Laravel Cloud is restored as Cloudflare completes prefix restoration. | **Total duration of impact: approximately 3 hours and 15 minutes.** ## What Happened Laravel Cloud uses Cloudflare for network services including IP prefix management via their BYOIP (Bring Your Own IP) product. On February 20, Cloudflare experienced an incident that caused IP prefix advertisements to be withdrawn for a subset of their customers, including Laravel Cloud. When IP prefixes are withdrawn from BGP, traffic can no longer be routed to the affected services. This meant that while Laravel Cloud's applications, databases, and infrastructure were fully operational, users could not reach them because the network path no longer existed. Cloudflare identified the underlying cause and advised customers to re-advertise their prefixes manually through the Cloudflare dashboard. However, Laravel Cloud's prefixes were locked in a "Withdrawn" state that required Cloudflare's intervention to unlock. This meant the suggested self-mitigation path was not available to us, and recovery was dependent on Cloudflare restoring the prefixes on their end. ## What Was Affected - **Connectivity to Laravel Cloud applications** — users could not reach their apps - **Laravel Cloud dashboard and API** — inaccessible during the outage - **Deployments** — new deployments could not be initiated ## What Was Not Affected - **Customer data** — all data remained intact and secure - **Running applications** — apps continued to run normally; they were simply unreachable - **Databases and caches** — no data loss or corruption ## Our Response Our monitoring detected the issue within minutes, before Cloudflare's own status page reflected the incident. We immediately declared an incident, assembled our response team, and updated our status page and social channels to keep customers informed. Once Cloudflare published their self-mitigation guidance, we attempted to follow it but were unable to do so due to the prefix locking issue described above. We escalated directly with Cloudflare's team and continued to monitor and communicate throughout the incident. ## Looking Forward Laravel acknowledges that single points of failure in our infrastructure can disproportionately introduce risk in our ability to manage availability of the applications we serve. We are exploring strategies to decouple and introduce redundancy in our key networking layers to create better resiliency from underlying components. We take the reliability of Laravel Cloud seriously, and we understand the impact this outage had on our customers and their users. We are committed to learning from this incident and building a more resilient platform.

Laravel Team