KIMITSU
Declarative agentic
pipeline orchestration
Tools are pure functions. Agents are stateful processes. The pipeline is a declaration. Every boundary is an HTTP contract.
$curl -fsSL https://kimitsu.ai/install.sh | sh
macOS and Linux — Windows users: use WSL
01 // Architecture
┌─────────────────────────────────────────────────────────────┐
│ Internal Network │
│ │
│ ┌──────────────┐ ┌──────────────┐ │
│ │ Orchestrator │───▶│ Agent Runtime│ │
│ │ zero LLM │◀───│ worker pool │ │
│ │ calls │ │ MCP client │ │
│ └──────┬───────┘ └──────┬───────┘ │
│ │ │ │
│ │ ┌──────▼───────┐ │
│ └───────────▶│ LLM Gateway │──▶ internet │
│ │ sole egress │ │
│ └──────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
│
│ MCP (HTTP/SSE)
▼
┌─────────────────────────────────────────────────────────────┐
│ User-Provided Tool Servers (operator-managed) │
└─────────────────────────────────────────────────────────────┘02 // Quick links
Overview
Philosophy, core concepts, and how Kimitsu inverts the agentic model.
ACCESS →Installation
Binary install script and Docker Compose options. Up in minutes.
ACCESS →Quickstart
Run the hello-world pipeline end to end and understand every step.
ACCESS →YAML reference
Every field in every file kind — workflow, agent, server, gateway, env.
ACCESS →Tool servers
MCP servers as the atomic unit.
ACCESS →Runtime
Four container tiers, heartbeat protocol, state store, execution model.
ACCESS →