CLI

Everything Planton does, from your terminal: validate a manifest before it touches your cloud, deploy one component or a whole directory in dependency order, stream the Infra Job as it runs, install an Infra Chart, and bring in what already exists.

For the engineer who lives in a shell, and the pipeline that runs without one.

How It Works

1

Install

One Homebrew line on macOS; direct downloads for Linux and Windows.

2

Write the Manifest

The shape you already know: apiVersion, kind, metadata, spec. Validation catches a wrong field in seconds, before anything is created.

3

Apply

Deploy one manifest or a directory of them in dependency order, the way you already apply Kubernetes manifests, on every cloud.

4

Watch the Record

The Infra Job streams as it runs. The same event stream drives the console and the audit log, so every surface tells one story.

What You Get

Shipped behavior, stated as it works today.

The Exit Path Is the Same CLI

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.

The Same Rules at Every Door

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.

The Same Statement on Every Surface

The verified cost, the permission policy, and the controls print in your terminal word for word as they show in the console: one statement, stamped by the server, on every surface.

Inside GitHub Actions

The install and login actions put the same CLI inside a workflow, so a pipeline deploys the way a person does.

postgres.yaml

apiVersion: kubernetes.planton.dev/v1alpha1kind: KubernetesPostgresmetadata:  name: my-first-postgresspec:  namespace:    value: my-first-postgres  createNamespace: true  container:    replicas: 1    diskSize: 1Gi

Install, write, apply

brew install plantonhq/tap/plantonplanton apply -f postgres.yaml

Install, write the manifest above, apply. Validation fails a wrong field before anything touches your cloud. The manifest and the command are from the repository README.

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 →

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.