Langfuse vs LangSmith
Of the 117 makers' products we know the LLM observability & evals of, 35 chose Langfuse (30%) and 11 LangSmith (9%). Among the 33 launched in 2025, Langfuse is in 45% and LangSmith in 18%. At our calculator's default usage, Langfuse comes to $29 a month and LangSmith $475, at list prices. On GitHub, 0 public pull requests moved projects from Langfuse to LangSmith, and 9 the other way.
Two sides of the LLM observability & evals decision: open-source platform and hosted eval platform. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- You want tracing, prompts and evals in one tool you can self-host for free
Use it whenYou want to own your trace data or keep costs flat as volume grows.
Trade-offSelf-hosting means running Postgres, ClickHouse, Redis and object storage alongside it; otherwise it's a usage-based cloud plan.
- Your app is built on LangChain or LangGraph
Use it whenYou already use the LangChain stack.
Trade-offPaid per seat beyond the free tier; self-hosting is enterprise-only.
At a glance
| Used by | 35 makers' products · 58 open-source projects | 11 makers' products · 62 open-source projects |
|---|---|---|
| Cost at default usagetraces 100k traces | $29/mo Core | $475/mo Developer |
| Moved to it on GitHubpull requests since Oct 2024 | 9 from LangSmith | fewer than 3 |
| Downloads | 1.7M/wk+57% vs npm | 6.2M/wk−8% vs npm |
| Pricing | Free tier (50k units/mo); usage-based paid plans; fully free to self-host under MIT license. · paid from $29/mo | Free tier with a monthly trace limit; paid per-seat plan with usage overage; custom Enterprise, including self-hosted. · paid from $39/seat/mo |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | No |
| Incidents, 90 daysfrom its status page | 14 (1 major) | 0 |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for LLM observability & evals.
| Framework | |||
|---|---|---|---|
| 12 | 4 | All 48 Next.js products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the LLM observability & evals decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2024 | 38% 8 | 19% 4 | 21 |
| 2025 | 45% 15 | 18% 6 | 33 |
Cost as you grow
Both cost $0 up to 1k traces; from 10k traces Langfuse costs less ($0 vs $25); and still does at 10M traces ($821 vs $49,975). They're different kinds of tool — open-source platform and hosted eval platform — so the prices don't buy the same thing.
The numbers, plan by plan
| Traces per month | Langfuse | LangSmith |
|---|---|---|
| 1,000 | $0 Hobby | $0 Developer |
| 10,000 | $0 Hobby | $25 Developer |
| 50,000 | $0 Hobby | $225 Developer |
| 100,000 | $29 Core | $475 Developer |
| 500,000 | $61 Core | $2,475 Developer |
| 1,000,000 | $101 Core | $4,975 Developer |
| 5,000,000 | $421 Core | $24,975 Developer |
| 10,000,000 | $821 Core | $49,975 Developer |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Langfuse to LangSmith" or the reverse — real code changes, by developers in general rather than makers only.
- Migrate observability from LangSmith to Langfuse and trim logged fieldsHOSH19/HarnessLab · 2026-08-29
- feat: migrate observability from LangSmith to Langfuse Cloud (v4 SDK)icekarim/momo-assistant · 2026-08-05
- feat(trace): migrate LangSmith to Langfuse v4 and fix env key priority1935494577/Xiaoxin-Agentic-RAG-System · 2026-08-01
- [codex] Migrate from LangSmith to Langfuse, remove Python legacy, fix review issuesBunnyRabbit8mile/codex-tee · 2026-07-14
- Reapply "feat: migrate observability from LangSmith to Langfuse"sinuarlowbaby/RAG-PDF-Chatbot · 2026-07-14
- refactor: migrate observability from LangSmith to Langfusewei-yiting/fin-lab-x · 2026-03-18
- Migrate observability from LangSmith to LangfuseAneeshPulukkul/hybrid-rag-solution · 2026-03-14
- feat:migrate LLM observabilty from LangSmith to LangFuse100-hours-a-week/17-JinyUs-Q-Feed-AI · 2026-02-26
- Refactor: Migrate from Langsmith to Langfusedylangamachefl/fantasy-football-chatbot-v2 · 2025-12-01
What makers say
Makers on using it for LLM observability & evals, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
Marc gave me an in-person onboarding in SF - I found an issue in our LLM provider config just 30 minutes after the onboarding thanks to Langfuse. 10/10 recommendation
Observability for LLM apps and agents Langfuse helps us trace, debug, and improve agent quality across the platform.
We use it to trace every model call in Flowstep, super useful for debugging
LangSmith’s real-time analytics and versioning keep our AI agents rock-solid -- so everything just works better.
You can't build AI agents without monitoring. Metadata filtering is strong.
I deployed the manage Pig agent on LangGraph and it's been smooth sailing!
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Detailed traces show each agent call and the context it pulled, which makes debugging agent behaviour much easier. PHPH 2HN
- Token usage and cost are tracked across providers alongside quality, in one place. PHPH 2HN
- Open source and self-hostable, a common default for teams wanting tracing on their own infrastructure. PHHNHN 2HN 3
- Prompt management and experiments feel basic next to the tracing core. HNHN 2HN 3
- Views are retrospective dashboards, so explaining one run's cost or failure still means reading trace trees by hand. HNHN 2HN 3HN 4
- The ClickHouse acquisition raised GDPR and data-residency concerns for EU users of the cloud version. HNHN 2
- It keeps pulling users toward the LangChain platform, and LangChain docs push LangSmith, which feels like lock-in. HNHN 2HN 3HN 4
- Traces show which agent failed but not why, so root-cause analysis stays manual. HNHN 2HN 3HN 4
- Viewing your own traces requires a cloud account, with no local-first option. HNHN 2
Who uses each
What makers pair each with
Neither quite right?
See the whole LLM observability & evals decision →Questions
Langfuse or LangSmith: which do makers choose?
Of the 117 makers' products we know the LLM observability & evals of, 35 chose Langfuse (30%) and 11 LangSmith (9%). Among the 33 launched in 2025, Langfuse is in 45% and LangSmith in 18%. At our calculator's default usage, Langfuse comes to $29 a month and LangSmith $475, at list prices. On GitHub, 0 public pull requests moved projects from Langfuse to LangSmith, and 9 the other way. Choose Langfuse if you want tracing, prompts and evals in one tool you can self-host for free; choose LangSmith if your app is built on LangChain or LangGraph.
When should I pick Langfuse over LangSmith?
Pick Langfuse if: You want tracing, prompts and evals in one tool you can self-host for free.
When should I pick LangSmith over Langfuse?
Pick LangSmith if: Your app is built on LangChain or LangGraph.
Which is cheaper, Langfuse or LangSmith?
At traces 100k traces: Langfuse $29/mo (Core), LangSmith $475/mo (Developer), at list prices.
How do Langfuse and LangSmith compare in cost as you grow?
Both cost $0 up to 1k traces; from 10k traces Langfuse costs less ($0 vs $25); and still does at 10M traces ($821 vs $49,975). Cheapest usable plan at each scale, at list prices.
Are people switching from Langfuse to LangSmith?
Public GitHub pull requests since 2024-10-02: 9 from LangSmith to Langfuse.

