Hi everyone đź‘‹
A few weeks ago I shared Arco, an open-source CLI that deploys Laravel to AWS Lambda Web Functions with FrankenPHP + Octane, in your own AWS account. Thanks for all the questions and feedback, a lot of it went straight into what we built since.
What's new in the CLI (open source, now v0.19.1)
• Access log: request duration (p50/p95) per route, without extra services
• Request ids in every log line, so a web request, its queued jobs and its logs line up
• Starter template: a fresh Laravel app ready to deploy
What's new in Arco Cloud (the optional dashboard on top, in beta)
• X-Ray tracing: every request and queued job broken down step by step (Laravel boot, middleware, routing, each SQL query, AWS and HTTP calls, cold starts)
• Monitoring: errors grouped by type, log search with live mode, and per-function metrics, read from CloudWatch in your account
• Alerts on Slack and email when a deploy or a network fails
• AWS cost per environment, straight from Cost Explorer
• Run command: php artisan migrate (or any artisan command) from the browser, with output and history
• Queue panel: failed jobs and one-click dead-letter queue redrive
• Managed Aurora DSQL databases: IAM auth, no passwords, one cluster per environment, plus a guide to give your team a read-only role
• Private networks with a static outbound IP and free S3/DynamoDB endpoints
• Team 2FA, and a badge on every deploy showing whether it was built on GitHub Actions or our runners
Some numbers people asked for: across 64 deploys of our small test apps, the cold start of a fresh revision (FrankenPHP starting + Octane booting Laravel) is around 1.2-1.4 s median. After that, requests are served from memory, and one Web Function instance handles many requests at once, so you hit few cold starts in practice.
Everything still runs in your own AWS account. Arco Cloud never proxies your traffic.
Want to try it?
1. Sign up at https://staging.arcocloud.app
2. Click "Request beta access" and tell us about your project
3. I review every request myself and can help move a first app
Community: https://join.slack.com/t/arco-equipo/shared_invite/zt-4fi2aejbq-fzwl8U_4qeqSOxO6TtNoPg and GitHub Discussions at https://github.com/multi-api/arco/discussions
Repo: https://github.com/multi-api/arco
And a small ask: there's still no managed PHP runtime for Lambda. If you'd use one, a 👍 on this AWS roadmap issue helps: https://github.com/aws/aws-lambda-roadmap/issues/123
I'd love feedback, especially from anyone running Laravel on Vapor, Bref or their own Lambda setup: what would make you try this, and what's missing?

Arco CloudArco Cloud: Laravel on AWS Lambda, in your own AWS accountDeploy Laravel to AWS Lambda Web Functions in your own AWS account. Push to deploy, see your infrastructure as a map, roll back automatically. No idle cost, no markup on AWS.
commit 1ba34ee