Direct SDKs (no framework) vs DSPy
Both are free/open-source alternatives to LangChain. Here's how they stack up — verified facts, no spin.
Direct SDKs (no framework)
TOP PICKThe 2026 consensus: official SDKs + a few hundred lines you own.
The strongest LangChain alternative today is often no framework at all. Modern models ship native tool calling, structured outputs, and long context — the very things LangChain was built to scaffold — so the official Anthropic/OpenAI/Mistral SDKs (MIT/Apache-licensed) plus a small amount of your own orchestration code covers most real applications. You keep full debuggability (a stack trace is your code, not five layers of framework), zero dependency churn, and total freedom to swap providers. Engineering write-ups since 2024 keep landing on the same conclusion: start direct, add a framework only when a specific need demands it — not the other way around.
DSPy
Programming, not prompting — Stanford's optimizer-driven approach.
DSPy (MIT, from Stanford NLP, ~34k stars) replaces hand-tuned prompt strings with something closer to software engineering: you declare what a step takes in and produces (a Signature), compose modules, and let an optimizer compile the best prompts and few-shot examples against your own metric and data. When quality matters and you're tired of prompt whack-a-mole, DSPy turns the tuning into a reproducible build step. It's the most intellectually distinct alternative on this list.
Side by side
| Direct SDKs (no framework) | DSPy | |
|---|---|---|
| Sovereignty Score | 93 | 88 |
| Open source | Yes | Yes |
| Self-hostable | Yes | Yes |
| Local-first | Yes | Yes |
| License | Your code (official SDKs: MIT / Apache-2.0) | MIT |
| Pricing | Free — you pay only your model provider; no framework tier, no per-seat tooling | Free (MIT) |
Direct SDKs (no framework) is Macrostack's recommended LangChain alternative, so it's our pick here.
Direct SDKs (no framework)
Strengths
- +Every line is yours: debugging is a stack trace, not archaeology
- +No abstraction churn or breaking framework releases
- +Trivially swaps model providers; pairs cleanly with MCP for tools
- +Less code than the equivalent chain in many real apps
Trade-offs
- −You write your own retries, streaming, and evaluation plumbing
- −Big multi-agent orchestration is where hand-rolling gets costly
DSPy
Strengths
- +Optimizes prompts against your metric — reproducibly
- +Declarative modules stay stable as models change underneath
- +Research-grade ideas with a real production following
Trade-offs
- −A genuinely different mental model — real learning curve
- −Optimization runs cost tokens; needs a decent eval set
More LangChain head-to-heads
Facts verified 2026-07-16. Licenses and pricing change — spotted something out of date? That's a correction we want.