Infra Hub
Cursor for Cloud Infrastructure
Describe what you need, watch it compose on a live canvas, see the monthly cost and the IAM policy before anything is created, deploy, and publish it as an Infra Chart — a template your team reuses.
For the platform engineer who publishes the templates, and the developer or coding agent who deploys them.
How It Works
Describe
Say what you need: in the console, from the CLI, or through your coding agent. Every kind is a typed schema, so a wrong field fails before it touches your cloud.
Compose
Watch it compose on a live canvas: the components, how they connect, what each needs from the others.
Verify
See the monthly cost with its coverage stated, the least-privilege policy, and the controls each component enforces. Nothing exists yet.
Deploy
One Infra Job, kept: the exact configuration, the cost fact, the verdicts, who approved, and what exists afterward.
Publish
Publish it as an Infra Chart, a template your team redeploys into the next environment. A prompt cannot be redeployed; a chart can.
What You Get
Shipped behavior, stated as it works today.
The Monthly Cost, With Its Coverage
Every deployment-changing job is born with a verified monthly cost: an exact figure with line items when the pricing rules can derive one, a range otherwise, and plainly “unpriced” when neither is possible. A zero never stands in for unknown.
Least-Privilege Permissions
The least-privilege permission policy is derived from exactly what is composed, per kind.
A Budget That Pauses a Deploy
An environment can carry a deployment budget. A deploy whose verified cost exceeds it pauses for a human decision, and who approved, when, and why is stamped on the record.
One Record per Change
Every job is retained and queryable by resource, organization, environment, time, and outcome.
An environment, composed
components
vpc · eks cluster · rds postgres · s3 bucket · iam role · dns record
verified cost
~$412/mo est. · 5 of 6 components priced, 1 usage-based
permissions
least privilege · derived from the 6 components composed
controls
6 of 6 kinds carry a control profile with evidence
budget
within the environment’s $600/mo est. deployment budget
published as
Infra Chart production-baseline · redeployable into the next environment
An illustration of the record the product shows. Figures marked est. are examples; a real record carries its own.
Where This Is Proven
The same claims, written for the person who signs, with the record beside each one.
Verified Before Deploy
Before anything is created, Planton states the monthly cost with its coverage, the least-privilege permissions, and the controls each kind enforces.
What It Proves →Rules and Approvals
Deployment budgets that pause a deploy, protected environments that refuse self-approval, a curated catalog, and sensitive fields that only take managed secrets.
What It Proves →The Record
Every infrastructure change is one Infra Job, kept and queryable with its configuration, cost fact, verdicts, approvals, and the snapshot of what exists afterward.
What It Proves →Read Next
Service Hub
Connect a repository and every push is built, containerized, deployed, and promoted in your environments’ order, with the result written back into GitHub.
Read More →Catalog
700+ catalog kinds across 8 providers, each with a cost fact sheet, a control posture with evidence, and least-privilege permissions; 18 Infra Charts.
Read More →