As of June 4, 2026, Botpress pricing should be modeled as several ledgers, not one chatbot subscription line. Separate the plan subscription, monthly AI credit, AI Spend at provider-token cost, incoming messages and events, extra bots, Always Alive, collaborators, Table Rows, Vector DB Storage, File Storage, website indexing, Knowledge Base answering, Studio emulator testing, spend caps, and Makefun support-media handoff. Refresh the official Botpress pricing page before using this worksheet for procurement.
Publication-time checks used the official Botpress pricing, pricing overview, knowledge-source docs, Knowledge Bases docs, and AI spend tracking guide. Those official pages are the source of truth because plan prices, included limits, add-ons, storage rows, AI Spend behavior, and legacy dashboard differences can change.
Botpress pricing source snapshot
| Cost row | What to record | Budget caveat |
|---|---|---|
| Plan subscription | Pay-as-you-go, Plus, Team, Managed, or Enterprise route, including monthly versus annual billing where shown. | Botpress notes that dashboard prices can differ for legacy workspaces, so quote exact rows only after a current source refresh. |
| AI Spend | Included monthly AI credit, configured AI Spend cap, and provider-token usage from Autonomous Nodes, AI Cards, translator or summarizer actions, and Knowledge Base calls. | The cap can stop AI actions; it is not a hidden unlimited allowance. |
| Messages and events | Incoming messages, bot-triggering events, proactive events, publish/test events, session behavior, and shareable URL testing. | Budget event volume, not just visible human chat messages. |
| Workspace add-ons | Extra bots, Always Alive, collaborators, Table Rows, Vector DB Storage, and File Storage. | Add-ons can matter as much as token spend when the knowledge base, tables, or file uploads grow. |
| Makefun handoff | Creator support, product onboarding, localization, media-production escalation, API-status triage, human QA, and analytics review. | These rows sit outside the Botpress subscription and should not be treated as free automation. |
AI Spend and provider-token rows
Start with the included monthly AI credit and the workspace AI Spend cap. Then add token-consuming actions: production answers, Studio emulator turns, AI cards, Autonomous Nodes, translation, summarization, personality actions, Knowledge Base ingestion and answering, searchable table or vector transformations, website indexing, and any fallback LLM route. The useful unit is cost per answered support conversation after testing, missed answers, escalation, and review.
Incoming messages events and storage rows
Botpress planning should count incoming messages and events together. Publishing, shareable URL tests, proactive triggers, reactions, session timeout behavior, and bot-triggering automation can all change event volume. For knowledge-heavy bots, keep Vector DB Storage and File Storage separate: website recrawls, documents, tables, images, audio, video, and uploads can grow even when conversation volume is flat.
Three scenario calculator
| Scenario | Botpress inputs | Decision row |
|---|---|---|
| Small product FAQ bot | One bot, one knowledge base, modest website indexing, low event volume, emulator tests, monthly AI credit, AI Spend cap, Vector DB Storage, File Storage, and human handoff. | Compare cost per answered support conversation, not only the plan subscription. |
| Makefun creator-support workflow | Plus or Team route, support events by language, onboarding flows, docs search, proactive chat, Always Alive, collaborators, media/API handoff, localization, QA, and escalation rate. | Botpress can own FAQ and routing while Makefun owns richer media, avatar, video, API, and support review work. |
| Agency or enterprise workspace | Several bots, higher event quota, extra bots, Always Alive, collaborators, larger Vector DB/File Storage, table rows, analytics, governance, and custom support requirements. | Compare workspace limits and governance with outcome-priced helpdesks only on the same support unit. |
Same-use comparison rows
Compare Botpress against the same workload shape. For adjacent Makefun planning, use current internal references such as Pinecone Assistant context-token planning, Airtable Field Agents AI credit planning, Hugging Face Inference Providers routing, and Macroscope Check Run Agent review costs. Do not claim Botpress is cheaper, better, safer, easier, more accurate, or higher ROI than HubSpot Breeze, Zendesk AI Agent, Intercom Fin, Voiceflow, Ada, LiveKit, Pipecat, Vapi, Make AI Agents, custom OpenAI or Anthropic bots, or Makefun-owned workflows without fresh same-scenario evidence.
Makefun support media API and localization handoff
For Makefun-style operations, add rows for product FAQ support, creator onboarding, API-status triage, documentation search, product catalog answers, localization, video or avatar follow-up, media-production escalation, and human review. Botpress can route the support-agent layer, but final customer-facing media, sensitive account decisions, pricing advice, and unsupported answers still need review and escalation paths.
Risks and caveats
- Refresh official Botpress pricing, pricing overview, knowledge-source docs, Knowledge Bases docs, and AI spend tracking docs before quoting exact prices or limits.
- Keep AI Spend, messages/events, storage, add-ons, testing, indexing, and handoff labor as separate rows.
- Account for legacy dashboard differences, provider-token drift, website recrawls, spend caps that stop actions, and human escalation.
- Review privacy and source quality before letting a Knowledge Base answer sensitive support questions.
- Avoid cheapest, best, safer, easier, more accurate, or guaranteed-savings claims without current same-scenario evidence.
FAQ
What counts as Botpress AI Spend?
AI Spend covers provider-token usage from LLM-powered actions such as Autonomous Nodes, AI Cards, Knowledge Base queries, testing, and related transformations. Treat the official docs and dashboard as the current source for the exact rows.
Are incoming messages the same as events?
No. Model incoming messages and bot-triggering events together, including proactive chat, publish/test actions, reactions, shareable URL tests, and session behavior where they apply.
When does Knowledge Base storage become a budget issue?
Storage becomes important when documents, websites, tables, uploads, recrawls, and answer logs grow. Keep Vector DB Storage and File Storage separate so a low-chat bot does not hide a large knowledge-base footprint.
Can an AI Spend cap replace support QA?
No. A cap controls spend behavior, but it does not validate answer quality, privacy, escalation, localization, or Makefun media/API handoff decisions.
