A production multi-agent team that runs headless on Azure — without binding engineering to an IDE or direct cloud AI SDKs. Every worker routes cognition through KimssClient; every Git and telemetry action flows through a self-hosted MCP tool plane authenticated with Microsoft Entra ID.
Modern teams want AI that ships work: reviews code, fixes incidents, drafts content, triages support — not chat in a sidebar. They also need governance: one model gateway, auditable actions, human approval where it matters, and no scattered API keys in scripts.
worksfusion set out to operate Kimss with a persistent digital workforce: specialized agents, clear ownership per task, and orchestration that survives beyond a single developer session.
worksfusion built a multi-agent, multi-service architecture on three pillars:
Every worker uses kimss.KimssClient for chat, agents, and vector stores. No direct OpenAI or Azure AI SDK calls in application code — a runtime guard enforces that policy.
Git, GitHub, logs, and repo introspection run through a self-hosted MCP server on Azure Container Apps, authenticated with Microsoft Entra ID. Secrets never reach agent containers.
Scheduled and event-driven DAGs run workers on Azure Container Apps. Private PostgreSQL holds missions and content state; Slack provides ingress and human-in-the-loop approval.
Ingress, orchestration, cognition, tools, and state — separated by design.
Hover or scroll to see each layer highlight in sequence.
A single agent router listens on Slack and delegates to the right worker — one channel reaches the whole fleet.
Architecture review and controlled merges to staging.
Log-driven bug fixes as pull requests.
Staging validation and PR feedback.
API documentation from route changes.
Turns CTO missions into structured hiring packages for new workers.
Runs any role defined by a hiring package — no redeploy per job title.
Ticket triage and usage digests to Slack.
Daily content drafts with approval, then scheduled publishing.
"Kimss gave us a sovereign control plane for a fleet of agents that actually ships work — with governance we could put in front of our platform team."
Executive sponsor, worksfusion
Replace with approved customer quote before publish.
Start with the SDK or talk to us about enterprise governance and dedicated Azure capacity.