OpenClawMU vs Botpress — open multi-tenant gateway vs commercial bot SaaS

Botpress is the polished commercial product in the bot-platform category. Studio for visual flows, hosted infra, marketplace, premium support. They’ve executed extremely well on the “I want to ship a bot without becoming a backend engineer” use case.

OpenClawMU is the open-source counterpart for a different shape of buyer: engineers who want CLI-first workflows, teams with data-residency or BYO-LLM requirements, and platform builders who want to ship multi-customer products on top of an open primitive.

Where Botpress wins

• Studio. The drag-and-drop builder is genuinely good for non-engineering users.
• Hosted infra. Don’t want to operate a server? Their cloud takes care of it.
• Marketplace. Integrations, templates, agents — curated and shipped.
• Support. Paid plans get human SLAs.

Where OpenClawMU wins

• Data residency. Your sessions, memory, and credentials sit on hardware you control.
• BYO-LLM. Point at Anthropic, OpenAI, your own Llama / Mistral inference server — gateway is provider-agnostic.
• Apache-2.0. Fork it, audit it, modify it, redistribute it.
• Code-first. Configuration as YAML, agents as TypeScript modules, no proprietary flow language.
• Tenant isolation as a building block. Build a platform on top instead of inside their walled garden.
• No platform margin. You pay your LLM provider, your VM provider, that’s it.

Cost model comparison

A medium SaaS with 200 active customers, each averaging 50 turns/day at ~3 K input + 500 output tokens per turn:

• Botpress (Team plan or higher): $495/month + AI spend (~$1,800/month on Sonnet 4.6) + per-message-volume overages. ≈ $2,300+/month.
• OpenClawMU (Hetzner CCX13 VM + AI spend): $35/month VM + ~$1,800/month direct to Anthropic. ≈ $1,835/month.

The $500/month difference compounds; over a year that’s $6 K. At 1,000 customers it scales linearly with no platform fee.

When to pick which

Botpress if your business is “shipping a bot quickly with minimal engineering”. OpenClawMU if your business is “shipping a product that happens to use bots, and you’d rather not pay a platform spread to do it”.

When to pick OpenClawMU

• Apache-2.0 source + self-hosted required (data residency, compliance, BYO-LLM).
• You want a code-first, CLI-driven workflow — not a drag-and-drop studio.
• Per-tenant cost accounting and quotas are first-class needs.
• You're building infrastructure-as-product (a platform on top), not an end-user bot.

When to pick Botpress instead

• You want the polished studio UX — non-engineers building flows visually.
• You're fine with managed infra and don't want to operate a Node process.
• You need Botpress's specific integrations / marketplace.
• Your bot is customer-support-focused; their built-in CSAT + handover tooling fits.

Frequently asked

Does Botpress support multi-tenancy?

Botpress Cloud is multi-tenant in the cloud-platform sense — accounts, workspaces, bots — but the isolation is theirs to enforce in their cloud. OpenClawMU's tenant isolation is enforceable by *you*, on your hardware, with your audit trail.

Can I self-host Botpress?

Botpress 12+ moved primarily to a Cloud-hosted model; self-hosted Community is available with a more limited feature set. If self-hosted parity matters, OpenClawMU's all-features-everywhere model is a cleaner fit.

Which is better for a small bot project?

Botpress Cloud Community tier is faster to start. OpenClawMU is faster to scale because the unit cost stays at your LLM provider's rate forever — no platform spread.