Rules That Hold Before Anything Exists
The Self-Service Cloud Platform, for Security and Governance Leaders
Agents create infrastructure faster than your scanners find the problems. Prevention has to happen where creation happens.
You own the posture of an estate you did not build, and the tools you have tell you what went wrong after it did.
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.
What Decides It
Prevention at the Write Boundary
Budgets, protected environments, a curated catalog, and managed secrets hold before anything exists, whether the request came from a person, a script, or an agent.
Controls Stated, Never Asserted
Every covered component states which of 17 technical controls it enforces, with evidence for each claim, and never calls itself compliant.
A Record of Every Change
Every change is one immutable stack job, queryable by resource, environment, time, and outcome, with identity tags on every resource it created.
Your Rules Hold No Matter Who Asked
The rules are enforced at the one place infrastructure is created, so a coding agent cannot do what a person could not, and the refusal is identical at every door.
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 pause before anything deploys, and nobody approves work they initiated, the assistant included.
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.
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 record the product shows. Figures marked est. are examples; a real record carries its own.
Verified Before It Exists
Least-privilege permissions derived from exactly what is composed, and the technical controls each component enforces, stated with evidence before it exists.
The least-privilege permission policy is derived from exactly what is composed, per component kind.
Every covered component states which of a fixed list of 17 technical controls it enforces, with evidence for each claim.
The console, the CLI, and the assistant render the same server-stamped statement word for word.
Control profile · S3 bucket
encryption at rest
enforced · every new object is encrypted at rest by default; an unencrypted object is not representable
customer-managed keys
exposed · set encryption.kms_key_id
encryption in transit
enforced · TLS on every request
no public exposure
enforced · public access blocked at the bucket
HIPAA 164.312(a)(2)(iv)
served by encryption at rest, customer-managed keys
SOC 2 CC6.1
served by no public exposure, role-based access control
verdict
none
An illustration of the record the product shows. Two crosswalk rows are shown; evidence is quoted from the component’s profile. There is no verdict that says compliant, because a component enforces controls and is never called compliant.
Every Deployment Leaves a Record
The immutable stack job: configuration, verdicts, approver, outcome, and identity tags on every resource created. Evidence that exists whether or not anyone asked.
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.
Every job is retained and queryable by resource, organization, environment, time, and outcome.
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 record the product shows. Figures marked est. are examples; a real record carries its own. Every deploy leaves one of these.
The Rest of the Story
The chapters that matter next, each with the page that tells it in full.
How It Compares
Posture platforms observe after the fact; Planton prevents at creation. They complement each other, and neither replaces the other.
How Planton Compares →Runs Where You Decide
Keyless connections mean no long-lived cloud credential is stored anywhere. Self-hosted runs on your cluster with a license that verifies offline.
Your Cloud, Your Keys →The Self-Service Cloud Platform
One platform in the customer’s own account, with one door every request goes through. That door is where the rules live.
Product →You Will Ask
Is this compliant with SOC 2 or HIPAA?
No component is ever called compliant, and no deployment gets a framework verdict. What you get is each component’s stated controls with evidence, and 4 framework crosswalks that map those controls to HIPAA, SOC 2, FedRAMP Moderate, and CIS AWS Foundations so your assessor can read them.
Security Posture →Which rules hold today?
Deployment budgets that pause a deploy exceeding them; protected environments that refuse self-approval; a catalog curated to the kinds you allow, refused identically at every door; sensitive fields that take only a managed secret. Every one is stated here as it works today.
Rules and Approvals →Does this cover what already exists in the account?
Infrastructure that already exists can be adopted and its live state imported and verified in one step; from then on it carries the same record as everything Planton created. Import recipes exist for S3 buckets, VPCs, security groups, and container registries, proven in a live round trip.
Import →Proof It Works
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.
Planton runs on Planton: its own infrastructure and the pipelines that ship it go through the platform. Open-Source Modules →
Read It for Another Role
Planton for Engineering Leaders
What your team deploys, proven before it exists: the cost, the rule that held, and the record, without a new team and without opening a console.
How Planton Fits Your Work →Planton for Platform Engineers
Self-service your developers and their coding agents cannot break: rules written once, cost and permissions verified before anything exists, a record of every deploy.
How Planton Fits Your Work →