Vapor · Laravel on Lambda · Field-Guide-to-Laravel

A FIELD GUIDE TO LARAVEL · VOLUME II · THE ECOSYSTEM

ENTRY II.19 · SERVERLESS HOSTING

Vapor

Laravel\Vapor · Product · first recorded 13 August 2019, vapor-core and vapor-cli v1.0.0 on Packagist

Serverless Laravel on AWS Lambda, in your own AWS account. Closed to new sign-ups since September 2026; it runs on for existing customers indefinitely, and new projects start on Laravel Cloud. Each deploy is built on your machine or in CI, then uploaded.

Specification

Kind Hosting platform; new sign-ups closed, existing customers supported

Driver AWS Lambda behind API Gateway; SQS queues, CloudFront for assets

Runs on Your AWS account, linked by an IAM role; Vapor orchestrates it

Installed by composer require laravel/vapor-cli · laravel/vapor-core · vapor login

Voice vapor deploy · vapor rollback · vapor env:pull · vapor down

Scales by Lambda concurrency, typically 1,000 a region; warm keeps containers ready

Range Cloud: n/a: a home itself; where new projects start
Forge, VPS: n/a: the server-shaped alternative
Vapor: this sheet; closed to new sign-ups Sep 2026

Neighbours

Laravel Cloud is where new projects start: containers Laravel operates, with a migration guide from Vapor. Private Cloud is Cloud in a dedicated AWS account that Laravel maintains. Vapor's distinction is Lambda in your own AWS account, which Vapor orchestrates and you own.

Laravel Cloud II.38Private Cloud II.44

Field marks

vapor.yml
laravel/vapor-core
VAPOR_API_TOKEN
.env.production.encrypted

Fig. II.19.1 · One deploy, exploded

Parts

1 Build. Where vapor deploy runs, your machine or CI. build hooks run there; out comes a Lambda package or Docker image.

2 Deploy hooks. php artisan migrate --force and the rest run against the new version before it goes live; a failure stops it.

3 Lambda. The function, behind API Gateway. Default web timeout 10 s; the gateway caps at 30 s, Lambda at 15 minutes.

4 Assets. The public directory goes to S3 and is served by CloudFront; only changed files are uploaded on later deploys.

5 Environment. Variables and secrets are pinned to a deployment; vapor rollback restores them. Lambda caps them at 4 KB.

Hidden joinery

Only changed assets are uploaded; the rest are copied from the previous deployment. Octane on Vapor keeps the app in memory between requests, on Lambda rather than Swoole, RoadRunner or FrankenPHP. The scheduler runs by default with a DynamoDB lock against overlap. Amazon Linux 2 left maintenance on 30 June 2026; use AL2023.

Every line checked against docs.vapor.build, Packagist, The Monitor and the Cloud team on 2026-10-08.

TITLE

Vapor · Laravel on Lambda

SOURCES

docs.vapor.build/introduction · docs.vapor.build/projects/deployments · docs.vapor.build/projects/environments · docs.vapor.build/resources/queues · docs.vapor.build/resources/migrate-to-cloud · packagist.org/packages/laravel/vapor-core · packagist.org/packages/laravel/vapor-cli · laravel.com/blog/one-minute-or-less-how-we-built-laravel-clouds-architecture · Laravel Cloud team statement, 8 October 2026: Vapor runs on for existing customers indefinitely · laravel.com/cloud/docs/private-cloud · Monitor 227, 746, 699

STATUS

Verified · 2026-10-08

SHEET

II.19 of 48

REV

A · 2026-10-08

DRAWN

FINISH

All faces, including the back