Guidance vs Dspy

Guidance and Dspy are both popular ml inference & agents tools. This page compares their internal architecture, technology stack, data flow patterns, and system behavior — based on automated structural analysis of their source code. They share 2 technologies including pydantic, openai.

guidance-ai/guidance

21,366

Stars

Jupyter Notebook

Language

Components

0.8

Connectivity

stanfordnlp/dspy

33,164

Stars

Python

Language

Components

2.1

Connectivity

Technology Stack

Shared Technologies

pydantic openai

Only in Guidance

llguidance numpy transformers llama-cpp-python jupyter-widgets svelte

Only in Dspy

litellm json_repair tenacity diskcache pytest asyncer

Architecture Layers

Guidance (4 layers)

Grammar Language

AST nodes, grammar functions, and language constructs for defining constraints

Parser & Interpreter

Token parsing, constraint enforcement, and generation control using llguidance

Model Backends

Adapters for different LLM providers (OpenAI, Transformers, llama.cpp)

Visualization & Tools

Jupyter widgets, tracing, and development tools

Dspy (5 layers)

Signatures & Types

Type-safe interfaces defining input/output contracts with custom types like Image, Audio, Tool

Adapters

Interface layer between DSPy and language models, handling format conversion and parsing

Modules

Composable building blocks like Predict, ChainOfThought, ReAct for creating AI programs

Optimizers

Algorithms for automatically improving prompts and weights through teleprompt techniques

Clients & Infrastructure

LM clients, caching, evaluation, and utility functions for the framework

Data Flow

Guidance (5 stages)

Function Definition
Grammar Compilation
Token Generation
Constraint Enforcement
State Update

Dspy (6 stages)

Signature Definition
Module Creation
Adapter Processing
LM Execution
Response Parsing
Optimization

System Behavior

Dimension	Guidance	Dspy
Data Pools	3	2
Feedback Loops	3	3
Delays	3	3
Control Points	4	4

Code Patterns

Unique to Guidance

ast pattern backend adapter constraint compilation widget messaging

Unique to Dspy

adapter pattern type system signature-based programming composable modules optimization framework

When to Choose

Choose Guidance when you need

Unique tech: llguidance, numpy, transformers
Loosely coupled, more modular

View full analysis →

Choose Dspy when you need

Unique tech: litellm, json_repair, tenacity
Tighter integration between components

View full analysis →

Frequently Asked Questions

What are the main differences between Guidance and Dspy?

Guidance has 10 components with a connectivity ratio of 0.8, while Dspy has 10 components with a ratio of 2.1. They share 2 technologies but differ in 12 others.

Should I use Guidance or Dspy?

Choose Guidance if you need: Unique tech: llguidance, numpy, transformers; Loosely coupled, more modular. Choose Dspy if you need: Unique tech: litellm, json_repair, tenacity; Tighter integration between components.

How does the architecture of Guidance compare to Dspy?

Guidance is organized into 4 architecture layers with a 5-stage data pipeline. Dspy has 5 layers with a 6-stage pipeline.

What technology does Guidance use that Dspy doesn't?

Guidance uniquely uses: llguidance, numpy, transformers, llama-cpp-python, jupyter-widgets. Dspy uniquely uses: litellm, json_repair, tenacity, diskcache, pytest.

Explore the interactive analysis

See the full architecture maps, code patterns, and dependency graphs.

Guidance Dspy

Related ML Inference & Agents Comparisons

Compared on March 25, 2026 by CodeSea. Written by Karolina Sarna.