Batteries included
One argument, carried by one device: the framework is the circuit, Cloud closes it.
A FIELD GUIDE TO LARAVEL · STORIES
Stories
Presentations built in advance, one chapter each. Every story has a commercial and a technical reading on the same address: present full screen with F, step with the arrow keys, export with E.
- Stories
- 14
- Readings
- 2 each
- Sources
- sheets · The Monitor · docs
- Register
- warm, the Artisan pages
01
Why Laravel and Cloud
The thesis, the customer story and the catalogue, as shipped.
AI speed. Human judgment.
One message traced through five accountable handoffs, then the architecture, then the business case.
One ecosystem
A rack of modules, an explorer, one module opened up, and a composition showing them chained.
02
Moving to Cloud
What teams stopped operating, and what idle now costs.
From Vapor to Cloud
Vapor is closed to new sign-ups and fully supported. What changes when a Vapor application moves to Cloud, and four teams' published results.
Leaving the server room
Eight teams moved from Forge, Heroku, AWS and their own servers to Laravel Cloud by choosing to stop operating servers; what each stopped running, in their own figures.
The 500ms wake
Flex compute on Laravel Cloud sleeps when idle and, on the new Flex sizes, wakes in under 500 milliseconds by restoring a checkpoint, with the database and cache waking on the first connection.
03
Enterprise
Isolation, data and the audit trail.
Private Cloud
Laravel Private Cloud is the same Cloud in a building of its own, and this story sets out when a team needs one and when shared Cloud is enough.
Private Cloud with PlanetScale
Laravel works directly with PlanetScale to bring its Postgres to Private Cloud customers at scale: what has been said, what has shipped, and Sportmonks running it at 600 million requests a week.
Choosing a database
The databases and stores a Laravel application can use on Cloud, and the context in which each is the right choice.
Ready for the audit
A dated compliance ledger for Laravel Cloud, Private Cloud and Nightwatch that says which attestation covers which product and plan, and the controls behind them.
04
Choosing a home
One application, three good homes, and when to choose each.
One app, three homes
One Laravel application on Laravel Cloud, on Forge with Laravel VPS, and on Vapor for existing customers: what stays the same, what each home operates, and when to choose each.
05
Capabilities
Two things the framework and the platform do together.
Agent ready
What a coding agent can read in a Laravel application, what it can call in the app and on Cloud, and what still waits for a person.
Realtime without a vendor
Broadcasting, Reverb and Echo are framework contracts and the WebSocket server is a resource you attach on Cloud: one event walked from ShouldBroadcast to the browser.
06
For talks
An opener for a room.
The year in Laravel
The tech tree as a conference opener: seven ages from 2011 to the next, the packages each one brought, and the platform age that Cloud opened.