Botpress vs. Voiceflow

The DDR Score(TM) evaluates products across four weighted pillars: Company Credibility (15%), Core Features (25%), Unique Capabilities (35%), and User Sentiment (25%).

Botpress leads on Company Credibility (9.00 vs 6.50), Core Features (8.52 vs 7.00), and Unique Capabilities (8.00 vs 7.33), and the two tie on User Sentiment at 7.50. The credibility gap is the widest: Botpress pairs a public open-source repository with independently monitored uptime, while Voiceflow's paid pricing is unpublished and the review found no EU server region, both of which count against transparency. Sentiment is the pillar where Voiceflow closes the gap, on the strength of its ease of use and support.

See how Botpress and Voiceflow's pillar scores compare visually against all seven products in the DDR Spider™.

These scores are a starting point, not a verdict. Botpress and Voiceflow are built for different jobs, and the right pick depends on which job is yours. If both meet your must-haves, shortlist both, get Voiceflow's actual price, and test each on a real conversation: Botpress's free tier and, for agencies, Voiceflow's no-card trial.

Start with what you get at the entry point, then see what each upgrade adds and what it costs. Botpress publishes three tiers before Enterprise; Voiceflow publishes none, offering agencies a trial and routing businesses to a demo.

Features and pricing verified September 2026. ✓ gray = shared by both products at the Free tier. ✓ colored = unique to that product at this price. + = newly added at this tier. Indented ✓ note = the competing product already had this feature at a lower-priced plan.

Both products meter usage, but on different units, and only one publishes its prices. Botpress bills per conversation: any exchange with two or more user messages in a month counts as one, each conversation includes $0.10 of AI usage, and every tier states its allowance on the pricing page. Voiceflow bills in credits that cover messages, voice minutes, and knowledge queries, and does not publish prices: agencies and partners get a free trial with no credit card and then usage-based billing, while businesses are routed to a demo.

For a chat-only support bot the practical difference is predictability. A Botpress plan tells you the ceiling before the month starts. A Voiceflow bill depends on credit consumption, and voice minutes consume credits far faster than chat, which is exactly the workload Voiceflow is built for. Verified on both vendors' pricing pages, September 22, 2026.

These two products build agents differently, and the difference matters more than any feature list. Botpress runs every agent in its own isolated runtime, pairs a visual flow builder with code-level customization, and publishes its platform source under the MIT license. Voiceflow's distinction is the canvas: chat, voice, and telephony agents designed in one place, with model selection and fallback across the major LLM providers and environments for moving an agent from development to production.

The channel question decides most Botpress-versus-Voiceflow choices. Voiceflow offers voice on every tier including free; Botpress lists a voice channel only on its Enterprise plan. If a phone agent is the goal, that gap outweighs the score difference. If the goal is a resilient, customer-facing chat agent that a technical team will extend, Botpress's architecture is the stronger foundation.

Botpress publishes 67+ native integrations, verified on its own hub, and adds Zendesk, Intercom, HubSpot, and Salesforce connectors alongside WhatsApp, Slack, and webchat channels. Voiceflow's public integrations page lists 8 native integrations, and the review found that common channels beyond those are reached through its API and Functions rather than a connector.

Eight is not a typo and it is not disqualifying: Voiceflow's users reach most tools through its API layer, and its Discord community shares patterns for the common ones. It does mean that a team without a developer will hit a wall on Voiceflow sooner than on Botpress when the agent needs to touch a third-party system. Counts verified on each vendor's own integrations page, September 2026.