{
  "id": "page:docs-user-guide-ecosystem-kradle",
  "_kind": "Page",
  "_file": "wiki/docs/user-guide/ecosystem/kradle.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/user-guide/ecosystem/kradle.md",
    "sourceKind": "repo-docs",
    "title": "kradle — Kubernetes-native Git forge (MVP)",
    "displayName": "kradle — Kubernetes-native Git forge (MVP)",
    "slug": "docs/user-guide/ecosystem/kradle",
    "articlePath": "wiki/docs/user-guide/ecosystem/kradle.md",
    "article": "\n[Docs](../index.md) › [Ecosystem](./overview.md) › kradle\n\n# kradle — Kubernetes-native Git forge (MVP)\n\n**Packages:** `@a5c-ai/kradle` (core) + `@a5c-ai/kradle-cli` · **Version:** 6.0.0 · **Maturity:** MVP\n\n> **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.\n\n**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.**\n\n---\n\n## On this page\n\n- [What it is](#what-it-is)\n- [How it models a forge](#how-it-models-a-forge)\n- [The per-org assistant](#the-per-org-assistant)\n- [Entrypoints](#entrypoints)\n- [How it fits the stack](#how-it-fits-the-stack)\n- [Example](#example)\n- [Next steps](#next-steps)\n\n---\n\n## What it is\n\nPer its package description, kradle is a \"Kubernetes-native Git forge runtime with Argo CD GitOps and Gitea-backed Git hosting.\" It ships:\n\n- A Node runtime and an HTTP API server.\n- Helm charts and CRDs (`packages/kradle/charts/`).\n- A Next.js console (`apps/web`).\n- A controller container.\n\n---\n\n## How it models a forge\n\nRepositories, 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:\n\n`Repository`, `PullRequest`, `Issue`, `Review`, `Pipeline`, `Job`, `RunnerPool`, `WebhookSubscription`, `RefPolicy`, `BranchProtection`, and more.\n\nBecause everything is a custom resource reconciled via GitOps, the forge's state is declarative and auditable.\n\n---\n\n## The per-org assistant\n\nThe \"built-in assistant, dispatchable in org namespaces\" maps to a concrete API and chart set:\n\n- **API:** `POST /api/orgs/:org/agents/dispatch` (kradle-cli README).\n- **Charts:** `assistant-stack.yaml`, `assistant-identity.yaml`, `assistant-org-secret.yaml`, `org-namespace.yaml` (`packages/kradle/charts/templates/`).\n\nIn other words, each org namespace gets its own dispatchable agent/assistant stack.\n\n---\n\n## Entrypoints\n\n| Surface | Detail |\n|---------|--------|\n| Core bins | `kradle-demo`, `kradle-server` |\n| CLI (`@a5c-ai/kradle-cli`) | `kradle serve` (HTTP API, default port 3080) and `kradle mcp` (stdio MCP server) |\n| Watch streams | SSE at `/api/watch/orgs/:org/:resource` |\n| Product home | `https://a5c.ai/kradle`; deploy lanes develop/staging/main → `kradle-*.a5c.ai` |\n\n---\n\n## How it fits the stack\n\nKradle 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](../architecture.md).\n\n---\n\n## Example\n\n```bash\n# Run the HTTP API locally (default port 3080)\nkradle serve\n\n# Expose kradle to an MCP client over stdio\nkradle mcp\n```\n\nDispatching the per-org assistant is an HTTP call:\n\n```\nPOST /api/orgs/:org/agents/dispatch\n```\n\n> Subcommand flags are governed by the repository CLI allowlist; run `kradle <command> --help` on your installed version for the authoritative surface.\n\n---\n\n## Next steps\n\n- **See where it sits:** [Architecture & How It Fits Together](../architecture.md)\n- **Ecosystem map:** [Ecosystem Overview](./overview.md)\n- **Related agent runtime:** [genty overview](./genty.md)\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-user-guide",
      "to": "page:docs-user-guide-ecosystem-kradle",
      "kind": "contains_page"
    }
  ]
}