Runkite Docs

One place for what the plane does, why each feature exists, how to implement it, how it looks in Admin, and what you should expect. Reference markdown still lives in docs/ on GitHub — these pages are the product guide.

Onboard (enterprise path)

• Try it — demo (Admin has no login here)
• Admin login — what to paste; why read/write keys fail
• Admin UI guide — every dashboard screen, what it's for and how to use it
• Credentials map — Admin vs client vs runner vs connectors
• Install · Production day-0
• First agent · Migrate agents
• Feature map — Admin ↔ Docs matrix

Build

• Install — Supported profile, compose, Helm
• Agents — register & run Python / TypeScript graphs
• Framework matrix — LangGraph, CrewAI, LlamaIndex, AutoGen, LangChain
• Checkpoints — opaque durable state
• Connectors — run-bound sessions & MCP proxy
• Registry — publish & search agent definitions

Operate

• Runs & threads — monitor, stream, cancel
• Cron — scheduled fires with multi-replica claims
• Webhooks — outbound events & dead letters
• Ops — reclaim, secrets, day-2

Govern

• Grants & HITL — policy grants, argument predicates, pending queue, approve/deny
• PDP / Cedar — bring your own decision point
• Kill & break-glass — emergency stop & timed bypass
• Security — tenancy, auth, audit posture
• Spend (FinOps) — spend controls on the plane

Connect

• A2A coordination — agent calls agent via the plane
• Protocols — Agent Protocol vs Runner Protocol

Deep

• Why a plane · Scenario · Limitations
• Chapters · Blog · Decisions · Engineering notes

Template on every guide: What · Why · How · In product · Expect. Admin screenshots are the real UI surfaces for that page.