---
title: "10 Best Chatbot Development Frameworks in 2026"
description: "I tested many chatbot development frameworks to find the best fit for each skill level. Here are 10 picks for code-first, low-code, and no-code teams."
url: "https://www.lindy.ai/blog/chatbot-development-frameworks"
category: "AI Agents"
---

# 10 best chatbot development frameworks in 2026

_By Marvin Aziz, reviewed by Lindy Drope, updated November 20, 2026_

I tested many chatbot development frameworks to find the best fit for each skill level. Here are 10 picks for code-first, low-code, and no-code teams.

**_Halfway through building a test bot with Microsoft Bot Framework, I opened its GitHub repository for a code sample and found an archived notice. Microsoft stopped supporting the SDK on December 31, 2025. Botkit, another frequent recommendation, had gone read-only in 2024._**

Two of the most-cited tools in this space no longer receive updates. That shaped how I evaluated everything else. I checked maintenance status alongside features and separated tools for new builds from those relevant mainly to existing bots.

I tested many chatbot development frameworks and picked nine across three skill levels, plus one AI teammate for Slack. Code-first SDKs, low-code builders, and no-code tools. Each ran a real task like booking a class, replacing a lost card, or answering a refund question. Teams that want AI help inside Slack can use Lindy, which answers questions and handles follow-up work with no bot to build.

Skill level is the sharpest filter. It decides who builds, who maintains, and how much your team leans on a developer after launch.

## Best chatbot development frameworks compared

