one platform.
many crews.
any work that fits in a graph.
custom crews: early access
self-host: Q4 2026
KMSES — KAKEL Multi-agent Software Engineering System — is the orchestration platform KAKEL uses internally. It ships pre-configured with a five-person engineering crew that delivers product work today. The same machinery runs whatever crew your work requires: security auditing, incident response, compliance, content operations, anything that can be expressed as a coordinated team of specialists.
an orchestrator,
not an LLM wrapper.
Agents defined in YAML. Models swapped per role via LiteLLM. State in Redis, memory in ChromaDB, tasks in Celery, audit log everywhere. When something breaks, you read the stack trace. When you need a new specialist, you write a YAML file.
→ architecturea five-person
engineering team.
The crew KAKEL runs to keep delivery moving across a multi-vertical portfolio. Orchestrator plans, four specialists execute. Output lands as artifacts: branches, PRs, tests, docs. Today this crew is invoiced; metered billing comes with the Stripe wiring.
→ meet the crewone default crew today.
six on offer.
Three pre-configured crews — Engineering ships today; Security Audit and Application Build are the next two we're hardening into named SKUs. Three more illustrate the custom-crew pattern any team can express on the platform.
./engineering
Ship product features. Branches in your repo, PRs ready to review.
./security-audit
Audit a repo, URL, or APK. Findings + remediation PRs + executive PDF.
./application-build
Brief → deployed working app. Source lands in your GitHub.
./incident-response
When something breaks at 3 a.m. — page, triage, draft comms, write the post-mortem.
./compliance-audit
SOC 2 · ISO 27001 · HIPAA evidence collection and gap analysis.
./content-operations
Long-form content production at volume — with citations.
// crew status legend · shipping today = available now on KAKEL-hosted KMSES · scoping = pre-configured crew under active design (KMSES Audit + KMSES Build SKUs) · you define = the platform hosts custom crews via agent YAML; KAKEL writes the crew with you.
the engineering crew.
shipping today.
Five specialists. One coordinated task graph. Each agent has a defined role, a scoped toolkit, and an audit trail.
orchestrator
Decomposes the brief, drafts a plan, schedules sub-tasks, resolves dependencies.
backend engineer
Writes APIs, schemas, infrastructure, integrations. Owns the data model.
frontend engineer
Writes components, screens, client-side state. Owns the user-facing surface.
qa tester
Writes tests, runs them, fails the build when something breaks.
technical writer
Writes documentation, changelogs, runbooks, READMEs.
Add an agent by dropping a YAML file in the crew config and registering its tool kit. Standard engineering plumbing — no DSL to learn.
bring the platform
into your vpc.
For regulated industries (healthcare, finance, defense) or teams that need agents to reach proprietary internal services, KMSES will ship a customer-hosted control plane: Helm chart, customer-owned model keys, customer-owned data plane, audit log streamed to your SIEM.
- ▸ k8s helm chartdeploy to your existing kubernetes
- ▸ bring your own keysAnthropic · OpenAI · Bedrock · self-hosted (Ollama/vLLM)
- ▸ data residencyno telemetry leaves your VPC unless you opt in
- ▸ SAML SCIMyour IdP, your roles, your SoR
- ▸ audit to SIEMSplunk · Datadog · CloudWatch · stdout
$ helm repo add kakel https://charts.kakel.io
# install into your namespace
$ helm install kmses kakel/kmses \
--namespace kmses \
--set crews.engineering.enabled=true \
--set inference.provider="anthropic"
> deploying...
> ready in 3m12s
boring infrastructure.
by design.
Nothing exotic. CrewAI for orchestration, Celery for the task graph, Redis for state, ChromaDB for memory, LiteLLM so any agent can swap providers. When something breaks, you can read the stack trace.
The interesting part is the scaffolding: crew definitions, role budgets, retry semantics, the audit ledger, human-in-the-loop checkpoints. That's where the IP lives.
what's coming.
honestly dated.
Items below are scoped but not shipped. Want to influence priority? The early-access program is the place for that.
- ./kmses-auditPre-configured security-audit crew paired with SAST · DAST · CVE · IaC · secrets scanners. Findings + remediation PRs.scoping
- ./kmses-buildPre-configured app-build crew with architect, infra, and release-engineer agents. Brief → deployed app pipeline.scoping
- ./customer-hosted-planeSelf-hosted Helm chart with bring-your-own-keys. For regulated industries and air-gapped fleets.Q4 2026
- ./custom crew authoringFirst-class UI for defining new crews against the orchestrator without writing YAML by hand.Q1 2027
- ./per-team usage billingStripe-metered usage so teams pay for what their agents actually do. Today: invoiced.after stripe wiring
what kmses will not do.
- ✗ replace your senior engineer.Agents follow defined roles and submit artifacts. Humans still own architecture, review, and merge.
- ✗ run a security audit today.The security-audit crew is pre-configured but not yet shipping. KMSES Audit SKU is in scoping.
- ✗ generate a product from a paragraph.Build crews execute briefs, they do not invent product strategy. You write the spec.
- ✗ host your custom crew automatically.Custom crews work today, but the YAML and tool wiring is done with us. The DIY authoring UI is on the roadmap.
- ✗ lock you in.Code lives in your repo. Cancel anytime, keep everything.
early access is open
for a small group.
Tell us about your team and what crew you would brief first — default engineering, a planned SKU, or a custom workflow. We respond within two business days.