Skip to main content
nexeai

Botpress: our review

Botpress builds conversational agents for customer relations: a visual studio to lay out the logic, an engine that lets a language model guide the conversation, and a TypeScript developer interface for cases the visual layer doesn't cover.

Data in the United StatesFree version, then paid·from $150/month
Go to Botpress's website (opens in a new tab)

What we take away from it

What counts in its favor

  • Written, unrestricted commitment not to use conversations to train or improve a model: the clause covers all conversation data, not just one particular connector.
  • SOC 2 certification publicly displayed, alongside a claimed GDPR compliance: rare at this level of detail among chatbot builders.
  • The visual studio and the developer kit (ADK) coexist: a business team lays out the scenario, a developer takes over edge cases without switching tools.

What counts against it

  • The free tier caps at 100 conversations per month: enough to test, not for real use before moving to a paid tier.
  • Hosting defaults to the United States; hosting in another region requires a negotiated Enterprise contract, not a simple checkbox.
  • The old self-hostable version (v12) has been relegated to a separate repository: the active product is a cloud platform, not software you install on your own servers.
  • Billing counts conversations, not messages: a long conversation and a one-line conversation cost the same, which can disadvantage a chatty use case.

A solid choice for a company that wants to industrialize its customer support with a written data commitment. Skip it if the spec requires hosting outside the United States from the very first paid tier, or a fully on-premise deployment.

The facts

First paid tier
$150/month — Plus, billed annually
Data hosting
Data in the United States · source
Categories
AI agents
Data verified on
30 July 2026

What happens to your data

Is your data used to train their models?
No
Subprocessors
The privacy policy is explicit and not limited to one particular connector: "We do not use Conversation Data or other End-User personal data for any other purpose, which includes analytics and algorithms and model improvements or training." Conversation data is stored "on servers located in the United States or other locations determined by the relevant Customer": hosting defaults to the United States, another location is negotiated contractually (Enterprise offer). A data processing agreement (DPA) is publicly published, which isn't standard in this category.
Retention
Kept "as long as it's necessary for the intended processing purposes," or until deletion is requested by the customer or the vendor; no figured duration is published.
Data processing agreement
Document published by the publisher

Botpress in detail

Botpress builds conversational agents for support and sales: a customer writes, the agent understands the request, looks up the information and replies, with a handoff to a human when the case goes beyond what it has been taught to do.

What it actually does

Studio lays out the scenario in visual blocks: what the agent should understand, where it looks for the answer (a knowledge base, a table, an API), and when it hands off. A so-called "autonomous" engine then lets a language model improvise the wording within that framework, rather than reciting fixed replies. For cases the visual builder doesn't cover, a TypeScript development kit (the ADK) lets you write the logic directly.

The most common use among businesses that adopt it: a first-line agent that answers recurring questions on a website or WhatsApp, and hands off to a human adviser as soon as it detects a sensitive request or frustration.

Why it interests us

It's one of the few chatbot vendors to publish a broad commitment against reusing conversations to train models, without limiting it to a single integration — a nuance that sets Botpress apart from narrower commitments found elsewhere in the category. But default hosting remains US-based: for a firm or notarial practice handling sensitive client exchanges, the question to ask before signing isn't just "does the agent answer well," it's "where do its conversations run, and who can see them pass through" — the central question of our work on AI agents and customer relations.

Where it falls short

The free tier caps at 100 conversations a month, enough to test but not to run real support. The first paid tier, at $150 a month billed annually, covers 250 conversations; beyond that, each extra block of 100 conversations is billed separately.

Hosting outside the United States isn't a self-service option: you have to go through a negotiated Enterprise contract to set a different region. And the old self-hostable version, v12, has been moved off to a separate repository: the product you install today is a cloud platform, not software you run on your own server without a sales conversation.

Our recommendation

Botpress suits a business that wants to industrialise its customer support with a written commitment on data and a published certification. For a small outfit handling a handful of requests a week, or one that requires European hosting by default, the ratio between the setup effort and the volume handled doesn't work in its favour.

Who it's for, and who it isn't

Suited for

  • A corporate customer-service team that wants to automate sorting and answering common requests, with a team able to supervise the studio
  • An organization that needs a written commitment against reusing conversations for training purposes
  • A mixed team: someone lays out the logic in the studio, a developer picks up edge cases through the developer kit

Not a fit

  • A small organization handling fewer than 100 conversations a month: the free tier is enough, but the jump to the 150 $/month paid tier is felt fast
  • An organization that must keep data in Europe by default, with no negotiated Enterprise contract to get it
  • A need for self-hosted software on your own server: the version that still allowed it (v12) is no longer the actively developed product

Frequently asked questions

Do you need to know how to code to build a Botpress agent?
Not to get started: the visual studio lets you lay out a conversation scenario by drag-and-drop. As soon as you need precise business logic or an integration it doesn't cover, the ADK (TypeScript developer kit) takes over. Plan for a technical profile to go beyond a first-level chatbot.
Do my customers' conversations train a model?
No, according to the published privacy policy: conversation data is explicitly excluded from any analytics, algorithm or model-training use. It's a broad commitment, not limited to one particular integration.
Does my data stay in Europe?
By default, no: Botpress stores conversation data on servers located in the United States. Hosting in another region is possible, but only through an Enterprise contract negotiated directly with the vendor, not as a self-service option.
How much does Botpress cost for a ten-person team?
Seat count isn't the limiting factor on paid tiers: it's the monthly conversation volume. The Plus tier starts at 150 $/month billed yearly for 250 conversations, with extra packs of 100 conversations at 65 $. The Team tier rises to 750 $/month for 1,500 conversations and unlimited seats.
Can Botpress still be self-hosted?
The old version (v12), under the AGPLv3 license, still exists in a separate repository, but it's no longer the actively developed product. The current Botpress — Studio, standalone engine, integrations — is a cloud platform; the public MIT-licensed code mainly covers the developer kit and integrations, not a full server to install on your own.

Alternatives to Botpress

Our sources

Prices and hosting terms change often. We recheck them periodically, but the publisher's page remains the only up-to-date reference.

Is Botpress the right choice for you?

We measure this tool against your real constraints — budget, privacy, your team's skill level — before you sign an annual subscription.

Book a call