Features
Move at agent speed. Until you shouldn't.
Agents make infra fast — and unreliable. Recipes come with real guardrails, and Cloud Fabric checks every change against your live account graph — so the one change that would take production down is the one that doesn't ship.
The primitive
Recipes: one unit of production-ready infra
A Recipe is a new infra primitive — it composes IaC templates, CDK glue, and CloudFormation into a versioned, metadata-rich unit that stands up a production-ready three-tier ECS architecture, with networking, security, and observability baked in.
You deploy or import a Recipe. You don't hand-assemble IaC, CI, and IAM — and you don't start from a blank AWS console.
01 — The ask
"Tighten the ALB's TLS policy to TLS 1.2+ for SOC 2 compliance."
02 — Without LaunchPaaS
The new TLS policy breaks the listener your ECS service sits behind. Tasks fall out of the target group, traffic dies — and the first one to notice is a customer.
2nd Day Ops
Cloud Fabric keeps the whole account coherent
Recipes rarely live alone. LP Cloud Fabric composes recipes that interact and runs 2nd Day Ops — reconciling against a live dependency graph of your real account, including resources you built by hand or with any IaC (Pulumi, Crossplane, CloudFormation, and more).
Change one thing and you know what it touches: updates and deletes are checked for blast radius before they run.
OR — see how it works with LaunchPaaS
02 — With LaunchPaaS
Claude issues the same change through Cloud Fabric over MCP — which checks it against the live account graph first.
VPC
Subnet · used by ECS cluster
ECS Cluster · not affected
03 — Before apply
Cloud Fabric returns the blast radius and holds the change until it's reconciled. The ECS service and task were never at risk — and no one heard about it from a customer.// the ALB isn't even LaunchPaaS-managed — the account graph caught it, traced the change into the ECS service and task inside the cluster, and left the cluster, subnet, and VPC themselves untouched.
Built for agents
Every capability, callable over MCP
AI agents make infra fast — but unreliable. LaunchPaaS exposes the whole primitive — deploy, import, reconcile, provision — over MCP, behind the same guardrails a person gets.
An agent gets high-context, metadata-rich infrastructure and dependency-graph checks — not a blank console and hope.
- Deploys into your own AWS account
- Real IaC — you own the code
- Secure cross-account role, no vendor cloud
- Import existing infra · adopt incrementally
Real ownership
Your AWS account. Real IaC. No black box.
Infrastructure lands in your own AWS account through a secure cross-account role — never a vendor-managed cloud. You own the IaC, the data, and the account.
Already on AWS? Import and manage what you have, and adopt LaunchPaaS at your own pace. Leave anytime — it's your cloud.
Grows with you
LaunchPaaS grows with your stack
Start with the foundation and add what you need, when you need it. Every service is provisioned into your own AWS account and wired into your stack automatically — no bolt-ons, no second control plane.
Stop Renting Infrastructure. Start Owning It.
Join product teams building on AWS with PaaS-level simplicity — and full control of their cloud from day one.