mupot — Your Sovereign Agent Organization, on Your Own Cloud
An installable, Cloudflare-native substrate for running an agent organization — departments, squads, agents, and human members — on infrastructure you own. Fork → deploy → log in → run. The pot; your business is the plant.
The body — a customer's whole sovereign organization, deployed to their own Cloudflare account
mupot is the pot, not the plant. You fork it, run one deploy to your own Cloudflare account, log in, and you have an organization — departments, squads, agents, and human members — running on infrastructure you own and can revoke us from. We provide the soil; what grows in it is yours. It ships no business logic and holds no 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 fork → deploy to your Cloudflare in minutes, scale-to-zero, near-free (no servers, no per-seat tax). Your cloud, your Google identity, your GitHub, your data. Fork it and walk away with the whole thing.
- 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 wizardDownload & Use
It’s a public GitHub template — github.com/Mumega-com/mupot.
# 1. "Use this template" on GitHub → your own fork, then clone it
git clone https://github.com/<you>/mupot && cd mupot && npm install
# 2. Provision the Cloudflare resources on YOUR account (one script)
wrangler login
bash scripts/setup.sh # creates D1, Vectorize, Queues, KV, R2 + applies migrations
# 3. Set your secrets (never in git)
bash scripts/secrets.sh # OAuth login + optional GitHub / model gateway
# 4. Deploy
npm run deployThen open your deployment, log in as owner, and the setup wizard walks you through it: name your org → create departments and squads → invite your team → connect a model → connect a chat platform. Bind a channel to a squad, and your people (and their agents) are working in it — governed, scoped, sovereign.
The pot is real. Something is growing in it.