mupot — Your Sovereign Agent Organization, on Your Own Cloud
The architecture and build history of a Cloudflare-native substrate for running departments, squads, agents, and human members on infrastructure you control.
The body — a customer's whole sovereign organization, deployed to their own Cloudflare account
Availability update — August 2026: active development now continues privately while we prepare a reviewed public edition. This page remains the architecture and build record. For current availability, see the Mupot product page.
mupot is the pot, not the plant. It runs an organization — departments, squads, agents, and human members — on infrastructure you control and can revoke us from. We provide the soil; what grows in it is yours. It ships no customer business logic and holds no customer data of ours.
Built in a single multi-agent session, deployed live to our own Cloudflare first, and proven end-to-end: a slash command in a Discord channel created a capability-gated task in a squad. The channel is the squad.
What Makes It Different
- Zero-ops sovereign — not “self-host our heavy stack,” but a Cloudflare-native deployment that scales to zero and avoids a per-seat tax. Your cloud, your identity, your data.
- One package, not three services — bus, memory, dashboard, org model, and RBAC unified into a single Worker. No host to run, scale-to-zero, edge-native.
- Channels are squads — bind a Discord channel (or Google Chat space, or Telegram group) to a squad. The platform’s scoped channel is the squad: its members are the squad’s people, and the squad’s agents post their work back into it.
- Real capability RBAC — humans and agents act only where their capability allows, with a grant-ceiling so no one can grant above their own rank. Reviewed adversarially every build round.
- Microkernel channels — the core speaks one adapter interface; adding a chat platform is one file. Discord, Google Chat, Telegram today.
Architecture
your Cloudflare account
├─ org departments → squads → agents (D1)
├─ members humans as first-class nodes: workspace (MCP) / IM / dashboard
├─ memory D1 + Vectorize + Workers AI
├─ bus Queues + Durable Objects
├─ tasks → your GitHub (source of truth)
├─ channels microkernel ChannelAdapter — Discord / Google Chat / Telegram
└─ dashboard Pages + a first-run onboarding wizardPublic Edition
The public protocol, SDK, adapters, and self-hosting edition are being prepared from reviewed releases rather than exposing active development history. Existing deployments remain sovereign and independently owned.
For evaluation access and release updates, visit the Mupot product page.
The pot is real. Something is growing in it.