Your coding agent can already create cloud infrastructure. What it creates is unverified, unrecorded, and unrepeatable: nobody priced it, nobody checked the permissions, nothing remembers what was made, and the next environment starts from a blank prompt.

Planton turns your own cloud account into a self-service platform. AI designs the infrastructure, the platform verifies the cost and permissions before anything is created, and the design is published as an Infra Chart, a template your whole team can deploy. Your services then ship onto that infrastructure straight from Git. It sits beside the coding agent and the cloud CLI you already use; nothing about how you work changes.

• Infra Hub is Cursor for cloud infrastructure: describe what you need, watch it compose, see the monthly cost and the IAM policy before anything exists, deploy, and publish it as an Infra Chart.
• Service Hub is Vercel for backend, in your own cloud: connect a repository and every push becomes a running deployment, with the result written back into GitHub checks and deployments. No pipeline YAML, no Dockerfile required.

Every change Planton deploys is:

• Priced before it exists, with its coverage stated: an exact monthly figure with line items, a range, or plainly "unpriced". A zero never stands in for unknown. The least-privilege permission policy is derived from exactly what is composed, and every covered component states which of a fixed list of 17 technical controls it enforces, with evidence.
• Held to your rules no matter who asked. A deployment budget pauses a deploy whose verified cost exceeds it, for a human decision. Protected environments refuse self-approval. The catalog can be curated to the component kinds your organization allows. A sensitive field takes a managed secret, never a pasted value. The console, the CLI, and the coding agent see the same list and refuse the same things.
• Left behind as a record. One immutable stack job holds the exact configuration that was deployed, the cost fact, the budget verdict, who approved and why, and a snapshot of what exists afterward, queryable by resource, environment, time, and outcome.

Hosted at planton.ai, self-hosted on your own Kubernetes cluster with a license that verifies offline, or free on your laptop as Planton Desktop. In every shape it is your cloud account, your keys, your state, and your bill. Connections can be keyless, so no long-lived cloud credential is ever stored. If you leave, you take your manifests and keep deploying them with the open-source CLI.

Every infrastructure module is Apache 2.0. Audit it, fork it, or run it without the platform.

• Planton Desktop is free for individuals forever, commercial use included: planton.ai.
• Teach your coding agent: npx skills add plantonhq/skills, then read Coding Agents.
• From the terminal: brew install plantonhq/tap/planton, then the Getting Started guide.
• For a team: the hosted free tier needs no card, and nobody below the self-serve ceiling talks to sales. Pricing.

"As a junior DevOps engineer with almost no AWS experience, Planton enabled me to provide a very mature developer experience to our entire 7-person dev team. They can quickly deploy services to multiple environments without me having to deal with learning AWS from scratch or rewriting complex infrastructure code."

Sai Saketh, Junior DevOps Engineer, iorta TechNext

Teams have run production on Planton since 2023. Planton runs on Planton.

• Questions and ideas: Discord
• Bugs and requests: issues on plantonhq/planton
• Contributing: CONTRIBUTING.md and the CLA
• Documentation: planton.ai/docs

The code is Apache 2.0. The Planton name and logo are trademarks of Planton Cloud, Inc.; see TRADEMARKS.md.