Overview
plnt is the orchestration runtime for micro-agent workflows on Kubernetes. Pick a workflow from the registry, pick a GPU backend, and plnt handles the Helm deploy, canary, smoke test, and rollback — as a durable Temporal saga.
What you get
Section titled “What you get”- One CRD —
WorkflowRun.kubectl applyis the entire deploy trigger. - One saga — a Temporal workflow drives every run: pull spec → resolve backend → helm install canary → smoke → promote or rollback.
- Pluggable workflows — pull from microagents or any S3/OCI registry.
- Pluggable backends — any Kubernetes cluster with GPU nodes. Same YAML runs on kind, GKE, EKS, on-prem.
- One playground URL — play.plnt.work — pick a workflow, watch the step DAG, invoke it.
What it isn’t
Section titled “What it isn’t”- Not a workflow framework. plnt doesn’t compete with Argo, Temporal, or Airflow — it stands on top of Temporal and deploys workflow runners.
- Not a control plane SaaS. Everything runs on your cluster. No plnt.com account.
- Not a workflow authoring tool. Workflows are authored in microagents (or any registry that speaks the pull path).
Where to start
Section titled “Where to start”- Just want to try it locally? Quickstart — 60 seconds, no cluster.
- Building against it? Local dev — API + site side-by-side.
- Curious how it works? Architecture.
- Ready to ship it? Kind demo for laptop, DO K8s runbook for prod.
Related repos
Section titled “Related repos”- plnt — the runtime (this repo).
- microagents — the workflow registry.
- maps-micro-saas — reference consumer product (Google Maps profile copilot).
- plnt-site — this marketing site + interactive playground.