Import
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.
For the team that already has an account full of infrastructure and no intention of redeploying it.
How It Works
Adopt
Register the resource in Planton without deploying anything. Nothing in your cloud is touched, and the page says so: adopted, not yet deployed.
Import
From the resource’s page or the CLI, name the provider resource that already exists. Import only writes state; the provider resource itself is never modified.
Verify
A wrong import fails before it lands. Import never writes a configuration it did not apply.
Continue
From then on the resource carries the same record as everything Planton created: every change one Infra Job, kept.
What You Get
Shipped behavior, stated as it works today.
Proven in a Live Round Trip
Import recipes exist for S3 buckets, VPCs, security groups, and container registries, proven in a live round trip.
Nothing Is Touched Until You Say
Adopting runs no job and changes nothing. The import itself only writes state; the provider resource is never modified.
From the Terminal Too
The CLI imports with the same verification, and a dry run prints the native command it would run without creating a job.
Tagged Like Everything Else
Every resource Planton creates in your cloud carries identity tags naming its organization, environment, kind, and id.
An import, verified
resource
AwsS3Bucket · media-archive · adopted, not yet deployed
operation
state import · identifier derived by recipe
verify
refresh, then preview · 0 changes pending
state
written once, only what was applied
record
Infra Job kept · queryable by resource, environment, time
An illustration of the record the product shows.
Where This Is Proven
The same claims, written for the person who signs, with the record beside each one.
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
Infra Hub
Describe what you need, see the monthly cost and the IAM policy before anything is created, deploy, and publish it as an Infra Chart your team reuses.
Read More →CLI
Everything Planton does, from your terminal: validate a manifest, deploy a component or a directory in dependency order, stream the job, install an Infra Chart.
Read More →