What's the difference between Botpress Cloud and self-hosted Botpress?

Botpress Cloud is the hosted SaaS version. You build flows in their editor and they handle infrastructure. Self-hosted Botpress runs on your own servers, giving you data control but requiring you to manage the Botpress runtime, updates, and infrastructure. Self-hosted is free for most use cases; Botpress Cloud has a free tier with paid plans for higher volumes and enterprise features. For data residency requirements, self-hosted is the right path, but you're still running their platform software, not owning the codebase.

What's the migration path from Botpress to a custom build?

Botpress flows can be exported as JSON. This serves as a specification for the custom build: what entities are extracted, what the conversation states are, what integrations are called. The custom build won't import this directly but it documents the logic that needs to be replicated. Plan two to four weeks for a medium-complexity migration, including re-testing the conversation flows against your actual user inputs.

How does Botpress compare to Rasa and custom builds?

Rasa is another open-source chatbot framework, more Python-native, with stronger NLU customization. Botpress is more accessible to non-Python developers and has a visual flow editor. Both are platforms with their own abstractions and update cycles. A custom build doesn't use either platform. You write the conversation logic directly in Python or TypeScript. Choose Rasa if your team is Python-first and you need fine-grained NLU control; choose Botpress if you want a visual editor and broader community; choose custom if you've outgrown what a chatbot platform can do.

What's the real cost of maintaining an open-source platform like Botpress?

Self-hosted Botpress is free to use but not free to run. You need someone to handle Botpress version upgrades (which sometimes break flows), manage the runtime environment, debug platform-level issues (which require understanding Botpress internals), and keep integrations compatible with new Botpress versions. For a team with a dedicated developer, this is manageable. For a small team without dedicated DevOps capacity, the maintenance burden of running a complex open-source platform is often underestimated.

Botpress vs Custom AI Agent

Botpress is solid open-source tooling. Here's when you outgrow it.

Botpress is a well-maintained open-source chatbot platform with a large community, a visual flow editor, and reasonable self-hosting support. For teams building standard chatbot flows, it's a legitimate choice, the community produces plugins and integrations, and the platform is actively developed.

The limit is that it's still a platform. When your use case doesn't fit the chatbot flow model, when integrations get non-standard, or when you need to fully own the codebase without a runtime dependency, the platform becomes a constraint rather than a foundation.

Tell us what your agent needs to do.

What Botpress is.

Botpress is an open-source AI agent and chatbot platform. It provides a visual flow editor for designing conversation logic, an NLU system for intent recognition and entity extraction, and an integration framework for connecting external services. It can be self-hosted or used as a cloud service.

The platform has been around since 2017, has a substantial community, and is actively maintained. It supports LLM integration for generative responses alongside its traditional flow-based approach. The self-hosted version is free under a license that permits commercial use for most organizations.

What custom development adds.

These are the specific advantages of owning the code vs running a platform runtime.

No platform abstractions

Custom code expresses exactly what your system does. No Botpress node types, no flow engine constraints, no undocumented platform behaviors that change with updates. The logic lives in your codebase.

Full TypeScript or Python control

Any algorithm, any library, any pattern. Botpress allows custom code through its Actions system, but you're still working within the platform's execution model and its version of Node.

Arbitrary integrations

Connect to any internal system, legacy API, or proprietary data source. Botpress's integration system works well for standard use cases, for non-standard authentication, binary protocols, or custom data pipelines, you're working around the platform.

No Botpress update dependency

When Botpress releases a major version, your flows may break. Your integrations may need updating. Your deployment may require downtime. A custom build updates on your schedule.

Non-chatbot workflows

Botpress is designed for conversation flows. If your use case is a background agent, an event-driven automation, a data pipeline with AI steps, or anything that doesn't have a chat interface: Botpress is the wrong tool.

Full operational control

Your own observability stack, your own deployment pipeline, your own scaling logic. Botpress Cloud abstracts infrastructure; self-hosted Botpress still requires running the Botpress runtime, which adds operational complexity you don't own.

Feature comparison.

