Comparisons / DSPy vs Rasa

DSPy vs Rasa: Which Agent Framework to Use?

DSPy vs Rasa, head to head

DSPy and Rasa both let you build an agent, but they sit in different parts of the stack and they assume different things about who's writing the code.

DSPy replaces hand-written prompts with compiled modules.

Rasa is an open-source framework for building conversational AI — chatbots and virtual assistants.

Underneath, both wrap the same thing: a model call, a tool dispatch, a loop. The decision is about which abstraction your team wants to think in day to day, and which ecosystem you're willing to inherit along with it. There's an honest, framework-free version of the same pattern in about 60 lines of Python in the lesson at the bottom of this page — useful as a baseline regardless of which framework wins.

Pick DSPy if

Pick DSPy if dSPy's real innovation is automated prompt optimization — replacing manual prompt engineering with algorithmic tuning. This is genuinely novel and valuable for production systems where prompt quality matters at scale. For simple agents or learning, hand-written prompts are easier to understand and modify. The tradeoffs in its intro should match how your team already thinks about agents; Rasa will feel like translation if they don't.

Full DSPycomparison →

Pick Rasa if

Pick Rasa if 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. The tradeoffs in its intro should match how your team already thinks about agents; DSPy will feel like translation if they don't.

Full Rasacomparison →

What both add

Whichever you pick, you're inheriting a dependency tree and a vocabulary your team has to learn before they ship anything. DSPy has its own class hierarchy and tool registration conventions; Rasa has its. Either way, when something misbehaves you'll be reading framework source before you reach the actual HTTP call.

If the real workload is one model and a handful of tools, both can feel like a workbench for driving a nail. The lesson below builds the same pattern in plain Python — useful as a comparison point even if you ultimately keep the framework.

By the numbers

By the numbers

DSPy

GitHub Stars

33.4k

Forks

2.8k

Language

Python

License

MIT

Created

2023-01-09

Created by

Stanford NLP (Omar Khattab)

github.com/stanfordnlp/dspy

Rasa

GitHub Stars

21.1k

Forks

4.9k

Language

Python

License

Apache-2.0

Created

2016-10-14

Created by

Rasa Technologies

Cloud/SaaS

Rasa Pro / Rasa Cloud

Production ready

Yes

github.com/RasaHQ/rasa

GitHub stats as of April 2026. Stars indicate community interest, not necessarily quality or fit for your use case.

ConceptDSPyRasa
Agent`dspy.ReAct` module with signature and toolsRasa agent with NLU pipeline, dialogue policies, and action server
Prompts`dspy.Signature` defines input/output fields, compiled to optimized prompts
Optimization`dspy.BootstrapFewShot`, `MIPROv2` auto-tune prompts against a metric
ToolsTools passed to `ReAct` module as callable listCustom actions running on a separate action server via HTTP
Chaining`dspy.ChainOfThought`, `dspy.Module` with `forward()` composition
Evaluation`dspy.Evaluate` with metric functions and dev sets
NLUNLU pipeline: tokenizer, featurizer, intent classifier, entity extractor
DialogueStories/Rules YAML + dialogue policies for conversation flow
SlotsTyped slots for tracking entities and state across turns
CALMLLM for understanding + deterministic `Flows` for business logic

Or build your own in 60 lines

Both DSPy 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 →