⚡

Serverless, then signups closed.

Laravel Vapor alternative for PHP hosting

Q: Is Laravel Vapor shutting down?

No new signups - Vapor takes no new signups. Existing customers can still sign in, and Laravel points them to Laravel Cloud for migration.

Q: Do queues and the scheduler work without SQS?

Yes - Laravel's database queue driver runs on MySQL, with a worker and a cron job for the scheduler, both set in the dashboard.

Laravel Vapor runs Laravel on AWS Lambda and takes no new signups. Existing projects keep running, with Laravel Cloud as the official way out. Consider fortrabbit.

Try for free

7 days free trial

See pricing

Built by

Built with

Built what

Built how

About Laravel Vapor

Laravel Vapor is the serverless platform from Laravel, revealed in 2019. It deploys Laravel to AWS Lambda in the customer's own AWS account, with SQS for queues, S3 for files, CloudFront for assets and RDS or Aurora Serverless for the database. The subscription costs $39 a month, plus the AWS bill. Vapor no longer accepts new signups, and Laravel's migration docs point to Laravel Cloud.

Why not Laravel Vapor?

No new projects can start on Vapor. Existing projects run on, with Lambda limits to plan around: a temporary filesystem, timeouts, no Horizon, and two bills, one from Laravel and one from AWS.

Why fortrabbit

fortrabbit runs Laravel as a regular PHP app on AWS, with no AWS account on the customer's side. Git push deploys, Composer and npm in the build, MySQL as a component, a persistent disk, and the scheduler and queue workers as jobs. Laravel Cloud is the other way out, compared on its own page.

Vapor and fortrabbit

Feature	Laravel Vapor	fortrabbit
New signups	Closed	Open
Runtime	AWS Lambda	PHP containers
Bills	Vapor and AWS	One
Queues	SQS	Database driver, workers
Filesystem	Temporary, S3	Persistent storage
Database	RDS, Aurora Serverless	MySQL component

Different by design #

Pay in arrears

Daily prorated, post-paid billing. No upfront payment, no yearly commitment.

Modular pricing

Pay per component and scale each one from xs to 2xl on its own.

No dark patterns

No vendor lock-in, no upselling, no misleading messages.

Humans in support

Eye-level developer chat over the support bubble. No sales calls.

Developer-first

Git-push deploy, SSH access, bring your own code. No 1-click bloat.

Managed platform

A hardened, service-oriented PHP stack. Deploy code, skip the server admin.

Frequently asked #

Is Laravel Vapor shutting down?

No new signups

No new signups - Vapor takes no new signups. Existing customers can still sign in, and Laravel points them to Laravel Cloud for migration.

Does fortrabbit need an AWS account?

No - Vapor deploys into the customer's AWS account, billed by AWS on top of the Vapor subscription. fortrabbit runs on AWS too, with one bill from us.

Do queues and the scheduler work without SQS?

Yes

Yes - Laravel's database queue driver runs on MySQL, with a worker and a cron job for the scheduler, both set in the dashboard.

What customers say #

Having fortrabbit is like having a dedicated DevOps engineer on the team, taking care of the infrastructure so we can focus on writing code. We've used many PaaS providers, but none come close to fortrabbit's mix of features, reliability, predictable and fair pricing, and fast, genuinely helpful support. Their service has been rock solid, giving us the confidence that our apps are in good hands.

Len van Essen

CTO at Fitwinkel

2026 — Direct feedback

Unmatched performances and ease-of-configure. I really like what fortrabbit is doing for the modern PHP hosting ecosystem, and I'd suggest anyone to have a try with them.

Federico Magnani

CTO at glueglue