Docs › Ecosystem › kradle

kradle — Kubernetes-native Git forge (MVP)

**Packages:** @a5c-ai/kradle (core) + @a5c-ai/kradle-cli · **Version:** 6.0.0 · **Maturity:** MVP

**Maturity warning — read this first.** Kradle's own README describes it as an "executable MVP runtime and handoff package." Treat it as **early / MVP**: APIs, charts, and CRDs may change, and rough edges are expected. It is included here for completeness and forward planning, not as a hardened production system.

**Kradle is a Kubernetes-native Git forge runtime — Argo CD GitOps and Gitea-backed Git hosting — with a per-org dispatchable assistant. It lets you run a self-hosted forge where repositories, PRs, CI, and policy flow through Kubernetes-style custom resources.**

---

On this page

• What it is
• How it models a forge
• The per-org assistant
• Entrypoints
• How it fits the stack
• Example
• Next steps

---

What it is

Per its package description, kradle is a "Kubernetes-native Git forge runtime with Argo CD GitOps and Gitea-backed Git hosting." It ships:

• A Node runtime and an HTTP API server.
• Helm charts and CRDs (packages/kradle/charts/).
• A Next.js console (apps/web).
• A controller container.

---

How it models a forge

Repositories, PRs, CI, webhooks, policy, and UI flows execute through Kubernetes-style **custom resources**, reconciled by Argo CD and hosted on Gitea. The resource kinds include:

Repository, PullRequest, Issue, Review, Pipeline, Job, RunnerPool, WebhookSubscription, RefPolicy, BranchProtection, and more.

Because everything is a custom resource reconciled via GitOps, the forge's state is declarative and auditable.

---

The per-org assistant

The "built-in assistant, dispatchable in org namespaces" maps to a concrete API and chart set:

• **API:** POST /api/orgs/:org/agents/dispatch (kradle-cli README).
• **Charts:** assistant-stack.yaml, assistant-identity.yaml, assistant-org-secret.yaml, org-namespace.yaml (packages/kradle/charts/templates/).

In other words, each org namespace gets its own dispatchable agent/assistant stack.

---

Entrypoints

---

How it fits the stack

Kradle is an **adjacent product**: a hosting/forge plus agent-dispatch substrate. It integrates with the rest of the ecosystem as a place for repositories and CI to live with built-in agent dispatch, and exposes MCP (kradle mcp) so MCP clients (such as Claude Desktop) can drive it. See where it sits in the architecture.

---

Example

# Run the HTTP API locally (default port 3080)
kradle serve

# Expose kradle to an MCP client over stdio
kradle mcp

Dispatching the per-org assistant is an HTTP call:

POST /api/orgs/:org/agents/dispatch

Subcommand flags are governed by the repository CLI allowlist; run kradle <command> --help on your installed version for the authoritative surface.

---

Next steps

• **See where it sits:** Architecture & How It Fits Together
• **Ecosystem map:** Ecosystem Overview
• **Related agent runtime:** genty overview