Agentic Index
Botpress vs Tidio (2026)
Both vendors last verified
Botpress and Tidio serve different buyers. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Botpress is a flexible agent builder for teams that want to construct custom agents, with a free plan and Plus at $150 a month on annual billing, while Tidio is an SMB support tool whose Lyro AI handles FAQs and actions with Shopify and Wix integrations, on a Starter plan from $29 a month with Lyro sold separately from $39. Choose Botpress for custom build flexibility. Choose Tidio for a fast, affordable ready made agent.
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Botpress and Tidio are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Botpress if
- You want to build custom agents with OAuth, multichannel deployment, and orchestration control.
- You have the resources to construct and maintain agents yourself.
- Flexibility matters more than the lowest price.
Choose Tidio if
- You want an affordable ready made agent with Shopify and Wix integrations, from $29 a month plus the Lyro add on.
- Lyro AI covering FAQs and light actions handles most of your volume.
- Fast self serve setup is the priority.
| Feature | B Botpress |
T Tidio |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
BotpressIntegrations & Tool Calling The Hub supplies installable integrations maintained by Botpress and by third parties, including HubSpot, Notion, Jira and Calendly, with a full catalog behind them, and agents call those systems through action cards and an Execute Code card. A single resolution can coordinate several systems at once, updating the record, triggering the next step and closing the loop, for example by changing a plan or updating billing details. On Enterprise, custom JavaScript can be injected to integrate business systems, which Botpress says makes the platform as flexible as code. Sourcebotpress.com/hubread 2026-09-05 |
||
|
TidioIntegrations & Tool Calling There are two routes out, one bounded and one general. Actions call external services over their APIs for third-party data and write back to them, with native Shopify support and coexistence alongside an existing helpdesk such as Zendesk. Above that, Model Context Protocol support means Lyro, connected once to a CRM, billing platform or database, can use every tool that system exposes. Named servers include Shopify, Guru and Stripe, and customers can ship their own for product search, bookings or order status. Tidio says every call is scoped, authenticated and auditable. Breadth is bounded by what the customer connects, not by a catalog. Sourcetidio.com/ai-agent/lyro-actionsread 2026-09-05 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
BotpressWorkflow Orchestration The Autonomous Node runs on LLMz, a versioned autonomous engine that decides which cards to execute and in what order, iterating until it reaches a final decision. Standard Nodes hold deterministic paths, so one bot can mix reasoning-driven and rule-based execution across multiple workflows. Agents can be composed with a Vision Agent for image input and hand off to other agents or to a person mid-flow. Sourcebotpress.com/docs/studio/introductionread 2026-09-05 |
||
|
TidioWorkflow Orchestration Lyro carries out tasks as well as answering. Actions let the agent retrieve and modify information in external systems dynamically mid-conversation over their APIs, checking order status and shipment details, managing address changes, updating databases, creating tickets and scheduling appointments. An API call or a sequence of calls fires when Lyro determines a customer needs external information. Tidio sets this against rigid scripted flows, and what is possible is bounded by the external system's API, not by a fixed action list. The Smart Actions and Simple Actions distinction is now legacy and survives only on a small number of older projects. The current product has a single Actions tool. Sourcehelp.tidio.com/hc/en-us/articles/20344365583132-lyro-actionsread 2026-09-05 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
BotpressTriggers & Channel Coverage Channels include webchat, WhatsApp, Instagram, Messenger and Slack among others, with voice through a maintained Twilio Voice integration that lets a bot take a phone call, and one build reaches all of them. The agent can also start work itself. Studio has Triggers, a Fixed Schedule card runs work on a timetable, and bots can send reminders into conversations. Sourcebotpress.com/integrations/twilio-voiceread 2026-09-05 |
||
|
TidioTriggers & Channel Coverage Lyro runs on the live chat widget by default and is switched on per channel for Facebook Messenger, Instagram, WhatsApp and incoming email, with connected mailboxes listed automatically and tickets answered from the same inbox. The multichannel product connects email, WhatsApp, Messenger, Instagram and live chat into one place, and Lyro audiences can branch on which channel a visitor arrived through. Voice and SMS are not among the channels. Sourcehelp.tidio.com/hc/en-us/articles/9003475527196-lyro-the-conversational-ai-agentread 2026-09-05 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
BotpressKnowledge Grounding & RAG Knowledge Bases are a Studio object that defines the information an agent can access. They take websites crawled by the platform, documents, custom text and Tables, index them automatically on ingest, and can be segmented so different bases serve different purposes, with per-node toggling of which bases an autonomous node may use. A Search Knowledge card performs retrieval inside the node, a Knowledge Agent ships in the prebuilt agent library, and Botpress publishes guidance on optimizing files for retrieval. Sourcebotpress.com/academy-lesson/studio-ui-knowledge-baseread 2026-09-05 |
||
|
TidioKnowledge Grounding & RAG A unified knowledge base, curated and scoped by the operator, feeds both customer-facing automation and agent assistance from one source. Adding a website URL automatically extracts and structures the content into searchable knowledge, and operators control which sources serve customer responses and which serve internal assistance. Lyro normally depends on the knowledge uploaded into it and does not improvise outside it. Actions exist to cover cases that need third-party data the knowledge base cannot supply, which makes it clear where grounding ends. Sourcehelp.tidio.com/hc/en-us/articles/20344365583132-lyro-actionsread 2026-09-05 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
BotpressMemory & State Persistence The agent development kit has a state layer with three scopes. Bot state persists across all users and conversations, user state persists across all conversations for a given user, and conversation state covers a single conversation, each defined as a typed schema in the agent config and read or written through the runtime. Any user or conversation can be loaded by id from anywhere in the agent to read and write its state and tags, so each customer's store can be reached and kept separate. Sourcebotpress.com/docs/adk/conversations/stateread 2026-09-05 |
||
|
TidioMemory & State Persistence Lyro works in session only, so no state persists between conversations, and Tidio says so in its security documentation. The Actions and MCP mechanisms retrieve CRM notes, past tickets and subscription state from external systems at request time. That is live retrieval against the customer's own systems, not agent memory, and reading a record the customer's CRM holds is not a memory layer, whoever writes it. Sourcehelp.tidio.com/hc/en-us/articles/20344365583132-lyro-actionsread 2026-09-05 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
BotpressHuman Oversight & Guardrails Human Handoff is a core platform feature with its own setup step, Configure Human Handoff, and a HITL Agent in the Studio's prebuilt agent library lets a builder drop escalation into a bot. A Policy Agent in the same library constrains behavior against defined rules, builder Instructions govern what the autonomous node may do, and Botpress publishes guidance on preventing fabricated answers. Access control over the agent is another setup step. Sourcebotpress.com/docs/studio/get-started/manage-your-agent/edit-appearanceread 2026-09-05 |
||
|
TidioHuman Oversight & Guardrails Control sits with the operator at configuration time and at the handoff. Guidance lets operators write behavioral instruction scoped to the Lyro agent covering tone, style and escalation rules. Operators keep complete control over which Actions Lyro can perform and which systems it can access, individual Actions can be tested before activation and enabled or disabled manually, and unresolved queries hand off instantly to a human. Lyro does not validate or roll back integrations. Tidio tells customers to test in a safe environment, says unintended changes to external systems cannot be reversed by Tidio, and adds that the customer's security team should evaluate the risk of data exposure. That is a real boundary on the oversight the platform provides, and it is the customer's configuration, not a Tidio gate, that stops a bad write. Sourcehelp.tidio.com/hc/en-us/articles/20344365583132-lyro-actionsread 2026-09-05 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
BotpressSecurity, Identity & Governance Botpress states SOC 2 certification and GDPR compliance, with third-party penetration testing by KPMG. Customer controls cover roles and role-based access, SSO, audit logs and workspace controls, and a DPA is available from the Plus tier and a HIPAA BAA on Enterprise. The SOC 2 report type is not specified, and a Trust Center is linked from the site footer. Sourcebotpress.comread 2026-09-05 |
||
|
TidioSecurity, Identity & Governance A live trust portal covers Tidio services including the Lyro AI Agent and publishes both attestation and named customer-facing controls. An independent third party completed a SOC 2 Type II audit covering Security, Availability and Confidentiality, and the report, an annual penetration test confirmation letter and a HECVAT-Lite are all available on request through the portal. Tidio also cites GDPR, CCPA and the EU voluntary AI Pact, and its Responsible Disclosure Policy offers safe harbor for good-faith security testing. Data is protected by TLS 1.2+ in transit and AES-256 at rest, accounts support two-factor authentication via TOTP with backup codes, and a DPA is folded into the terms. A version-controlled subprocessor list is published and updated at least thirty days before any change, which is a strong disclosure commitment. Tidio is not HIPAA compliant and will not sign a BAA. Sourcetrust.tidio.comread 2026-09-05 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
BotpressObservability & Auditability In production, a Conversations tab holds conversation history, a Logs tab records a deployed bot's activities, events, errors and actions with date filtering and custom console logging, and audit logs come on the enterprise tier. The view of an Autonomous Node's input, output and iteration steps lives in the Studio emulator, which does not save conversations, and Botpress's production debugging guide recommends duplicating the bot and inserting text cards or log statements instead of reading a native trace. Iteration data reaches production only through a separate Improvement integration built for feedback. Sourcebotpress.com/docs/debugging-bot-behavior-in-productionread 2026-09-05 |
||
|
TidioObservability & Auditability Tidio says every Action and MCP call is scoped, authenticated and auditable. The Actions list reports an execution count per action over the trailing thirty days, and advanced analytics ship from the Growth tier. There is no agent decision trace, reasoning log or configuration audit trail, and the auditable claim comes with no surface to view it, so a customer cannot see where the record lives or what it contains. Sourcetidio.com/ai-agent/lyro-actionsread 2026-09-05 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
BotpressDeployment & Data Residency Custom data residency is listed on the Enterprise tier, but the hosting region for Botpress Cloud, and whether a customer can choose it, is not stated. Self-hosting belongs to the older open-source v12 line, not the current cloud platform, and does not apply to Botpress Cloud. |
||
|
TidioDeployment & Data Residency All customer data is stored on servers in European Economic Area member countries, hosted on AWS in ISO-certified EU data centers. That is a single fixed region, a residency commitment with no customer choice of where data sits, and there is no self-hosted, private-cloud or single-tenant option. The parent entity Tidio LLC is US incorporated, so EU storage does not by itself remove US legal reach, and the trust portal covers Tidio services including Lyro under one policy. Sourcetrust.tidio.comread 2026-09-05 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
BotpressPrebuilt Agents, Templates & Packs The Hub carries production-ready templates for customer support, appointment scheduling and lead qualification, including a Kitchen Sink template that shows user data loading, workflow routing and live agent handoff, adopted by customizing instructions and swapping in a knowledge base. The Studio also offers prebuilt Agents that a builder drops into a bot, namely Summary, Personality, Policy, Translator, Knowledge, HITL, Vision and Analytics. Sourcebotpress.com/hubread 2026-09-05 |
||
|
TidioPrebuilt Agents, Templates & Packs A browsable template library ships in the product, templates can be added alongside custom Actions, and Actions can be cloned and exported for reuse across projects, so the customer adopts packaged assets by selection instead of writing each one. Tidio also offers ready MCP servers including Shopify, Guru and Stripe as adoptable units. The unit adopted is an Action or a server, not a whole agent, and there is no catalog of prebuilt agents. Sourcehelp.tidio.com/hc/en-us/articles/20344365583132-lyro-actionsread 2026-09-05 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
BotpressModel Flexibility & Routing Default LLMs are set per bot in Bot Settings and can be overridden on an individual Autonomous Node through advanced settings, separately for response generation and for the RAG model used against knowledge bases. The LLMz autonomous engine is versioned independently and written to stay agnostic to variance between models. Sourcebotpress.com/docs/studio/concepts/bot-settingsread 2026-09-05 |
||
|
TidioModel Flexibility & Routing Lyro's configuration covers channels, audiences, knowledge sources and behavioral guidance, with no model selection, routing or bring-your-own-model control, and the underlying provider is not named. Sourcehelp.tidio.com/hc/en-us/articles/9003475527196-lyro-the-conversational-ai-agentread 2026-09-05 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
BotpressAPIs, SDKs & MCP Extensibility Developers get a public API Reference, a Botpress Cloud API, an Agent Development Kit with its own documentation set alongside Studio, Integrations, Desk and Webchat, Hooks for custom code, an Execute Code card inside the autonomous node, and Import and Export for moving bots programmatically. Botpress also publishes Model Context Protocol material that ties MCP tool access to the Autonomous Node. Sourcebotpress.com/docs/studio/get-started/manage-your-agent/edit-appearanceread 2026-09-05 |
||
|
TidioAPIs, SDKs & MCP Extensibility The platform can be called from outside and extends in more than one direction. Model Context Protocol support connects Lyro to a system once so it can use every tool that system exposes, and customers can ship their own MCP servers for product search, bookings or order status as well as using Tidio's. An OpenAPI surface is available on the Plus tier, Actions are written directly against external APIs, and Actions can be exported for portability between projects. Tidio notes the Actions tooling is intended for developers, which is about audience, not availability. Sourcetidio.com/ai-agent/lyro-actionsread 2026-09-05 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
BotpressTesting, Debugging & Optimization The Emulator supports real-time conversation testing, with an inspect window showing an Autonomous Node's input, output and iteration steps, alongside an Event Debugger, version history and an Improvement integration that collects feedback on production iterations. Testing is a manual loop of inspecting and fixing. There is no test suite, regression harness, scored evaluation or pass rate, and the emulator neither saves conversations nor counts toward usage, so there is nothing to compare runs against. Sourcebotpress.com/academy-lesson/studio-ui-emulatorread 2026-09-05 |
||
|
TidioTesting, Debugging & Optimization Individual Actions can be tested inside the editor before deploying to a live site, drafts are flagged in the Actions list, and Tidio tells customers to test in a safe environment because it does not validate or roll back integrations. That is a test at the component level. There is no scored evaluation, scenario set or readable comparable verdict on a proposed agent change, so a team can exercise an action but not compare two versions of an agent. Secondary guides citing Tidio's help center describe a Playground sandbox for testing Lyro on chat and email before going live, with the ability to add a Q and A pair on the spot when it answers wrong. Neither that sandbox nor the action test produces a score. Sourcehelp.tidio.com/hc/en-us/articles/20344365583132-lyro-actionsread 2026-09-05 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
BotpressBrowser & Computer Use Botpress offers no browser control, hosted session or computer use. Agents act programmatically through Hub integrations, action cards, an Execute Code card and API calls, and reach people through channels. The Vision Agent in the prebuilt agent library reads images and does not operate an interface. Sourcebotpress.com/hubread 2026-09-05 |
||
|
TidioBrowser & Computer Use Tidio offers no browser control, hosted session or computer use. Lyro works programmatically, acting through Actions and Model Context Protocol connections against external APIs, with every call scoped and authenticated, and it reaches customers through the widget and its messaging channels, not by operating an interface. Sourcetidio.com/ai-agent/lyro-actionsread 2026-09-05 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | B Botpress |
T Tidio |
|---|---|---|
|
Entry price Lowest public entry point |
From $150 a month on Plus, billed annually. A free tier is available. | From $29 a month on Starter, with a free tier. The Lyro AI agent is sold separately from $39 a month. |
|
Pricing confidence How public the numbers are |
Public, exact | Public, partial |
|
Billing Primary billing axis |
Per conversation. Each tier includes a monthly conversation allotment, every conversation includes $0.10 of AI usage, and extra conversations bill in packs of 100. | Per billable conversation, a chat where a human replies, with separate quotas for Lyro AI conversations and Flow triggers. Seats are included up to 10 agents. |
|
Variable cost Workload / overage exposure |
Low variable cost | Low variable cost |
|
Free tier / trial Try before you buy |
Free tier
|
Free tierTrial
|
|
Buying motion Self-serve vs sales call |
Self-serve | Mixed |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
More comparisons with Botpress or Tidio
Other matchups in customer support agents
Not the pairing you were after? These compare a different set of customer support agents on the same 14 capabilities.