Comparisons / CrewAI vs Rasa
CrewAI vs Rasa: Which Agent Framework to Use?
CrewAI crewai organizes work into agents, tasks, and crews. Rasa rasa is an open-source framework for building conversational ai — chatbots and virtual assistants. Here is how they compare — and what the same patterns look like in plain Python.
By the numbers
CrewAI
48.0k
6.5k
Python
MIT
2023-10-27
João Moura
Rasa
21.1k
4.9k
Python
Apache-2.0
2016-10-14
Rasa Technologies
Rasa Pro / Rasa Cloud
Yes
GitHub stats as of April 2026. Stars indicate community interest, not necessarily quality or fit for your use case.
| Concept | CrewAI | Rasa | Plain Python |
|---|---|---|---|
| Agent | Agent(role, goal, backstory, tools, llm) | Rasa agent with NLU pipeline, dialogue policies, and action server | A function with a system prompt and a tools dict |
| Tools | Tool registration with @tool decorator, custom Tool classes | Custom actions running on a separate action server via HTTP | A dict: tools[name](**args) |
| Agent Loop | Internal to Agent execution, hidden from user | — | A while loop over messages with tool_calls check |
| Task Delegation | Crew(agents, tasks, process=sequential/hierarchical) | — | A task queue processed in a while loop with a budget cap |
| Memory | ShortTermMemory, LongTermMemory, EntityMemory | — | A dict injected into the system prompt |
| State | Task output passed between agents via Crew orchestration | — | A dict tracking tool calls and results |
| NLU | — | NLU pipeline: tokenizer, featurizer, intent classifier, entity extractor | An LLM call with a prompt: "Classify this message's intent: {message}" |
| Dialogue | — | Stories/Rules YAML + dialogue policies for conversation flow | A state machine: if intent == 'greet': state = 'greeting'; respond() |
| Slots | — | Typed slots for tracking entities and state across turns | A dict updated during conversation: slots = {"order_id": "123"} |
| CALM | — | LLM for understanding + deterministic Flows for business logic | LLM parses user intent, if/else routes to the right handler function |
What both do in plain Python
Every concept in the table above — agent, tools, loop, memory, state — maps to a handful of Python primitives: a function, a dict, a list, and a while loop. Both CrewAI and Rasa wrap these primitives in their own class hierarchies and APIs. The underlying pattern is the same ~60 lines of code. The difference is how much ceremony each framework adds on top.
When to use CrewAI
CrewAI shines for multi-agent setups where you want named roles ("researcher", "writer"). But the core mechanics — tool dispatch, the agent loop, task scheduling — are the same patterns you can build in plain Python.
What CrewAI does
CrewAI models multi-agent systems as a crew of specialists. Each Agent has a role ("Senior Researcher"), a goal ("Find the best data sources"), a backstory that shapes its behavior, and a set of tools it can use. Tasks define discrete units of work with expected outputs. The Crew orchestrates execution — sequentially, hierarchically, or with a custom process. CrewAI also provides memory systems (short-term, long-term, entity) and delegation, where one agent can hand off subtasks to another. The mental model is a team of people collaborating on a project. For prototyping multi-agent workflows where you want to reason about roles and responsibilities, it provides a clean vocabulary.
The plain Python equivalent
An Agent in CrewAI is a function with a system prompt that includes the role, goal, and backstory. The tools dict maps names to callables. Task delegation is a list of tasks processed in order — each task calls the assigned agent function with the task description appended to the messages. Hierarchical execution is a manager agent that decides which sub-agent to call next (just another tool choice). Memory is a dict injected into the system prompt. The entire crew pattern — multiple agents, task queue, delegation — is a for-loop over tasks, where each iteration calls the right agent function. No Crew class, no process kwarg. Just functions calling functions with a shared state dict passed between them.
When to use Rasa
Rasa is purpose-built for production conversational AI with enterprise requirements — on-premise deployment, regulatory compliance, deterministic business logic. For general-purpose agents or simple chatbots, an LLM with a system prompt and a few tools is faster to build and more flexible.
What Rasa does
Rasa provides a complete framework for building conversational AI systems. The traditional stack includes an NLU pipeline (intent classification and entity extraction), dialogue management (stories and rules that define conversation flows), and an action server for custom business logic. The newer CALM architecture separates language understanding (handled by LLMs) from business logic (handled by deterministic Flows), giving you LLM fluency without sacrificing reliability. Rasa focuses on enterprise requirements: on-premise deployment, data privacy, regulatory compliance, and deterministic behavior for critical business flows. You define your domain in YAML — intents, entities, slots, responses, actions — and Rasa trains a model that handles the conversation lifecycle. The framework is battle-tested in production across banking, telecom, and healthcare.
The plain Python equivalent
Intent classification is one LLM call: send the user's message with a prompt asking for the intent and entities, parse the JSON response. Dialogue management is a state machine — a dict tracking the current state and a series of if/else branches routing to the next step. Custom actions are functions you call based on the classified intent. Slot filling is updating a dict as entities are extracted. The entire conversational agent — intent handling, state tracking, tool dispatch, response generation — fits in about 60 lines. The LLM handles the language understanding that Rasa's NLU pipeline was trained for, and your if/else logic handles the flows that Rasa's dialogue policies managed. No YAML domain files, no training pipeline, no action server.
Or build your own in 60 lines
Both CrewAI and Rasa implement the same 8 patterns. An agent is a function. Tools are a dict. The loop is a while loop. The whole thing composes in ~60 lines of Python.
No framework. No dependencies. No opinions. Just the code.
Build it from scratch →