Planton · The Self-Service Cloud Platform
Your coding agent can already create cloud infrastructure. Planton makes it verifiable, recorded, and reusable.
It sits beside the coding agent and cloud CLI you already use. Verifiable: cost, permissions, and controls checked before anything exists. Recorded: every change kept where you can query it. Reusable: a template your team redeploys.
Hosted is free for up to 3 seats, no card. Desktop is free for individuals, commercial use included.
Planton Desktop
What do you want to build?
A production environment on AWS: private VPC, ECS services behind a load balancer, RDS PostgreSQL encrypted with our own KMS key.
AWS VPC
No charge
NAT Gateway
~$33/mo est.
Application Load Balancer
~$16/mo est.
ECS Service
Usage-based
RDS PostgreSQL (Multi-AZ)
~$122/mo est.
KMS Key
$1/mo est.
verified cost
~$172/mo est. · 5 of 6 priced
permissions
least-privilege policy · 14 actions
controls
encryption at rest · encryption in transit · no public exposure
An illustration of the shape. Figures marked est. are examples; a real deploy carries its own.
Deploys to 8 providers, among them
What the Agent Leaves Behind
Developers still wait and platform teams still queue, and the agent that was meant to end the wait has added a new kind of risk.
Unverified
Nobody priced it before it existed, and nobody checked what permissions it was given.
Unrecorded
Nothing remembers exactly what was made, by whom, or why. The transcript is not a record.
Unrepeatable
The next environment starts from a blank prompt, and staging will not match production.
The Self-Service Cloud Platform
Planton turns your own cloud account into a self-service platform. AI designs the infrastructure, verifies the cost and permissions before anything is created, and publishes it as templates your whole team can deploy. Your services then ship onto that infrastructure straight from Git.
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.
Infra Hub →Service Hub
Vercel for Backend, In Your Own Cloud
Connect a Git repository and every push becomes a running deployment — no pipeline YAML, no Dockerfile required, with results written back into GitHub checks and deployments.
Service Hub →Your coding agent reaches Planton through the Planton skills and the Planton MCP server, or through the CLI. It sits beside the tools you already use; nothing about how you work changes. Connect Your Agent →
Verified Before It Exists
Before anything is created, Planton tells you what it will cost each month with its coverage stated honestly, which permissions it needs and no more, and which technical controls the components enforce. Proof at creation, not detection after.
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 component kind.
The Controls Each Component Enforces
Every covered component states which of a fixed list of 17 technical controls it enforces, with evidence for each claim.
Before deploy
verified cost
~$172/mo est. · 5 of 6 components priced, 1 usage-based
catalog release
2026.09.2 · prices verified against provider documents
against today
+$16/mo est. · the load balancer is new
permissions
least-privilege policy · 14 actions · ready to download
controls
encryption at rest · encryption in transit · no public exposure
uncovered
none of the 6 components is without a control profile
An illustration of the shape. Figures marked est. are examples; a real deploy carries its own.
Your Rules Hold No Matter Who Asked
A platform team writes the rules once and every request obeys them, whether it came from a person in the console, a script on the CLI, or a coding agent at two in the morning.
Deployment Budgets
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.
Protected Environments
Protected environments pause before anything deploys, and nobody approves work they initiated, the assistant included.
A Curated Catalog
The catalog can be curated to the component kinds your organization allows. The console, the CLI, and the agent all see the same list and refuse the same things, because one answer serves both.
Secrets Stay Secret
A field the schema marks sensitive takes a managed secret. There is no way to type a raw secret into it.
Deploy paused
requested by
coding agent, on behalf of s.rao
environment
prod · protected · budget $250/mo
verified cost
~$312/mo est.
verdict
over budget by ~$62/mo · paused for a decision
who may approve
anyone with approve access on prod · never the requester
resolution
approved by a.patel · 2026-09-17 09:14 · “the replica is intentional”
An illustration of the shape. Figures marked est. are examples; a real deploy carries its own.
Every Deployment Leaves a Record
Every change to infrastructure runs as one stack job, and every stack job is kept: the exact configuration that was deployed, the cost fact, the budget verdict, who approved and why, who triggered it, what happened in every phase, and a snapshot of what exists afterward.
The Configuration, Frozen
The full configuration is embedded into the job when it is created, and the job is immutable: the resource may change later; the job never does.
Kept and Queryable
Every job is retained and queryable by resource, organization, environment, time, and outcome.
One Stream, Every Surface
One event stream drives the console, the CLI, and the audit log, so every surface tells the same story.
Tagged in Your Cloud
Every cloud resource Planton creates carries identity tags naming its organization, environment, kind, and id.
Deploy record
deploy
production environment · prod · succeeded
requested by
coding agent, on behalf of s.rao
approved by
a.patel · 2026-09-17 09:14 · “the replica is intentional”
configuration
embedded at creation; never changes
verified cost
~$312/mo est. · catalog 2026.09.2
phases
init · refresh · preview · apply · capture
snapshot
7 resources · tagged planton.ai/environment=prod
An illustration of the shape. Every deploy leaves one of these.
Services Ship from Git
Once the infrastructure exists, your services ship onto it straight from Git. Connect a repository; every push is built, containerized, and deployed, with the result written back into GitHub as checks and deployments.
Build
No pipeline YAML and no Dockerfile required.
Promote
Builds can be manual, from a branch, or from an exact commit; promotion follows the order your environments declare; protected environments carry a manual gate.
Protect
A rejected environment is never touched, and a service with deployments in a protected environment refuses deletion outright.
Cost
Runner minutes are never billed.
Service run
push
main · a41f2c9 · “add the invoices endpoint”
build
buildpacks · 2m 04s · image pushed
deploy
dev · succeeded · 1m 12s
promote
staging succeeded · prod paused (protected)
github
check planton/deploy passed · deployments dev, staging
An illustration of the shape; times are examples.
Bring What You Already Have
You do not start from an empty account. Infrastructure that already exists can be brought under Planton’s record without being redeployed: it is adopted, its live state is imported and verified in one step, and from then on it carries the same record as everything Planton created.
Adopt Without Redeploying
Create and update can track a resource without deploying anything; it reads honestly as adopted, not yet deployed.
Import, Verified Atomically
A state import is verified atomically: a wrong import fails before it lands, and import never writes a configuration it did not apply.
Recipes for the Common Kinds
Import recipes exist for S3 buckets, VPCs, security groups, and container registries, proven in a live round trip.
Import
resource
S3 bucket · billing-exports · existing
state
adopted, not yet deployed
import
verified · live state matches the manifest · 0 changes planned
record
from here on, every change is a stack job
An illustration of the shape.
Runs Where You Decide
Planton runs where you decide: 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.
Hosted
Free for Up to 3 SeatsSign up at planton.ai and connect your cloud. Your account, your keys; Planton holds the record.
Start Free →Self-Hosted
Free for Up to 5 SeatsThe whole platform on your own Kubernetes cluster, community edition free; a license key that verifies offline for larger teams.
Licenses →Planton Desktop
Free for IndividualsWhen you become a team, nothing is redone: the same manifests and model on planton.ai or your own cluster.
Planton Desktop →Keyless Connections
Connections can be keyless: a short-lived, connection-scoped identity token is minted at the moment of use and exchanged by the cloud for temporary credentials. Nothing is stored, nothing is rotated, and the trust is yours to revoke.
Open Source, and the Way Out
Every infrastructure module is open source under Apache 2.0. If you leave, you take your manifests and keep deploying them with the open-source CLI.
Secrets on the Desktop
On the desktop, secrets are encrypted locally with the key in your OS keychain and resolved on the runner at the moment of use.
Who It Is For
The platform engineer is the user: they write the rules, curate the catalog, publish the Infra Charts, and hand developers and agents a self-service platform that cannot break those rules. The engineering leader is who signs: what reaches them is the proof.
Platform Engineer
Agents can already create infrastructure in your account. You cannot see what they made, what it costs, or whether it follows the rules you wrote down last quarter.
How Planton Fits Your Work →Engineering Leader
Your team says the agents are making them faster. Nobody can show you the cost of what was created before it was created, or who approved it.
How Planton Fits Your Work →IT Consultancy
Every client starts from zero, and the last client’s Terraform does not fit this one.
How Planton Fits Your Work →Startup Founder
Your agent can build the infrastructure. You are not sure what it built, what it will cost next month, or how you will do it again for staging.
How Planton Fits Your Work →Security and Governance Leader
Agents create infrastructure faster than your scanners find the problems. Prevention has to happen where creation happens.
How Planton Fits Your Work →Proof It Works
Teams have run production on Planton since 2023. Here is what the people running it say, in their own words.
700+
Component Kinds
8
Providers
17
Controls with Evidence
Since 2023
In Production
Catalog figures counted from the open-source repository on 2026-09-17 (github.com/plantonhq/planton); 2023 is the year the first customer went to production.
Rohit Reddy Gopu
CEO
“For one client project where the client mandated GCP but our DevOps engineer had no GCP experience, Planton allowed us to successfully deliver the entire infrastructure. We essentially got full DevOps capabilities for GCP without needing GCP expertise on our team.”
Sai Saketh
Junior DevOps Engineer
“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.”
Balaji Borra
DevOps Engineer
“Planton has dramatically improved my efficiency. I no longer have to deal with the grunt work of rewriting Terraform configurations between client projects. I can now manage multiple client environments simultaneously and provide a much better experience for all the developers I support.”
Rakesh Kandhi
Senior Developer
“The dot-env file generation for services feature in Planton's ServiceHub been super helpful for me. I can now update service configurations without having to ping Balaji every time. Even better, creating new services and deploying them to dev, staging, or prod is completely self-service. I don't need to wait for DevOps anymore.”
Planton runs on Planton: its own infrastructure and the pipelines that ship it go through the platform. Open-Source Modules →
Where It Sits, and Where to Start
Beside Governance Tools
Prevent at creation versus observe after: a complement to posture tools, never a replacement.
Beside Terraform
Your Terraform stays yours: the modules are open-source Terraform and Pulumi, and what you already run is adopted, not rewritten. Every covered component reports its controls against the same fixed list, so what you check is one vocabulary, not each kind’s field names.
Beside a Portal
The execution layer behind the catalog: it deploys, with the record attached.
Start free today. Planton Desktop is free for individuals forever, commercial use included. The hosted free tier is free for up to 3 seats with no card. The self-hosted community edition is free for up to 5 seats, and a 30-day evaluation of the full edition needs only an email.