plnt docs

plnt is the runtime that turns a micro-agent workflow spec + a Kubernetes GPU backend into a running service — with canary, smoke test, and rollback, all driven by a durable Temporal saga.

It sits in the middle of a three-repo stack:

• google-business — reference end-user product (Google Business Profile copilot). Consumes the runtime.
• microagents — public registry of workflow recipes. Pull path speaks S3 and OCI.
• plnt (this) — the runtime. WorkflowRun CRD → Temporal saga → Helm deploy.

Where to start

Quickstart

pip install, plnt playground up, first workflow run in 60 seconds. Start here →

Local dev

Run the playground API and the site’s UI on the same laptop. Set it up →

Architecture

The 4-layer stack — product, registry, runtime, backend. Read →

WorkflowRun CRD

The declarative deploy contract. kubectl apply is the trigger. Inspect →

Concepts

• Architecture — the 4-layer stack, where each piece lives.
• WorkflowRun CRD — the deploy contract.
• Orchestration saga — the Temporal workflow that drives every run.
• Runtime adapter — one Protocol, N backends.
• Playground API — the HTTP surface for interactive invocations.
• Glossary — vocabulary used across the code and docs.

Reference

• API contract — the invocation shape, enforced by tests.
• WorkflowRun schema — every field on the CRD.

Operations

• Kind demo — 60-second local-laptop demo, no cloud.
• DigitalOcean K8s runbook — ship playground.plnt.work end-to-end.
• Fly.io (API only) — cheap-and-cheerful path for the API layer.
• CI/CD — GitHub Actions running tests and publishing artifacts.