CLI

Everything Planton does, from your terminal

Context-switching between terminal, console, and CI. Different tools for different operations. Copy-pasting YAML between systems.

kubectl-inspired commands, manifest-driven workflows, and real-time infrastructure operations — all from one CLI.

planton cli

$ brew install plantonhq/tap/planton
✓ planton 0.15.0 installed
 
$ planton apply -f postgres.yaml
▶ Applying GcpCloudSqlInstance/my-postgres
Organization: acme-corp
Environment: production
 
⏳ Creating stack job...
✓ Stack job sjb-d4f21a created
⏳ Provisioning resources...
✓ GcpCloudSqlInstance created in 3m 12s
Homebrewbrew install plantonhq/tap/planton
curlcurl -fsSL https://get.planton.ai | sh

1

CLI

0

Context Switching

< 1 min

Install Time

0

Config Required

Manifest-Driven

Deploy any cloud resource or service from YAML. Same manifests work in CI, in console, from terminal.

`planton apply -f manifest.yaml` — one command for any resource type

Validated against typed protobuf specs before submission

Diff preview before apply — see exactly what will change

Works identically in local terminal, CI pipeline, and console

planton apply

$ planton apply -f postgres.yaml
 
▶ Applying GcpCloudSqlInstance/my-postgres
Organization: acme-corp
Environment: production
 
⏳ Creating stack job...
✓ Stack job sjb-d4f21a created
⏳ Provisioning resources...
✓ GcpCloudSqlInstance created in 3m 12s
 
Connection string written to:
planton secret get my-postgres-conn-url

Kubernetes Access

Access any connected cluster without kubeconfig files. IAM-scoped, auditable, zero local configuration.

`planton kubectl` — proxy through Planton with org-level RBAC

No kubeconfig files, no VPN tunnels, no local credential management

Cluster auto-discovery from your connected providers

Full audit trail of every kubectl command executed

planton kubectl

$ planton kubectl --cluster prod-us-east-1 \
get pods -n backend
 
NAME READY STATUS
api-server-7d4f8b-x9k2m 1/1 Running
worker-5c8a9f-p3n7j 1/1 Running
scheduler-6b2e1d-m8w4r 1/1 Running
 
# No kubeconfig files. No VPN.
# IAM-scoped, auditable access.

Your infrastructure, one command away

From deploying resources to streaming logs to managing secrets — the Planton CLI covers your entire workflow.

Stack Job Operations

Stream IaC execution logs in real-time. Preview, apply, destroy from command line.

planton stack-job watch
planton stack-job list
planton stack-job cancel
planton stack-job retry
⏳ Previewing changes...
  ~ gcp:sql:DatabaseInstance (update)
    + availabilityType: "REGIONAL"

✓ Preview complete. 1 resource.
✓ Update complete in 2m 34s.

Connection Management

Create, list, and manage cloud connections. Guided setup for every supported provider.

create
list
inspect
rotate

Self-Update

Built-in update mechanism. Always run the latest version with a single command.

v0.14.2

Current

v0.15.0

Latest

Local dev, production secrets

Pull environment variables for local development. Secrets resolved securely from your vault — never stored in plaintext.

planton service dot-env

$ planton service dot-env \
--service api-server --env dev
 
DATABASE_URL=postgres://...
REDIS_URL=redis://...
API_KEY=sk-...
STRIPE_SECRET=whsec-...
 
✓ 12 variables written to .env
4 secrets resolved from vault

Secrets Resolved Securely

Secrets are fetched at runtime from your vault, never stored in plaintext on disk.

Environment-Specific

Separate variable sets for dev, staging, and production. Switch with a single flag.

Vault Integration

Works with AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault, and more.

console.planton.ai

Planton CLI — Manifest-driven workflows and real-time streaming

One CLI, every operation

Install in seconds, deploy in minutes

brew install plantonhq/tap/planton — then apply your first manifest. Same commands work locally, in CI, everywhere.


©2026 Planton Cloud Inc. All Rights Reserved.