BeforeQuery vs Botpress
Botpress is a chatbot development platform — a visual flow builder plus LLM integration you assemble into a bot. BeforeQuery is a packaged AI knowledge assistant — you connect docs, and the widget, bots, MCP, retrieval, evals, and analytics are ready. This comparison is about product vs framework.
Feature comparison
Information about Botpress is drawn from their public website and documentation.
Where BeforeQuery focuses differently
A product, not scaffolding
Botpress is powerful when you want to build a custom bot with branching logic, custom actions, and non-docs channels like WhatsApp or Instagram. If your use case is 'answer questions from our docs', BeforeQuery is that assistant already — you skip the flow-building, the retrieval tuning, and the evals harness.
Retrieval tuned for docs
BeforeQuery's ingest pipeline knows what a docs page looks like — it strips nav and boilerplate, extracts code blocks, chunks by heading, infers structure from unstructured PDFs. Retrieval combines vector + full-text + reranking, and refuses to answer when confidence is low. That's the accuracy story a general chatbot framework leaves you to build.
Deploy time measured in hours, not weeks
Add a source URL, wait for the crawl to finish, embed the widget or install the Slack/Discord/Teams app. Total engineering time: usually less than a day. A Botpress project of the same scope typically runs into weeks.
MCP, form deflector, evals — all included
The MCP server (for Cursor/Claude/ChatGPT), the standalone form deflector (for support-form ticket deflection), and automated LLM-as-judge evals are part of the product. In a framework you build each of these from scratch.
Frequently asked questions
When would I still choose Botpress?
If you're building a bot that lives on WhatsApp / Instagram / Messenger with complex branching logic, custom actions against your own systems, and where 'answer from docs' is only part of the job — a framework gives you the flexibility. For docs and support answers on a widget, Slack, or MCP, that flexibility is overhead.
Does BeforeQuery let me customise the assistant's behaviour?
Yes — persona/tone per knowledge base, system-prompt overrides, filters on which sources or versions to search, and full CSS customisation on the widget. What you can't do (deliberately) is rebuild the retrieval or answer pipeline; that's the packaged part.
How long does it take to be live?
Under an hour for most teams: sign up, connect a docs source, wait for the crawl, embed the widget. Building the same in a chatbot framework is typically several days to weeks including retrieval tuning and evals.
How does pricing compare?
BeforeQuery has flat monthly pricing with clear included quotas (Free / $99 Pro / Enterprise). Botpress uses usage-based pricing which can be cheaper at very low volumes but harder to forecast as you scale.
Do I lose flexibility by using a packaged product?
For flow-based bots, yes. For docs/support Q&A, no — the SDKs, MCP endpoint, WebSocket streaming, and Agents SDK give you enough surface to build custom experiences on top of the packaged assistant.
See for yourself
Connect your docs and get your first AI-powered answer in under 5 minutes. No credit card required.