Self-Hosted

The whole platform on your own Kubernetes cluster, installed with two Helm commands and run by an operator. Free for up to 5 seats; a 30-day evaluation of the full edition needs only an email.

For the platform team that wants Planton inside the same trust boundary as the infrastructure it manages.

What You Get

Shipped behavior, stated as it works today.

Two Commands, Everything

The operator first, then the platform at the release you name. From that one resource the operator runs the whole stack: the control plane, the console, the identity server, the secrets manager, the databases, and an in-cluster runner. No license key, no admin account, no database, no values file.

A License That Verifies Offline

A license key is a signed proof of purchase the deployment verifies entirely offline: no network call, no phone-home. The community edition underneath is free: the whole platform, with one limit on how many people can join.

Expiry Never Bricks

The seat limit applies to people joining, never to the people already there. An install that holds more people than the community edition allows keeps every one of them working; a lapsed key never reaches into a running deployment.

Or Through Infrastructure as Code

The same two steps exist as catalog resources, so an agent or a pipeline installs Planton the way it installs everything else: two manifests, applied in order, through OpenTofu or Pulumi.

Several Plantons, One Cluster

Platforms are namespaced and one operator serves the whole cluster, so staging and production, or one platform per team, run side by side.

Guided From the Desktop

Planton Desktop offers the same install as a guided experience: pick a cluster from your kubeconfig, preflight it, choose the front door, and watch the install converge.

planton.yaml

apiVersion: kubernetes.planton.dev/v1alpha1kind: KubernetesPlantonPlatformmetadata:  name: planton  annotations:    planton.dev/provisioner: tofuspec:  namespace:    value: planton  createNamespace: true  version: <release>

Install

helm install planton-operator oci://ghcr.io/plantonhq/charts/planton-operator \  --namespace planton --create-namespacehelm install planton oci://ghcr.io/plantonhq/charts/planton \  --namespace planton --set platform.spec.version=<release>

Two Helm installs, the operator first; or apply the operator and platform manifests through the CLI in the same order (the platform’s is shown above). The guide lists the published releases. From the Self-Hosting guide.

What Stays Yours

In this shape, and in every other one.

The cluster, and everything the operator runs in it: records, secrets, deployment history, cloud credentials. Nothing leaves.
The release: you choose when to upgrade, and to which published release.
The license, verified against embedded public keys, with no call home.
The manifests. If you leave, the open-source CLI keeps deploying them.

The Other Shapes

Hosted

The control plane at planton.ai; every deploy in your own cloud account, under your own keys, with nothing to run. Free for up to 3 seats with no card.

Planton Desktop

The whole platform on your laptop, deploying to your own cloud with the sign-ins already on your machine. No account. Free for individuals, commercial use too.