| Tool | Open source or hosted | Skill level | Best for | Starting price |
| --- | --- | --- | --- | --- |
| [**Microsoft Bot Framework**](https://dev.botframework.com/) | Open-source SDK (archived) with Azure hosting | Code-first | Best chatbot framework for teams with existing Azure bots | Free SDK, Azure Free tier, then per 1,000 messages |
| [**Rasa**](https://rasa.com/) | Self-hosted | Code-first (Python) | Best self-hosted chatbot framework for on-premises control | Free Developer Edition, Enterprise custom |
| [**Amazon Lex**](https://aws.amazon.com/lex/) | Hosted on AWS | Low-code, with Lambda code | Best hosted chatbot framework for AWS-native teams | $0.00075 per text request |
| [**Google Dialogflow**](https://cloud.google.com/dialogflow) | Hosted on Google Cloud | Low-code | Best hosted chatbot framework for Google Cloud teams | $0.007 per text request (CX), free ES Trial |
| [**Botpress**](https://botpress.com/) | Hosted, legacy v12 is open source | Low-code | Best chatbot framework for SMBs who want a visual builder | Free plan, Plus $189/month |
| [**IBM Watsonx Assistant**](https://www.ibm.com/products/watsonx-orchestrate) | Hosted | Low-code | Best chatbot framework for enterprise teams on legacy systems | Free trial, Essentials $578/month |
| [**Botkit**](https://github.com/howdyai/botkit) | Open source (archived) | Code-first (Node.js) | Best open-source chatbot framework for existing Node.js Slack bots | Free |
| [**Wit.ai**](https://wit.ai/) | Hosted API | Code-first | Best free chatbot framework for lightweight NLU | Free |
| [**Kommunicate**](https://www.kommunicate.io/) | Hosted | No-code | Best chatbot framework for customer support with live handoff | $40/month |
| [**Lindy**](https://www.lindy.ai/) | Hosted | No-code | Best AI teammate for teams that want chatbot help inside Slack | $49.99/month per user |

This table compares chatbot frameworks, hosted builders, and an AI teammate on hosting, skill level, and starting price. Rasa suits developers who need control over deployment. Teams comparing [**AI chatbots for businesses**](https://www.lindy.ai/blog/best-ai-chatbots-for-businesses) often start with Botpress for its visual builder. Lindy handles internal questions and follow-up work in Slack with no custom bot.

## What is a chatbot framework?

A chatbot framework is a **set of code libraries and tools** that handle language understanding, dialogue, channels, integrations, and analytics, so developers do not have to build a chatbot from scratch. The team writes only what makes its bot unique, such as its answers, business rules, and connections to company systems.

Chatbot frameworks run structured conversations, while [**AI agent frameworks**](https://www.lindy.ai/blog/ai-agent-frameworks) such as LangChain and CrewAI run multi-step tasks that a language model plans on its own.

**Most chatbot frameworks share a core set of components:**

- **Natural language understanding (NLU):** NLU reads each message and turns it into an intent (e.g., "book a table") and entities (e.g., date and party size). The bot then knows what the user wants, even when two people phrase the same request differently.
- **Dialogue management:** This layer tracks where the conversation stands and decides the next reply or question. If a user changes the date halfway through a booking, dialogue management updates the details and keeps the flow on track, so the bot does not restart the conversation.
- **Channel connectors:** Connectors send and receive messages on web chat, Slack, WhatsApp, Microsoft Teams, and phone lines. A bot can serve customers across the channels its connectors support, with shared conversation logic managed in one place.
- **Integration layer:** Webhooks, APIs, and code functions connect the bot to CRMs, calendars, and databases. A support bot can look up an order, book a meeting, or create a ticket mid-chat, so the customer gets a real result.
- **Analytics and logging:** Logs and dashboards record every conversation and show where users drop out or ask for a human. Teams review this data each week to fix weak answers, add missing intents, and improve the bot before the next release.

## How I tested the best chatbot development frameworks

![Chatbot framework test projects overview](https://www.lindy.ai/_sherpa/content/5824ded7-f01f-48a2-80ca-ac121b1f8cf0.webp)

I evaluated nine frameworks, plus Lindy, through test projects covering tasks such as bookings, order support, and refund questions. **I set up the tests to answer a question people often ask on** [**r/Rag**](https://www.reddit.com/r/Rag/comments/1gptf9p/what_framework_to_use_for_chatbot/) **and** [**r/learnpython**](https://www.reddit.com/r/learnpython/comments/1aqd7i3/what_library_or_framework_do_you_recommend_to/)**:** which framework should a small team use for its first chatbot?

![Criteria used to evaluate the chatbot frameworks](https://www.lindy.ai/_sherpa/content/9c2092e4-29b3-41a8-aa9d-8d44331f205b.webp)

**I used five criteria, applying each where the tool supported it:**

- **Setup and skill level:** I noted when each build needed code and how much it took. This shows whether a support lead can run the tool alone, or whether the team needs a developer from the first day.
- **Off-script messages:** I typed loose requests and changed details mid-chat, such as a new booking date. Real customers write this way, so the check shows how well a bot keeps up after launch.
- **Channels:** I checked whether one bot could answer on web chat, Slack, WhatsApp, or a phone line. A team that adds a channel later should not have to build and pay for a second bot.
- **Backend connections:** I tested whether each bot could pull live data, such as an order status or open booking slots, during a chat. A bot that only answers FAQs cannot finish a real task for the customer.
- **Pricing and maintenance:** I checked every price on the official pricing page and every tool’s update status on GitHub or its docs. Costs change a lot at scale, and two tools on this list no longer get updates.

The findings below explain what each tool handled in its test, where it needed extra development, and which teams should consider it.

## Best chatbot framework for teams with existing Azure bots

### Microsoft Bot Framework

[**Microsoft Bot Framework**](https://dev.botframework.com/) is a set of open-source SDKs and Azure tools for building chatbots in code. Developers write the bot in C#, JavaScript, or Python, and Azure AI Bot Service hosts it. One bot can then answer users in Microsoft Teams, Slack, Facebook Messenger, a website chat window, and other channels.

![Microsoft Bot Framework page](https://www.lindy.ai/_sherpa/content/7a3c1af8-1b46-4206-930b-1accde7542c8.webp)

### In my testing

One C# codebase served two channels in my IT help desk test. I wrote the dialogs once, registered the bot in Azure AI Bot Service, and enabled Microsoft Teams and Web Chat from the Azure portal. A leave-policy question got the same answer in Teams and in a chat window on a test page, and **no code was exchanged between them**.

Enterprise teams also need the bot to know who is asking. I added an OAuth connection in the portal, and a sign-in card appeared inside Teams before the bot showed each user’s open tickets.

### Key features

- **Dialogs and state management:** The SDK includes a dialog library with step-by-step flows and ready-made prompts for text, numbers, choices, and yes-or-no answers. Each step saves the user's reply in the conversation state, so the bot can collect a long request across many turns and still recall the first answer.
- **Channel connectors:** Azure AI Bot Service links one bot to Microsoft Teams, Slack, Facebook, email, and other channels. An admin enables each channel in the Azure portal, so a team can reach users in a new app through a single setting while the bot code stays the same.
- **Direct Line and Web Chat:** Direct Line connects a bot to your website or mobile app. Microsoft publishes the Web Chat client as open source, so a front-end developer can restyle the chat window to match the product's brand and layout.
- **Adaptive Cards:** Bots can send cards with buttons, forms, images, and input fields in place of plain text. Developers write a card once in JSON, and each host app draws it in its own style, so an approval form looks native in Teams and in Web Chat.
- **Test adapter for unit tests:** The SDK includes a test adapter that sends sample user messages to a bot in a standard unit test. Developers can check every dialog path in their build pipeline and catch a broken reply before it reaches a real user.

### Limitations

Microsoft archived the Bot Framework SDK and ended support on December 31, 2025, and it now points new projects to the Microsoft 365 Agents SDK. Every bot needs code and Azure hosting, so the learning curve is steep for non-developers. Heavy website or in-app chat volume requires the paid S1 tier.

### Pricing

The Bot Framework SDK is free. Azure AI Bot Service has a [**Free tier**](https://azure.microsoft.com/pricing/details/bot-services/) with unlimited messages on channels like Teams and Slack, plus 10,000 website and app messages per month. The paid S1 tier costs $0.50 per 1,000 website and app messages, and Azure hosting incurs additional charges.

## Best self-hosted chatbot framework for on-premises control

### Rasa

[**Rasa**](https://rasa.com/) is a Python framework for building chatbots and voice assistants that you can run on your own servers. Its current engine, called CALM, uses a language model to understand each message. The flows that your developers write then determine what the bot does next, so the bot follows your business rules in every conversation.

![Rasa homepage](https://www.lindy.ai/_sherpa/content/8f7f4931-57ab-432d-a941-380d8a712116.webp)

### In my testing

I built a test card-replacement bot on a local server with **three steps in a single flow file:** confirm the customer's identity, ask which card they lost, and order a new one. A test user typed “lost my wallet, need my debit card blocked,” and the bot first asked for identity details. **The step order never changed**, even when I asked for the card early.

A custom Python action called a mock banking API, and the Rasa server kept every conversation record on the same machine. I then ran 10 test conversations and checked the result at each step. This gave me a repeatable way to check whether later flow changes affected the identity check, card selection, or replacement request.

### Key features

- **CALM engine:** A language model reads each message and picks the flow that matches what the user wants. The business logic stays in the flows your team writes, so the bot completes tasks in the same order every time and does not make up a new process mid-chat.
- **Flows and custom actions:** Developers write flows as plain YAML files and custom actions as Python code that calls your own APIs and databases. A developer can review every change in Git, so the bot's behavior goes through the same review process as the rest of your codebase.
- **End-to-end testing:** Rasa runs a bot through a set of sample conversations in text and voice, then reports which ones passed and which failed. Teams can run these tests after every edit and find a broken step long before a customer reaches it.
- **Self-hosted deployment:** The Developer Edition license covers local use and production use on your own infrastructure. Code and conversation records stay on your own servers, so a security team controls where the bot runs.
- **Enterprise Search:** Rasa includes Enterprise Search, which lets the bot answer open questions from your own documents. Structured tasks still run through flows, so one assistant can explain a policy and then process the request that follows it.

### Limitations

Rasa expects Python skills and server management, so non-developers face a steep learning curve. The free Developer Edition supports one bot and caps monthly conversations, so production scale requires a paid plan. The classic Rasa Open Source repository on GitHub is now in maintenance mode, and new features ship with the CALM engine.

### Pricing

Rasa’s free Developer Edition includes 1 bot and up to [**1,000 external conversations per month**](https://rasa.com/pricing). Enterprise pricing is custom.

## Best hosted chatbot framework for AWS-native teams

### Amazon Lex

[**Amazon Lex**](https://aws.amazon.com/lex/) is a fully managed AWS service for building chatbots and voice bots. You list the user's intents and the details the bot must collect, and Lex runs the conversation. Backend tasks run in AWS Lambda, and teams can publish finished bots to Amazon Connect, Slack, Facebook Messenger, and Twilio SMS.

![Amazon Lex homepage](https://www.lindy.ai/_sherpa/content/4172e2ae-f93f-4e31-8340-d4ba8810006d.webp)

### In my testing

Lex **filled three booking details from one sentence** in my hotel test. The intent had slots for city, check-in date, and number of nights, each with its own prompt for missing details. When a test user typed “two nights in Denver from Friday,” the bot asked no follow-up questions and moved straight to confirmation.

A Lambda function then checked room availability in a test DynamoDB table. Lex called the function at fulfillment, and the reply carried live data in the same turn. Adding the bot to an Amazon Connect test number took one step, and the same intents **answered a phone call with no rebuild**. Every part of the build stayed inside AWS.

### Key features

- **Slot-based dialogue management:** You list the slots and prompts for each intent, and Lex decides which question to ask next. Contexts let one finished intent open related intents, so a multi-turn flow, such as booking, then payment, needs no custom dialogue code.
- **Generative AI through Amazon Bedrock:** Conversational FAQ answers common questions from an approved knowledge source using Bedrock models. Assisted Slot Resolution calls a language model when the built-in NLU misses a value, so free-form replies still map to the right slot.
- **Telephony-grade speech:** Lex trains its speech engine on 8 kHz phone audio, and the engine supports barge-in and wait-and-continue. Amazon Polly voices each reply, so phone bots in Amazon Connect or Genesys Cloud CX can understand callers and answer them in a natural voice.
- **Test Workbench and analytics:** Test Workbench builds audio and text test sets from past conversations and reports results for transcription, intent matching, and slot resolution. Pre-built dashboards show where users drop out, so teams can fix weak intents before the next release.
- **Versions and aliases:** Teams can version bots, intents, and slot types and map each version to an alias such as production, development, or test. A new version goes live under a single alias, so client apps keep working without any code updates.

### Limitations

Lex works best within AWS, so moving to another cloud later will require rebuilding the Lambda code and channel setup. Non-developers can map flows in the Visual Conversation Builder, but backend logic still needs Lambda code and AWS permissions. Costs grow with every message, so high-volume bots need careful budgeting.

### Pricing

Amazon Lex charges per request, with no per-user, per-seat, or minimum fee. Text messages cost [**$0.00075 per request**](https://aws.amazon.com/lex/pricing/), and voice messages cost $0.004 per request. New AWS customers get up to $200 in AWS Free Tier credits, usable within 12 months.

## Best hosted chatbot framework for Google Cloud teams

### Google Dialogflow

[**Google Dialogflow**](https://docs.cloud.google.com/dialogflow/docs) is a Google Cloud service for building chatbots and voice agents. It comes in two editions. Dialogflow CX, now the Flows edition of Google's Conversational Agents, maps large conversations on a visual flow builder, and Dialogflow ES handles smaller bots built from intents. Google Cloud bills the paid editions by usage.

![Google Dialogflow documentation page](https://www.lindy.ai/_sherpa/content/05485af7-dac3-4f67-9438-53ccc4fb7b18.webp)

### In my testing

My order-support agent in Dialogflow CX **fit on one screen**. Order lookup, return request, and refund status each became a page on a visual graph, with every route between them visible. A return question that turned into a refund question moved to the right page in a single turn, and a teammate could review the full logic in minutes.

In my test, questions outside the defined flows received answers from the connected help-center data store, while return requests followed the configured steps. A Phone Gateway number then let the same agent answer a test call, so **chat and voice both ran from one agent.**

### Key features

- **Flows and pages:** Dialogflow CX splits a conversation into flows, and each flow holds pages with their own questions and routes. Large teams can assign one flow per topic, so several builders can edit the same agent at once, each in a separate flow.
- **Playbooks:** Playbooks let you write a generative agent as plain-language instructions. A playbook can handle open-ended requests alongside fixed flows, so one agent can chat freely while still following strict steps for tasks such as refunds.
- **Data stores:** A data store indexes your website or documents, and the agent answers questions from that content. Each month includes 10 GiB of free index storage, so most teams can connect their help center at no storage cost.
- **Phone Gateway:** Phone Gateway gives agents a US phone number, plus speech recognition and voice replies. A team can test a voice bot on a real call with no separate telephony provider.
- **Built-in sentiment analysis:** Conversational Agents scores the sentiment of each user message at no extra charge. Teams can route frustrated customers to a person sooner and track mood across conversations in their reports.

### Limitations

CX and ES are separate products with distinct consoles, APIs, and pricing, so moving an ES agent to CX requires rework. Webhook logic still requires code that runs on your own Google Cloud services. Generative features cost more per request than standard flows.

### Pricing

Dialogflow charges by usage, with no per-user or per-seat fee. Conversational Agents (Dialogflow CX) costs [**$0.007 per text request**](https://cloud.google.com/dialogflow/pricing) and $0.001 per second of audio, or $0.012 per request and $0.002 per second with generative AI. Dialogflow ES has a free Trial Edition with a limited quota, and its Essentials Edition costs $0.002 per text request.

## Best chatbot framework for SMBs who want a visual builder

### Botpress

[**Botpress**](https://botpress.com/) is a chatbot platform that lets a small team build AI support agents. Builders map each conversation on a drag-and-drop canvas, and the bot answers questions from your help docs. One bot can run on a website, WhatsApp, and Slack at once, and Botpress prices its plans based on conversation volume.

![Botpress homepage](https://www.lindy.ai/_sherpa/content/16919966-511b-4874-961b-ac9922de2fba.webp)

### In my testing

Botpress answered class questions for a test fitness studio in its first session. I uploaded the class schedule and membership FAQ to a Knowledge Base, then linked a booking card to a Table of open class slots. The **bot answered questions** about membership freezes and booked a test class in the same chat.

**For a second bot, I gave Botpress Viber a plain-language brief:** a lead form that asks for a name, a fitness goal, and a preferred class time. Viber drafted a working bot, which I could test and refine. I then enabled the WhatsApp channel, and the same bot answered there, too. I built both test bots without writing code, using the Knowledge Base, Tables, and channel settings.

### Key features

- **Studio and Viber:** Botpress offers two ways to build. Studio is a drag-and-drop canvas, while Viber creates a bot from a plain-language description. Both use the same plans and prices, so a team can switch between them on one subscription.
- **Knowledge Bases and Tables:** Knowledge Bases store help docs that the bot answers from, and Tables store structured records such as bookings or orders. Plus includes 100,000 table rows and 1 GB of vector storage, so a small business can keep its data in Botpress.
- **Channels and integrations:** The Botpress Hub offers official integrations for WhatsApp, Messenger, Instagram, Slack, HubSpot, and Salesforce. One bot can reach customers on social apps and write each lead straight into the CRM.
- **Helpdesk handoff:** Botpress connects to Zendesk or Intercom through OAuth, so there is nothing to migrate. Teams without a helpdesk can use Botpress Desk, an AI helpdesk built into the platform, to manage escalated chats.
- **Code options:** The Botpress ADK lets developers build agents in code under the same plans. The older v12 edition is open source on GitHub, and teams that need their data on their own servers can self-host it.

### Limitations

Bots that call APIs or run custom code still need a developer, so non-technical teams face a learning curve on complex builds. Only the older v12 edition supports self-hosting, and your own team must maintain it. Teams that want a lighter setup can compare these [**Botpress alternatives**](https://www.lindy.ai/blog/botpress-alternatives).

### Pricing

Botpress charges by conversation. The Free plan includes 100 conversations with no top-ups and 3 seats. Plus costs [**$189/month**](https://botpress.com/pricing) for 250 conversations and 3 seats, Team costs $939/month for 1,500 conversations and unlimited seats, and Enterprise pricing is custom.

## Best chatbot framework for enterprise teams on legacy systems

### IBM Watsonx Assistant

[**IBM Watsonx Assistant**](https://www.ibm.com/products/watsonx-assistant), formerly called Watson Assistant, is IBM’s platform for building AI chatbots and voice assistants. Teams design conversations as actions in a visual builder, and the assistant searches company content when no action fits. Finished assistants run on web chat, phone lines, SMS, Slack, and WhatsApp through Twilio.

![IBM watsonx Assistant page](https://www.lindy.ai/_sherpa/content/564cc761-a4a1-4f06-bcf7-f0df8586c5da.webp)

### In my testing

My bill-payment assistant in Watsonx Assistant sent every request to either an action or a search result. Each action held the steps for one task, such as checking a balance or scheduling a payment, and one shared identity check served both. Questions outside those tasks were **routed to a related set of help articles**, and the assistant answered them.

The phone integration gave the assistant a working phone number in one step. The same actions answered a test call, and IBM’s speech services handled the voice replies. I then connected a live-agent handoff to Salesforce, and a test escalation reached a human agent in that system.

### Key features

- **Actions with reusable steps:** Each action contains the steps for a single customer task, and builders can reuse shared components across actions. Pre-built templates cover common requests, such as bill payment, so business users can build the basics while developers extend actions with expressions and JSON.
- **Conversational search:** IBM Watsonx Assistant uses IBM Watsonx Discovery and IBM’s Granite language model to answer questions from business content. IBM also offers bring-your-own-search starter kits for tools such as Coveo and Zendesk, so teams can reuse the search systems they already pay for.
- **Phone integration:** The assistant can get a new phone number or connect to an existing SIP provider such as Genesys or Twilio. Contact centers can add the bot to their current phone setup with no change of carrier.
- **Live-agent handoff:** Pre-built integrations hand conversations to agents in Salesforce, Zendesk, Genesys, NICE CXone, and Twilio Flex. Escalated customers reach the right person in the tools the support team already uses.
- **Custom channels and connectors:** A REST API and SDKs let developers build custom chat clients, and webhooks call outside services mid-conversation. An IBM App Connect starter kit adds pre-built connectors for cloud and on-premises apps, so the assistant can read from older internal systems.

### Limitations

IBM Watsonx Assistant fits best inside an existing IBM or contact center stack, so a team starting from scratch faces more setup than lighter builders require. The entry plan costs $578/month, which is a steep start for a small pilot.

### Pricing

IBM now sells Watsonx Assistant as part of Watsonx Orchestrate, with no per-user or per-seat fee. A 30-day free trial is available, Essentials starts at [**$578/month**](https://www.ibm.com/products/watsonx-orchestrate/pricing), Standard starts at $6,360/month, and Premium pricing is custom.

## Best open-source chatbot framework for existing Node.js Slack bots

### Botkit

[**Botkit**](https://github.com/howdyai/botkit) is an open-source Node.js library for building chatbots on messaging platforms such as Slack and Microsoft Teams. Developers write the bot’s logic once, and platform adapters handle each app’s messages, events, and logins. Botkit runs on the Microsoft Bot Framework SDK, so its bots can use Bot Framework dialogs.

![Botkit GitHub repository](https://www.lindy.ai/_sherpa/content/67f16c03-fd29-427d-a8d4-89b47306ec6f.webp)

### In my testing

I used the Yeoman generator to create a test Slack bot in Node.js. It produced a working project with a web server and the Slack adapter already in place. I added a handler for a /standup slash command, and the bot posted a daily check-in prompt to a test channel. The first reply reached Slack within minutes of setup.

The Teams adapter was added to the same project as a separate package. The handler logic remained the same, and the bot responded in a test Teams channel **using an interactive card**. Middleware let me log every incoming message before the bot replied so that I could **inspect traffic from both platforms** in one place.

### Key features

- **Platform adapters:** Separate adapter packages connect one bot to Slack, Microsoft Teams, Facebook Messenger, Webex, Twilio SMS, and web chat. A team can add a platform by installing a package, while the bot logic stays the same.
- **Middleware pipeline:** Middleware runs on every message as it arrives and before each reply goes out. Developers can log traffic, add a language-understanding service, or enrich messages with user data at one point in the code.
- **Conversation dialogs:** Botkit conversations use Bot Framework dialogs to ask a series of questions and store each answer in variables. A bot can collect a multi-step request, such as a vacation booking, inside a single chat thread.
- **Teams extensions:** Version 4.10 added extra Microsoft Teams support, including task modules. Bots can open pop-up forms in Teams, allowing users to complete a request in the app.
- **Project generator and CMS plugin:** A Yeoman generator creates a new Botkit project with the main files in place. An optional plugin connects to Botkit CMS, allowing non-developers to edit bot scripts in a browser.

### Limitations

The Botkit maintainers archived the repository on GitHub in September 2024, so Botkit no longer receives updates or security fixes. Botkit runs only on Node.js and depends on the Bot Framework SDK, which Microsoft has also archived. Developers starting fresh can follow this guide to [**create a Slack bot**](https://www.lindy.ai/blog/create-slack-bot) with current tools.

### Pricing

Botkit is free and open source, with no per-user or per-seat fee. Budget separately for hosting, maintenance, and any paid services connected to the bot.

## Best free chatbot framework for lightweight NLU

### Wit.ai

[**Wit.ai**](https://wit.ai/) is a free natural language understanding (NLU) API from Meta. You send it a text message or voice clip, and it returns the user’s intent and key details, such as a date or product name, as structured data. Your own code then decides how the bot should reply.

![Wit.ai homepage](https://www.lindy.ai/_sherpa/content/bde75e6a-b2c0-4916-a058-f0fb44d05ad0.webp)

### In my testing

I created a test app for a pizza-ordering bot and trained one intent, order\_pizza, with entities for size and topping. After about 20 example sentences, Wit.ai read “two large pepperoni for tonight” and returned the intent, both entities, and the time as structured JSON. The whole setup took one short browser session.

The official Python SDK returned the same result from a short script. A test Node.js app received an identical response. A short voice recording sent to the speech endpoint returned the same intent and entities. I still needed application code to decide the next response.

### Key features

- **Intents, entities, and traits:** Intents capture what the user wants, entities extract details such as sizes or locations, and traits describe the overall message, such as its sentiment. Developers get one clean JSON response, so the bot’s code can act on each field directly.
- **Speech and voice output:** The same API transcribes spoken audio and can turn text into speech. A voice assistant can listen and respond through a single service, so the team avoids wiring in a separate speech provider.
- **Official SDKs:** Meta publishes client libraries for Node.js, Python, Ruby, Go, iOS, Unity, and Unreal. Wit.ai, therefore, fits into web apps, mobile apps, games, and VR projects with very little setup code.
- **Browser training console:** Developers label example sentences in a web console, and the model updates with each new example. Developers can also send training data through the API and load large sets of examples in bulk.
- **Built-in entities:** Ready-made entities recognize common values such as dates, times, numbers, and monetary amounts. A bot can understand “next Friday at 6” or “$40” with no extra training.

### Limitations

Wit.ai handles only language understanding, so your own code must handle dialogue management, channel connections, and hosting. Each Wit.ai app handles a single language, so multilingual bots require separate apps.

### Pricing

Wit.ai is free for commercial and noncommercial use. It has no paid plans and no per-user or per-seat fee.

## Best chatbot framework for customer support with live handoff

### Kommunicate

[**Kommunicate**](https://www.kommunicate.io/) is a customer service platform that combines AI agents, live chat, and a shared inbox. The AI agent answers common questions on your website, mobile app, WhatsApp, or email, and it hands off harder cases to a human agent in the same dashboard. Teams can build agents in Kommunicate or connect an existing Dialogflow bot.

![Kommunicate homepage](https://www.lindy.ai/_sherpa/content/b171712e-adf2-4f86-b7e6-a195271242fc.webp)

### In my testing

I connected an existing Dialogflow test bot to Kommunicate and added the chat widget to a test page. The bot answered shipping questions from its Dialogflow intents, and each conversation appeared in the Kommunicate inbox as it happened. When a test user typed “talk to a person,” the chat moved to a live agent **with the full history visible**.

Kompose, Kommunicate’s no-code builder, handled my second agent, which **used intents and rich message buttons** for order tracking. I then connected the same agent to WhatsApp, and replies there landed in the same inbox as the web chats.

### Key features

- **Bot-to-human handoff:** Kommunicate’s AI agents decide when to answer and when to pass a chat to a person. Escalated chats arrive in the shared inbox with the conversation so far, so customers do not have to repeat themselves.
- **Kompose builder:** Kompose is a no-code builder for intents, rich messages, and conversation steps. Support leads can update answers and buttons on their own, so small changes do not wait on a developer.
- **Dialogflow integration:** Kommunicate connects to an existing Dialogflow agent. Teams keep the intents they have already trained and add live chat and an inbox on top of them.
- **Omnichannel inbox:** Conversations from the website, mobile apps, WhatsApp, Telegram, Instagram, and email arrive in one inbox. Mobile SDKs let developers embed the same chat inside iOS and Android apps.
- **AI email ticketing and agent assist:** AI email ticketing resolves common first-level email questions automatically. The Professional plan adds AI summaries and Agent Assist, so human agents get a recap and suggested replies when they take over.

### Limitations

The Starter plan includes only 250 conversations per month and one team member, so busy teams soon need the Professional plan or paid add-ons. Salesforce and HubSpot integrations are on the Enterprise plan. Teams that mainly want a bot trained on their own documents can compare these [**Chatbase alternatives**](https://www.lindy.ai/blog/chatbase-alternatives).

### Pricing

Kommunicate charges a monthly plan fee plus an extra seat fee, and every paid plan starts with a 30-day free trial. Starter costs [**$40/month**](https://www.kommunicate.io/pricing/) with 1 AI agent, 1 team member, and 250 conversations. Professional costs $200/month with 2 AI agents, 3 team members, and 2,000 conversations. Enterprise pricing is custom.

## Best AI teammate for teams that want chatbot help inside Slack

### Lindy

[**Lindy**](https://www.lindy.ai/) is an AI teammate that lives in your Slack, connects to your tools, and does real work for the whole team. @mention Lindy in a channel, and it answers in the thread with sources. You can also reach Lindy via iMessage, Gmail through the Chrome Extension, and the web app.

![Lindy homepage](https://www.lindy.ai/_sherpa/content/1b4a70f9-64e2-4006-8959-62e5f4baaa66.webp)

### In my testing

A teammate posted a customer’s refund question in the support channel, and no saved reply covered it. I @mentioned Lindy in the thread, and it pulled the answer from past tickets and a Notion doc, **with a source on each point**. I did not have to build a bot first.

Lindy then **drafted a reply in my voice**. It waited for my approval before sending the email and updating the ticket. Later, I texted Lindy from my phone to book a follow-up call with that customer; it checked my calendar and had the invite ready for me to approve.

Lindy starts from what your company already knows in its meetings, tools, and files. Workspace memory grows with each decision, so Lindy becomes more useful to the whole team every week.

### Key features

- **Answers with sources:** Lindy handles team questions by searching every meeting and connected tool at once, then answers in the Slack thread with citations, so your team can check each fact at its source. When Lindy does not know the answer, it says so.
- **Support triage with approvals:** Lindy handles incoming requests by drafting replies based on past cases and routing complex issues to the appropriate person. Anything with outside impact waits for approval, so every reply that reaches a customer has your team's sign-off.
- **Inbox management:** Lindy handles inbox triage and drafts replies in your voice from the context of each thread. In Gmail, the Chrome Extension pins a daily brief and applies smart labels, so Lindy sorts the emails that need you before you open your inbox.
- **Meetings, start to finish:** Lindy handles scheduling from Slack or iMessage, then joins Google Meet, Zoom, and Microsoft Teams as a named participant to record and summarize each call. Recordings and summaries land in a shared library, so anyone can ask Lindy what was decided.
- **Skills and routines:** Lindy handles repeat work through 40+ built-in skills, and you can add your own by explaining a task once. Routines run recurring jobs on schedule, such as "every Monday at 9, send the support summary," so updates arrive with no prompt.

### Limitations

Lindy focuses on your own team’s work, so a public chatbot widget for your website needs a separate no-code [**AI chatbot setup**](https://www.lindy.ai/blog/how-to-build-an-ai-chatbot). Bigger jobs, such as research reports or dashboards, use more credits, and Lindy pauses and notifies the team when credits run out.

### Pricing

Lindy starts at [**$49.99/month per user**](https://www.lindy.ai/pricing) on the Team plan, with 5,000 credits every month, pooled across your whole team. New users get $50 in free credits that last 7 days, with no credit card required. Enterprise pricing is custom and includes HIPAA, a signed BAA, SSO, SCIM, and audit logs.

## Rasa vs. Botpress: which should you pick?

**Rasa** is the better pick for teams with Python developers who need full control and self-hosting. **Botpress** is the better pick for teams that want a visual builder with LLM features and hosting included. Rasa keeps code and data on your own servers, while Botpress runs in the cloud so that a small team can launch faster.

**Here is how the two compare side by side:**

| Factor | Rasa | Botpress |
| --- | --- | --- |
| **Skill level** | Python developers | Non-developers for simple bots, developers for code and APIs |
| **How you build** | Flows in YAML files, custom actions in Python | Studio canvas or the Viber plain-language builder, plus the ADK for code |
| **Hosting** | Self-hosted, locally or in production | Botpress cloud, or self-host the older v12 edition |
| **LLM support** | CALM engine reads messages with a language model, while flows keep business logic fixed | LLMs connect through the Botpress Hub, and paid plans include AI usage credit |
| **Free option** | Developer Edition: 1 bot, up to 1,000 external conversations per month | Free plan: 100 conversations and 3 seats |
| **Paid plans** | Enterprise, custom pricing | Plus $189/month, Team $939/month, Enterprise custom |
| **Best for** | Regulated teams that need full control | SMBs that want a visual builder and a fast launch |

The deciding question is who runs the servers.

## How do you choose the right chatbot framework?

To choose the right chatbot framework, start with your team's skills, then consider hosting, channels, language understanding, and pricing. Developers can work with code-first tools such as Rasa.

**From there, five criteria separate the right pick from the wrong one:**

- **Skill level required:** Code-first frameworks such as Rasa and Microsoft Bot Framework expect developers who write Python, C#, or JavaScript. Low-code builders such as Botpress and Dialogflow CX let a support lead design flows on a visual canvas. No-code tools such as Kommunicate let a support lead run the entire bot from a single dashboard.
- **Self-hosted vs. hosted:** Self-hosted tools such as Rasa keep code and conversation data on your servers, which suits banks, insurers, and healthcare teams. Your team then owns servers, updates, and security. Hosted services such as Amazon Lex and Dialogflow handle the infrastructure and are billed by usage.
- **Channel support:** List the channels your customers use before you compare features. Botpress covers web chat, WhatsApp, and Slack. Amazon Lex publishes to Slack, Messenger, and Twilio SMS, and it connects to Amazon Connect for phone calls. Kommunicate brings web, mobile, WhatsApp, and email into one live-agent inbox.
- **NLU approach:** Intent-based engines such as Dialogflow ES and Wit.ai match each message to trained intents, which keeps answers predictable. LLM-powered tools understand free-form messages with less training. Hybrid designs such as Rasa CALM and Lex Assisted Slot Resolution use a language model to read messages and keep business steps in fixed flows.
- **Pricing model:** Frameworks charge per request, per conversation, or per user, and some charge nothing. Amazon Lex bills per request, so a bot that handles 10,000 text messages costs $7.50 a month. Botpress charges per conversation, and Wit.ai is free. Estimate your monthly message volume first, then price each model against it.

Lindy gives your team an AI teammate in Slack that answers questions with sources and handles the follow-up work. Setup takes about two minutes.

[**Try Lindy free**](https://chat.lindy.ai/signup)**.**

## FAQ

### What is the best open-source chatbot framework?

**Rasa** is the best-known open-source chatbot framework for teams with Python developers, but Rasa Open Source is now in maintenance mode. Its newer CALM engine ships under a free Developer Edition license, which covers one bot and up to 1,000 external conversations a month. Botkit is also open source, but its maintainers archived the repository in 2024.

### Do I need to code to build a chatbot?

No. You don’t need to code to build a chatbot. **Botpress** and **Dialogflow CX** let you design a bot on a visual canvas, and Botpress Viber creates one from a plain-language description. **Lindy** needs no bot design at all and answers team questions in Slack. Code may still be needed for backend connections, custom behavior, authentication, or self-hosted frameworks such as Rasa.

### What is the difference between a chatbot framework and a chatbot platform?

**A chatbot framework** is a set of code libraries that developers use to build and host a bot, while **a** **chatbot platform** is a hosted product where teams build bots in a visual interface. Rasa is a framework that gives full control over code and data. Botpress is a platform that handles hosting and channels for you. This list includes both, because teams often compare them for a first bot.

### Is Microsoft Bot Framework free?

Yes. Microsoft Bot Framework is **free to download** and use. Azure AI Bot Service adds a Free tier with unlimited messages on Teams and Slack, and 10,000 website and app messages per month. Azure hosting costs extra. Microsoft stopped SDK support on December 31, 2025, so new projects should start on the Microsoft 365 Agents SDK.