Feature	Botpress	Custom Build
Setup time	Hours to days	Weeks
Self-hostable	Yes	Yes
Custom code logic	Via Actions (Node.js)	Full control
Non-chatbot workflows	Not the intended use	Any workflow type
Platform update dependency	Yes	No
Community and plugins	Large open-source community	Build what you need
Operational complexity	Botpress runtime required	Your own stack

When Botpress is the right choice.

Building a chatbot
Botpress is designed for conversation flows. If that's your use case (FAQ bots, onboarding flows, support triage), it's a solid foundation.
Self-hosting is a requirement but you want existing infrastructure
If you need data on your own servers but don't want to build the chat infrastructure from scratch, Botpress self-hosted is a reasonable choice that saves significant development time.
Active development team
If you have engineers comfortable with JavaScript and willing to maintain a Botpress installation (handling updates, debugging platform-level issues, managing the runtime) the open-source model works.
Standard chatbot flows with established patterns
FAQ bots, guided troubleshooting, appointment scheduling, lead qualification. Use cases where the Botpress community has already built similar things and the patterns are well-documented.

When custom is the right call.

Complex non-chatbot workflows
Background agents, event-driven automations, multi-step data pipelines with AI reasoning steps. Botpress is a chatbot platform, forcing non-chatbot workloads into it creates architectural debt.
Full code control is required
When your team needs to fully own, test, and audit every line of code in the system, without any third-party platform runtime as a dependency.
Unique integration requirements
Non-standard APIs, custom authentication protocols, binary data streams, or integrations with legacy systems that Botpress's connector model can't handle cleanly.
You've already hit the ceiling
If you're writing significant custom code inside Botpress Actions to work around platform limitations, you're doing custom development on top of a platform. At that point, the platform is adding cost without adding value.

Cost comparison.

Botpress

Self-hosted is free for most use cases (license allows commercial use). Botpress Cloud starts free, with paid plans at $495–$1,495+/month for higher volumes and enterprise features. The real cost of self-hosted is engineering time to maintain the installation and handle version updates.

Custom AI agent

Build cost depends on complexity and scope. Monthly infrastructure typically runs $100–$300/month. No platform runtime to maintain, your team owns the entire stack.

Frequently asked questions.

What's the difference between Botpress Cloud and self-hosted Botpress?: Botpress Cloud is the hosted SaaS version. You build flows in their editor and they handle infrastructure. Self-hosted Botpress runs on your own servers, giving you data control but requiring you to manage the Botpress runtime, updates, and infrastructure. Self-hosted is free for most use cases; Botpress Cloud has a free tier with paid plans for higher volumes and enterprise features. For data residency requirements, self-hosted is the right path, but you're still running their platform software, not owning the codebase.
What's the migration path from Botpress to a custom build?: Botpress flows can be exported as JSON. This serves as a specification for the custom build: what entities are extracted, what the conversation states are, what integrations are called. The custom build won't import this directly but it documents the logic that needs to be replicated. Plan two to four weeks for a medium-complexity migration, including re-testing the conversation flows against your actual user inputs.
How does Botpress compare to Rasa and custom builds?: Rasa is another open-source chatbot framework, more Python-native, with stronger NLU customization. Botpress is more accessible to non-Python developers and has a visual flow editor. Both are platforms with their own abstractions and update cycles. A custom build doesn't use either platform. You write the conversation logic directly in Python or TypeScript. Choose Rasa if your team is Python-first and you need fine-grained NLU control; choose Botpress if you want a visual editor and broader community; choose custom if you've outgrown what a chatbot platform can do.
What's the real cost of maintaining an open-source platform like Botpress?: Self-hosted Botpress is free to use but not free to run. You need someone to handle Botpress version upgrades (which sometimes break flows), manage the runtime environment, debug platform-level issues (which require understanding Botpress internals), and keep integrations compatible with new Botpress versions. For a team with a dedicated developer, this is manageable. For a small team without dedicated DevOps capacity, the maintenance burden of running a complex open-source platform is often underestimated.

Tell us what you're building.

Describe the use case, the integrations, and any constraints. We'll give you an honest view of whether Botpress fits or whether a custom build is the better foundation.