--- title: "How Laravel Cloud Gave Developers Control Over Usage-Based Costs" url: https://getlago.com/blog/laravel-billing description: "After Laravel Cloud crossed 1 million deployments, Lago helps turn millions of hourly infrastructure data points into controlled, usage-based costs, from a $5 side project to enterprise scale." authors: ["Anh-Tho Chuong"] tags: ["Customer Stories"] published: 2026-09-03 updated: 2026-09-21 reading_time_minutes: 4 --- # How Laravel Cloud Gave Developers Control Over Usage-Based Costs ### From an idea to production Laravel was created to remove friction between an idea and a working application. Its open-source framework gives developers an opinionated, batteries-included way to build. Laravel Cloud extends that promise into production: connect a repository and let the platform manage compute, databases, cache, queues, storage, and security. The original target was to take an application from code to live in under 60 seconds. Laravel got the deployment time below 30 seconds. Less than one year after opening early access, Cloud crossed 1 million deployments. The product promise is simple. Build fast. Ship fast. Only pay for what the application uses. The billing system underneath it is not simple. Cloud resources are priced by actual consumption. Compute can run continuously, autoscale under load, or sleep when an application is idle. Different resource classes have different rates. Customers receive recurring credits and can set a hard spending limit. New infrastructure products need to appear in usage and on the same bill. Laravel needed billing to follow the application from a weekend experiment to a production business while keeping variable costs visible and bounded at every stage. That meant turning millions of data points from compute, database storage, bandwidth, serverless Postgres, key-value compute, object storage, and active users into billing events every hour. [Laravel's engineering retrospective](https://laravel.com/blog/1m-deploys-on-laravel-cloud-lessons-on-billing-admin-integrations) says every metric becomes an immutable event, projected to Lago in real time, with retries continuing for 24 hours if a delivery fails. ### The control problem Usage-based infrastructure creates a trust problem before it creates a billing problem. Developers understand a fixed server price. A bill that changes with compute time, storage, bandwidth, cache, queues, and scaling behavior is harder to control. Laravel heard that uncertainty about the monthly bill was preventing developers from committing to Cloud. It surveyed thousands of developers and followed up with 20 in-depth interviews to understand the blockers. The team responded by rebuilding the product and the pricing experience together. New Flex compute can scale an application's full stack to zero and wake in under 500 milliseconds, 20 times faster than the previous system. The $5 Starter plan includes $5 in monthly usage credits. A dormant Flex application can often keep its effective compute cost below $1 per month. Spending alerts fire at 50%, 80%, 90%, and 100% of the customer's limit. Hard limits stop new spending when the ceiling is reached. Each promise depends on the billing layer knowing exactly what ran, for how long, under which price, and against which balance or limit. [Read how Laravel Cloud rebuilt scale-to-zero and cost controls.](https://laravel.com/blog/your-laravel-cloud-stack-now-scales-to-zero) ### Pricing as code Cloud's pricing model changes as quickly as its infrastructure. New compute classes introduce new prices. Hibernation changes which seconds should be billed. A pricing release can add plan allowances, credits, resource filters, and new limits. Existing customers may need to remain on a legacy resource class while new customers move to the current model. Managing those objects manually would make billing the bottleneck for every infrastructure release. Laravel built a reconciliation workflow against Lago's API. The script walks the intended plan structure, compares it with the live pricing configuration, and pushes filter-level changes wherever it finds drift. It maintains 5 plans with 41 charges each and 2,019 filters. It runs in less than 5 minutes and makes a few safety checks at the same time. Pricing becomes a versioned system the team can test and automate, not a collection of settings someone needs to reproduce in a dashboard. That operating model helped Laravel ship major pricing changes, new compute classes, per-second billing for hibernating resources, and grandfathered legacy configurations without rebuilding its billing stack. ### One model from $5 to enterprise scale Lago's billable metrics and charge filters let Laravel represent each resource class and usage state directly. Compute, storage, and other resources remain distinct line items even when they share one customer invoice. Lago wallets provide the ledger behind Laravel's recurring usage credits. Lago meters usage and sends spending-alert signals. Laravel turns those signals into its customer-facing notifications and infrastructure controls. A $5 Starter customer can consume the plan's $5 monthly credit and scale to zero. Growth starts at $20 per month and Business at $200, while larger workloads can move to custom enterprise infrastructure. The billing model remains the same. Laravel also keeps control of its financial data. Billing and usage data flows from Lago into Laravel's warehouse, where Finance and analytics can model revenue and product usage in the tools they already use. ### Billing that blends into the background Laravel Cloud crossed 1 million deployments less than one year after early access. Millions of infrastructure data points are now collected every hour, transformed into immutable billing events, and sent to Lago. Laravel sends Lago around 80 million of those events every month and issues tens of thousands of invoices through Lago each month. **The more important outcome is what Laravel no longer has to do.** The more important outcome is what Laravel no longer has to do. Engineers do not rebuild pricing every time Cloud introduces a resource. Finance has full visibility and control over ARR and revenue reporting, unconstrained by any billing vendor's out-of-the-box analytics. Developers do not need to understand the infrastructure graph behind their invoice. Laravel can keep widening the stack while presenting one product promise: deploy quickly, pay for what runs, and know the ceiling before the month begins.