Head-to-head

SyntheticBrew vs Botpress: cloud studio, or an engine you own?

Botpress grew from an open-source chatbot framework into a polished cloud platform billed per conversation. SyntheticBrew went the other way: a source-available engine you self-host or run in our cloud, paying token prices on your own LLM keys — with setup driven from Cursor or Claude Code via native MCP. All Botpress figures below are from their public pricing page and GitHub, July 2026.

Side by side

SyntheticBrew vs Botpress: side-by-side comparison

Dimension	SyntheticBrew	Botpress
What it is	Source-available agent engine — self-host it or use our cloud; agents ship as an embeddable website widget	Cloud platform: AI-native helpdesk (Desk) plus a visual Agent Studio, managed on Botpress infrastructure
Pricing model	Self-hosted is free — you pay only your LLM provider. Cloud has a free tier and flat plans	Per-conversation: $150/mo for 250 conversations (Plus, billed annually), overage packs at $0.50–0.65 per conversation; LLM spend is bundled into the conversation quota
Overage control	No metered conversations; self-hosted has no platform metering at all	Auto-recharge cannot be turned off (their FAQ); unused pack conversations expire at month end
Self-hosting today	First-class: Docker and Helm, BSL 1.1 source on GitHub, actively released	Cloud-only: v12 is "officially sunset and no longer available for purchase, download, or new deployments" (their docs); its last release was April 2025
Bring your own LLM key	Yes — add models on your own provider keys (any OpenAI-compatible endpoint or OpenRouter); plus an optional per-request end-user BYOK mode admins can enable	Not documented as a plan feature; since May 2026 LLM spend is bundled into per-conversation pricing
Manage from a coding agent (MCP)	Hosted MCP server in the official registry: connect Cursor or Claude Code over OAuth and provision agents, knowledge, and the embed snippet — no local install	ADK dev tooling ships a local MCP server (`adk mcp`) so coding assistants can work with your running dev project
Build style	Config-as-code agents over REST — or let your coding agent set everything up via MCP; admin dashboard included	Visual flow builder (Studio) with an agent SDK (ADK); polished no-code/low-code experience
Built-in channels	Website widget + REST/SSE API today; other channels bridge through your backend	Webchat on all plans; WhatsApp from Plus; voice on Enterprise only
Knowledge grounding	Knowledge bases with RAG plus typed knowledge graphs; grounded, cited answers	Knowledge bases with vector storage (100 MB free / 1 GB Plus / 5 GB Team), tables for structured data
Data ownership	Self-hosted: agents, knowledge, and history live in your PostgreSQL	Vendor-managed cloud; storage capped by tier with a $40/mo expansion add-on

Where SyntheticBrew differs

Where SyntheticBrew differs from Botpress — and why it matters

Self-hosting that is not a museum piece

Botpress once stood for open-source chatbots — today the MIT repo hosts the SDK and integrations for their cloud, and the self-hostable v12 server is officially sunset: "no longer available for purchase, download, or new deployments" per their own docs, with its last release in April 2025. SyntheticBrew’s engine is the current product: source-available under BSL 1.1, released continuously, deployed with Docker or Helm.

Why it matters: If self-hosting is why you are leaving a closed SaaS, it has to be the vendor’s main line — not a sunset branch. Otherwise you inherit an unmaintained server and a migration problem on day one.

Token prices, not conversation arithmetic

Botpress bills per conversation with LLM spend bundled in: $150/month covers 250 conversations, overages cost $0.50–0.65 each, auto-recharge cannot be disabled, and unused pack conversations expire monthly. SyntheticBrew has no conversation meter — pay your LLM provider’s token price directly, or self-host for free.

Why it matters: A busy support widget can burn through 250 conversations in days. When each extra exchange costs half a dollar and top-ups are mandatory, cost scales with traffic — not with the value the agent delivers.

A hosted MCP, not just dev tooling

Both platforms speak MCP — differently. Botpress’s ADK ships a local MCP server so coding assistants can work on your running dev project. SyntheticBrew’s MCP server is hosted and listed in the official registry: your coding agent connects over OAuth and provisions the production agent, loads knowledge, and returns the embed snippet — one prompt, nothing installed locally.

Why it matters: Dev-loop tooling helps you build; a hosted MCP surface means the whole deployment — from empty account to a widget on your site — is driven from your editor and reproducible on demand.

For enterprise teams

An enterprise-ready Botpress alternative

Runs entirely inside your perimeter: engine + PostgreSQL, air-gap friendly, bring your own model keys.
Ed25519-signed JWTs, scoped API tokens, and an audit trail of agent actions.
No per-conversation metering on self-hosted deployments — costs scale with your LLM usage only.
Standard BSL 1.1 license with a fixed Apache 2.0 conversion date — read the code before you commit.

Enterprise AI agents

Choose for the job

Pick by what you value

Want a managed no-code studio with WhatsApp and a built-in helpdesk? Botpress Cloud does that today. Want an actively released self-hosted deployment, predictable token-price economics, an API from the free tier, and agents provisioned by your coding agent? That is what SyntheticBrew is built for — and the engine's source is open to read before you decide.

Try Cloud Self-host Contact sales

Questions

SyntheticBrew vs Botpress: FAQ

Is SyntheticBrew a good Botpress alternative?

If you want an actively maintained self-hosted deployment, token-price economics instead of per-conversation billing, or setup driven from Cursor / Claude Code via MCP — yes. If your team prefers building in a polished visual studio with built-in WhatsApp and a managed helpdesk, Botpress Cloud serves that profile well.

Isn’t Botpress open source?

The main GitHub repo is MIT-licensed and active, but today it hosts the SDK and integrations for Botpress Cloud — not a deployable platform. The self-hostable server lives in a separate v12 repo (AGPL), officially sunset: their docs state it is "no longer available for purchase, download, or new deployments", and its last release was April 2025. The current Botpress product is cloud-only. SyntheticBrew’s engine is source-available (BSL 1.1) and self-hosting is the mainline, continuously released path.

What does each actually cost to run?

SyntheticBrew self-hosted is free — you pay only your LLM provider; the cloud has a free tier. Botpress Plus is $150/month (billed annually) for 250 conversations with LLM spend bundled; extra conversations cost $0.50–0.65 in packs of 100, auto-recharge cannot be turned off, and unused pack conversations expire at month end.

When is Botpress the better choice?

When you want a managed, no-code experience: a visual flow studio, a built-in helpdesk with routing and RBAC (Team plan), WhatsApp out of the box, and you are comfortable with cloud-only hosting and per-conversation pricing. Test both against your actual traffic profile.

Can I migrate from Botpress to SyntheticBrew?

Your knowledge sources are your own docs and site content — re-ingesting them into a SyntheticBrew knowledge base takes minutes, from the dashboard or via MCP from your editor. Flow logic built in Botpress Studio would be re-expressed as agent instructions and tools rather than imported.

More comparisons: SyntheticBrew vs Chatbase · SyntheticBrew vs Flowise · SyntheticBrew vs Dify · All comparisons