110 sources from practitioners, by month and sentiment.
The read is mixed, and it depends on who is talking: teams and leaders lean positive, individual developers are mixed. Trace-level debugging draws the most praise, from 28 of 35 sources. The UI and SDK draw the most concerns, then price in 12, and 16 of the 25 that compared platforms chose another tool.
Positive, mixed and negative sources
354120
The score counts them as 35 positive, 38 mixed and 19 negative votes, one per author. See How the numbers work.
Counted for All practitioners, from 110 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1Trace-Level Debugging28 of 35 sources on it praise itTraces expose model calls, tool calls, and intermediate steps. Inputs, outputs, latency, and tokens help locate a failure.
monday.com wraps each feedAgent run in LangSmith's traceable(), which records every intermediate step and shows which tools ran and what they returned; its evals run on internal monday.com tooling.
"We use an LLM as a judge with specific metrics for each part, and run it on the CI to make sure we have no regressions before deploying to production."
Excerpt, Kamie Shami-Schnitzer
Published Sep 9, 2026self-described: monday.com feedAgent, a deep agent that curates a personal activity feed for each workspace member
Mixed
Aviad Rozenhek, Developer and maintainer of the open-source langsmith-cli
Calls LangSmith excellent for live debugging but warns extended retention costs 10x a base trace and online evaluators can silently upgrade retention, so archives traces to private S3.
Published Aug 21, 2026self-described: Operates LangSmith for live debugging of production AI systems; built an S3/Parquet archive workflow for traces
Lyft reads each AI Assist run's reasoning, help articles and tool calls in LangSmith traces, sends failed traces to an annotation queue where product managers and QA label them, and measures each LLM judge's precision and recall against about 100 hand-labeled examples.
Published Jul 19, 2026self-described: Lyft AI Assist customer-support agents, with LLM judges checked against about 100 hand-labeled pass and fail examples
Mixed
Antaripa Saha and Hamel Husain, AI evals consultants, Parlance Labs
Parlance Labs scored LangSmith's chat agent at 79.5% recall and 77.5% precision against 39 hand-labeled failures, after LangSmith Engine surfaced too few issues to score. LangSmith had the best interface for reading single traces, and several of its wrong findings were marked high severity.
"But it surfaced only a small set of issues, far fewer than a full review turns up, so we could not use it for the 100-trace comparison. We ran the scored experiment with LangSmith’s chat agent instead."
Excerpt, Antaripa Saha and Hamel Husain
Published Jul 11, 2026self-described: 100 production traces from Nurture Boss's apartment-leasing agent, hand-labeled with a domain expert into 39 failures, then given to Braintrust Loop, Arize Alyx, LangSmith and three coding agents
Mason reviews every agent conversation and its tool calls in LangSmith and keeps eval datasets there. He runs the evals in his own promptfoo harness to avoid lock-in, and says LangSmith's displayed costs ignored prompt caching.
Published Jun 22, 2025LangGraph agents Stride built to guide telemedicine patients through at-home treatment by text message
Positive
John Capobianco, YouTube creator building AI agents
Walks through adding @traceable and the OpenAI wrapper to their LangGraph agent, praising waterfalls with latency, tokens and cost, and noting it cost them nothing as an individual.
"…wrapper that wraps around our open AI client so we're just simply going to wrap our openai client and we're going to make traceables at traceable so what does this look like in the code I'm not going to show you myv file but my…"
monday.com's Production Engineering team gives every Infra agent run one parent trace in LangSmith as its audit trail, so the team can reconstruct any run after an incident.
"Each run has one parent trace in LangSmith and JSON logs to stdout, and every call that crosses a boundary is traced so the run can be reconstructed afterwards."
Excerpt, Pablo Sebastian Martinez
Published Oct 26, 2026self-described: monday.com Infra agents platform, where agents resolve infrastructure tickets and approve production pull requests
Added LangSmith tags to NeMo Compass's OpenTelemetry root traces so the engineer can filter traces by issue and compare runs before and after a code change; a live check loaded 160 traces with the tags stored on the root.
Published Oct 22, 2026self-described: NVIDIA NeMo Compass, whose development traces reach LangSmith over OpenTelemetry
Likes LangSmith for traces but exports results to a spreadsheet for paired query comparisons, because LangSmith does not lead them to a screen built for that comparison.
Published Oct 8, 2026self-described: RAG pipeline changes
Mixed
Tyler Norlund (tnorlund), Developer, maintainer of a personal portfolio repo
After canceling LangSmith Plus, strips the paid bulk-export wiring in favor of native S3 traces. Keeps the SDK and opt-in tracing of a fraction of runs on a free org for debugging.
Published Sep 28, 2026self-described: Personal portfolio with LangGraph receipt and QA agents on AWS
Positive
Titus Lim (tituslhy), Data scientist (GitHub profile)
Swaps self-hosted Langfuse and its ClickHouse/MinIO containers for hosted LangSmith tracing, shrinking a local agent template stack from about 47 containers to 14.
Published Sep 3, 2026self-described: Agent template repo (AG-UI / A2UI / A2A) on LangGraph
Akinloye traces every agent from day one and saves failed runs to a dataset. Before each prompt, model, or tool change, Akinloye runs an experiment against the last one and ships only when nothing important regresses.
Published Jun 19, 2026self-described: Agents built with LangChain and LangGraph, traced from day one and tested against datasets before each change
After a three-month evaluation the small team found LangSmith smoothest inside LangChain, but chose Langfuse over its LangChain ties and Enterprise-only self-hosting.
Published May 30, 2026self-described: Small team shipping agents
Wired Claude Code into LangSmith with the official plugin in minutes, gaining traces of LLM calls, tool executions and subagent runs that are otherwise invisible.
Published Apr 4, 2026self-described: Tracing Claude Code sessions, tool calls and subagents with the official LangSmith plugin
Mixed
Aviad Rozenhek, Developer and author of langsmith-cli
Values LangSmith's traces, datasets and evals but found daily use via the web UI and MCP server clunky, measuring the MCP tools at 16,100 tokens of always-loaded context.
Published Jan 15, 2026self-described: Debugging and monitoring production LLM runs from the terminal and from Claude Code
Tracing turned on with just an API key and was the easiest usable tracing UI they found; they call tracing a must-have and would start evals in LangSmith.
Published Dec 22, 2025self-described: Solo learning project: multi-agent newsroom workflow in LangGraph
Positive
Kyle Rush, Maker of Astrid: Personal Shopping Agent
The team became LangSmith power users for traces, datasets, annotation queues and evals, and picked it over Langfuse because of their prior experience and speed.
Published Jun 22, 2025self-described: Astrid personal shopping agent; traces, datasets, annotation queues and evals
Evaluated LangSmith for production evals: strong tracing, but evals feel secondary, US$0.50 per 1k traces after the free tier adds up, and the UI slows with large datasets.
Published Jun 5, 2025self-described: Team running LLMs in production for content generation, customer support and code review assistance
Mixed or negative, 7
Negative
Daniel Payne, Developer (self-described long-time programmer)
Prefers a custom Eve web channel for development because debugging in LangSmith meant digging through raw JSON inputs and outputs, which felt too manual.
Published Sep 16, 2026self-described: Solo app that values building-material photos with a Vercel Eve agent; previously used LangGraph and LangSmith
The Trajectory view sometimes starts at the second turn of a multi-turn trace while the stats panel still counts every turn, so the first turn cannot be reviewed there.
Published Sep 25, 2026self-described: Multi-turn LangGraph application traced to LangSmith Cloud
2Datasets & Evaluations13 of 22 sources on it praise itTeams build datasets from runs and score changes with evaluators, including LLM-as-a-judge. Experiments and annotation queues support review.
Counted for All practitioners.
Positive, 13
Positive
Patrick Porche Jr, product engineer building AI tools with clinicians and operations teams
Replaced Logfire with LangSmith tracing and moved the pipeline's evals from pydantic-evals to LangSmith datasets and experiments, sending only allowlisted keys so patient data stays out of traces.
Published Sep 21, 2026self-described: Medical-necessity review pipeline on Anthropic and Google models, with a patient-data boundary
Positive
Akele Reed and Dave Revere, Principal AI Engineer and Staff AI Engineer, SonderMind
SonderMind clinicians annotate production conversations in a LangSmith annotation queue, and a script turns each annotation into a typed eval that every prompt or model change must pass in CI.
"A clinical SME reviews a production conversation in LangSmith, marks the missed disclosure with an expected observation, and the script writes it to the eval set."
Excerpt, Akele Reed and Dave Revere
Published Jul 25, 2026Sonder, SonderMind's AI mental health coach, with guardrail evals written from clinician annotations
Positive
Nick Ung and Akshay Sharma, data science manager and machine learning engineer, Lyft
Lyft reads each AI Assist run's reasoning, help articles and tool calls in LangSmith traces, sends failed traces to an annotation queue where product managers and QA label them, and measures each LLM judge's precision and recall against about 100 hand-labeled examples.
Published Jul 19, 2026self-described: Lyft AI Assist customer-support agents, with LLM judges checked against about 100 hand-labeled pass and fail examples
Akinloye traces every agent from day one and saves failed runs to a dataset. Before each prompt, model, or tool change, Akinloye runs an experiment against the last one and ships only when nothing important regresses.
Published Jun 19, 2026self-described: Agents built with LangChain and LangGraph, traced from day one and tested against datasets before each change
Uses LangSmith as the orchestration layer for datasets, traces and evaluators, describing it as a full-lifecycle evaluation platform for automated regression pipelines.
Published Mar 31, 2026self-described: Hands-on eval pipeline: reference datasets, heuristic checks and LLM-as-judge (Gemini grading Claude) orchestrated in LangSmith
Added LangSmith's pytest integration so static eval datasets and untracked results become registered datasets and experiments tracked over time, without changing how tests are written.
Published Dec 28, 2025self-described: Production support agent built with LangGraph; pytest evaluators extended with LangSmith experiments
Harvey sends the OpenTelemetry traces of its OpenAI Agents SDK search agent into LangSmith and runs offline evaluations there on queries its legal experts write.
"Centralized evaluation infrastructure that we built using the OpenAI Agent SDK's OpenTelemetry traces enables us to run offline evaluations in LangSmith. We track metrics like hallucination, tool recall, retrieval recall, formatting, and answer quality."
Excerpt, Lysia Li, Varun Nair, Aaron Stern, Pablo Felgueres, Calvin Qi, Philip Cerles
Published Dec 10, 2025self-described: Harvey Agentic Search for legal research, built on the OpenAI Agents SDK
The team became LangSmith power users for traces, datasets, annotation queues and evals, and picked it over Langfuse because of their prior experience and speed.
Published Jun 22, 2025self-described: Astrid personal shopping agent; traces, datasets, annotation queues and evals
LangSmith evals in GitHub CI/CD catch regressions, but the UI gets tricky with large datasets or long experiment histories and filters are not kept in the URL.
Published Jan 27, 2025self-described: Startup; ongoing LLM evaluations with LangSmith evals in GitHub CI/CD
Positive
MarkAZhang, developer of a GAIA benchmark research agent
Moved a LangGraph research agent's tracing, datasets and five evaluators from Langfuse to LangSmith, with a one-time script that ports existing Langfuse datasets.
Published Jun 30, 2026self-described: LangGraph research agent scored on the GAIA benchmark with five evaluators
After a three-month evaluation the small team found LangSmith smoothest inside LangChain, but chose Langfuse over its LangChain ties and Enterprise-only self-hosting.
Published May 30, 2026self-described: Small team shipping agents
Likes LangSmith for traces but exports results to a spreadsheet for paired query comparisons, because LangSmith does not lead them to a screen built for that comparison.
Published Oct 8, 2026self-described: RAG pipeline changes
Mixed
Antaripa Saha and Hamel Husain, AI evals consultants, Parlance Labs
Parlance Labs scored LangSmith's chat agent at 79.5% recall and 77.5% precision against 39 hand-labeled failures, after LangSmith Engine surfaced too few issues to score. LangSmith had the best interface for reading single traces, and several of its wrong findings were marked high severity.
"But it surfaced only a small set of issues, far fewer than a full review turns up, so we could not use it for the 100-trace comparison. We ran the scored experiment with LangSmith’s chat agent instead."
Excerpt, Antaripa Saha and Hamel Husain
Published Jul 11, 2026self-described: 100 production traces from Nurture Boss's apartment-leasing agent, hand-labeled with a domain expert into 39 failures, then given to Braintrust Loop, Arize Alyx, LangSmith and three coding agents
Builds golden eval datasets with LangSmith annotation queues, but HTML inputs are hard to review since custom rendering replaces the editable output pane annotators need.
Published Mar 18, 2026self-described: Team building golden evaluation datasets with annotators
Prompt experiments with a code evaluator auto-convert traces to Extended Data Retention, hitting usage limits that block new experiments; deleting traces does not lower the count.
Published Jul 29, 2025self-described: Comparing prompts in LangSmith experiments against a dataset
Evaluated LangSmith for production evals: strong tracing, but evals feel secondary, US$0.50 per 1k traces after the free tier adds up, and the UI slows with large datasets.
Published Jun 5, 2025self-described: Team running LLMs in production for content generation, customer support and code review assistance
Finds LangSmith handy for high-level eval results and drill-downs, but hard for spotting failure patterns across groups, so builds own charts from its Python library.
Published Feb 6, 2025self-described: Team running LLM output evals in LangSmith, Python
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.LangSmith documents offline evaluation on datasets and online evaluation on production traces, with human, code, LLM-as-judge, decision model, and pairwise evaluators. Its documentation says LLM-as-judge evaluators need careful review of scores and prompt tuning. Evaluation concepts
3Quick SetupAll 11 sources on it praise itEnvironment variables start tracing in LangChain and LangGraph. Other code uses wrappers, decorators, or OpenTelemetry.
Swaps self-hosted Langfuse and its ClickHouse/MinIO containers for hosted LangSmith tracing, shrinking a local agent template stack from about 47 containers to 14.
Published Sep 3, 2026self-described: Agent template repo (AG-UI / A2UI / A2A) on LangGraph
Positive
Juan Cruz Boullosa Gutierrez, contributor to a LangGraph Discord bot
Deleted the bot's own trace recorder, span helpers and readers in favor of LangSmith's LangGraph auto-instrumentation set by environment variables, with every input and output hidden and only allowlisted metadata sent.
Published Jul 16, 2026self-described: LangGraph Discord bot with direct-message and crisis paths, traced with inputs and outputs hidden
Java teams can get LangSmith traces over plain OTLP with no custom instrumentation, though they would add sampling or redaction before shipping full prompts from production.
Published May 30, 2026self-described: Example Quarkus LangChain4j support assistant on Ollama exporting OpenTelemetry traces to LangSmith
Wired Claude Code into LangSmith with the official plugin in minutes, gaining traces of LLM calls, tool executions and subagent runs that are otherwise invisible.
Published Apr 4, 2026self-described: Tracing Claude Code sessions, tool calls and subagents with the official LangSmith plugin
Tracing turned on with just an API key and was the easiest usable tracing UI they found; they call tracing a must-have and would start evals in LangSmith.
Published Dec 22, 2025self-described: Solo learning project: multi-agent newsroom workflow in LangGraph
Positive
Hugo Santana, Builder of Applied, author of The Applied Report
Akinloye traces every agent from day one and saves failed runs to a dataset. Before each prompt, model, or tool change, Akinloye runs an experiment against the last one and ships only when nothing important regresses.
Published Jun 19, 2026self-described: Agents built with LangChain and LangGraph, traced from day one and tested against datasets before each change
Tracing Claude Code into LangSmith works, but traces show only the model name with no token usage or cost, so top-cost traces and model spend cannot be audited.
Published Dec 21, 2025self-described: Tracing Claude Code sessions into LangSmith
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.LangChain and LangGraph code traces with LANGSMITH_TRACING=true and an API key. Other code uses the traceable wrapper, the OpenAI, Anthropic, and Gemini wrappers, or OpenTelemetry spans. Tracing quickstart
Walks through adding @traceable and the OpenAI wrapper to their LangGraph agent, praising waterfalls with latency, tokens and cost, and noting it cost them nothing as an individual.
"…wrapper that wraps around our open AI client so we're just simply going to wrap our openai client and we're going to make traceables at traceable so what does this look like in the code I'm not going to show you myv file but my…"
Gabriel Gouvêa found LangSmith pricing Bedrock's US-geo Claude Sonnet 5 runs at the global rate of US$2.00 per million input tokens, where AWS lists US$2.20, so cost totals for those runs read low.
Published Jul 28, 2026self-described: Hosted LangSmith cost tracking for Claude Sonnet 5 runs through Amazon Bedrock's US cross-region profile
Traces in LangSmith, adversarial evals and CI rubric checks all missed three production failures: a tool's changed response format, an eval set three months stale, and memory that drifted across long sessions.
Published Jul 2, 2026self-described: Production agents traced in LangSmith, with an agent-to-agent adversarial eval tool and custom rubrics in CI
Tracing Claude Code into LangSmith works, but traces show only the model name with no token usage or cost, so top-cost traces and model spend cannot be audited.
Published Dec 21, 2025self-described: Tracing Claude Code sessions into LangSmith
Every concern practitioners raise, most raised first.
1UI & SDK Reliability23 of 25 sources on it raise it as a concernUI delays and outages affect trace review. SDK failures include lost traces, memory growth, and errors reaching application code.
The Trajectory view sometimes starts at the second turn of a multi-turn trace while the stats panel still counts every turn, so the first turn cannot be reviewed there.
Published Sep 25, 2026self-described: Multi-turn LangGraph application traced to LangSmith Cloud
LangSmith's Claude Agent SDK integration recorded no traces at all when an app read the SDK's continuous message stream, the path long-lived multi-turn sessions use, and gave no warning or error.
Published Sep 20, 2026self-described: Interactive multi-turn sessions on the Claude Agent SDK, traced through LangSmith's integration
Negative
Daniel Payne, Developer (self-described long-time programmer)
Prefers a custom Eve web channel for development because debugging in LangSmith meant digging through raw JSON inputs and outputs, which felt too manual.
Published Sep 16, 2026self-described: Solo app that values building-material photos with a Vercel Eve agent; previously used LangGraph and LangSmith
Builds golden eval datasets with LangSmith annotation queues, but HTML inputs are hard to review since custom rendering replaces the editable output pane annotators need.
Published Mar 18, 2026self-described: Team building golden evaluation datasets with annotators
Values LangSmith's traces, datasets and evals but found daily use via the web UI and MCP server clunky, measuring the MCP tools at 16,100 tokens of always-loaded context.
Published Jan 15, 2026self-described: Debugging and monitoring production LLM runs from the terminal and from Claude Code
In a long-running LangGraph app, memory grows significantly only when LangSmith tracing is on; tracemalloc diffs point at the SDK's serialization code.
Published Sep 10, 2025self-described: Long-running Python application on LangGraph and LangChain
After upgrading the LangSmith SDK, every LLM call's trace failed to upload and stayed pending, while a project on an older SDK version kept working until it was upgraded too.
Published Jun 4, 2025self-described: LangGraph app on Ollama and Groq models traced to LangSmith
LangSmith evals in GitHub CI/CD catch regressions, but the UI gets tricky with large datasets or long experiment histories and filters are not kept in the URL.
Published Jan 27, 2025self-described: Startup; ongoing LLM evaluations with LangSmith evals in GitHub CI/CD
Prefers Langfuse: open source, fewer bugs, and cheaper, since LangSmith bills per seat and per trace, charges more for retention past 14 days, and caps it at 400 days even self-hosted.
Mason reviews every agent conversation and its tool calls in LangSmith and keeps eval datasets there. He runs the evals in his own promptfoo harness to avoid lock-in, and says LangSmith's displayed costs ignored prompt caching.
Published Jun 22, 2025LangGraph agents Stride built to guide telemedicine patients through at-home treatment by text message
Evaluated LangSmith for production evals: strong tracing, but evals feel secondary, US$0.50 per 1k traces after the free tier adds up, and the UI slows with large datasets.
Published Jun 5, 2025self-described: Team running LLMs in production for content generation, customer support and code review assistance
Mixed
Karolis Mariunas (kmariunas), Developer (issue author)
Finds LangSmith handy for high-level eval results and drill-downs, but hard for spotting failure patterns across groups, so builds own charts from its Python library.
Published Feb 6, 2025self-described: Team running LLM output evals in LangSmith, Python
Discussed without concern, 2
Mixed
Hamel Husain, AI evals consultant and course instructor (co-written with Shreya Shankar)
Names LangSmith among the eval vendors they meet most, sees little feature difference, often builds custom tools on top, and says vendor prompt management adds indirection.
Published Sep 18, 2026self-described: Advising client teams on eval tooling and vendor selection
A year-long LangGraph Platform (now Deployments) user found it rough early, with poor monorepo support, but says benefits outweighed costs and the product has since matured.
Published Oct 21, 2025self-described: Agents on LangGraph TypeScript SDK hosted on LangGraph Platform / Deployments for about a year
After canceling LangSmith Plus, strips the paid bulk-export wiring in favor of native S3 traces. Keeps the SDK and opt-in tracing of a fraction of runs on a free org for debugging.
Published Sep 28, 2026self-described: Personal portfolio with LangGraph receipt and QA agents on AWS
Calls LangSmith excellent for live debugging but warns extended retention costs 10x a base trace and online evaluators can silently upgrade retention, so archives traces to private S3.
Published Aug 21, 2026self-described: Operates LangSmith for live debugging of production AI systems; built an S3/Parquet archive workflow for traces
Negative
icekarim, developer of the momo personal assistant
When the LangSmith trial ended the assistant had no observability, so the developer moved tracing and a 16-item eval dataset to Langfuse Cloud's free Hobby tier.
Published Aug 5, 2026self-described: Solo assistant on Anthropic models deployed on Cloud Run, with scheduled briefing jobs
GAIA added a self-hosted Langfuse beside LangSmith because LangSmith is paid and its development workspace kept hitting the monthly trace limit; LangSmith kept receiving the same traces in parallel during the move.
Published May 28, 2026self-described: GAIA, an open-source personal AI assistant whose agents, sub-agents and MCP tools are traced in LangSmith
Finds LangSmith's prompt engineering workflow okay-ish but laborious, quickly expensive, and only workable for one-turn prompts; multi-turn never works.
Prefers Langfuse: open source, fewer bugs, and cheaper, since LangSmith bills per seat and per trace, charges more for retention past 14 days, and caps it at 400 days even self-hosted.
Prompt experiments with a code evaluator auto-convert traces to Extended Data Retention, hitting usage limits that block new experiments; deleting traces does not lower the count.
Published Jul 29, 2025self-described: Comparing prompts in LangSmith experiments against a dataset
Evaluated LangSmith for production evals: strong tracing, but evals feel secondary, US$0.50 per 1k traces after the free tier adds up, and the UI slows with large datasets.
Published Jun 5, 2025self-described: Team running LLMs in production for content generation, customer support and code review assistance
Discussed without concern, 2
Negative
Andrew Kaszubski (akaszubski), Developer, maintainer of the autonomous-dev Claude Code plugin
Rejects LangSmith for multi-agent tracing because self-serve is cloud-only, self-hosting is an Enterprise add-on, and traces go to LangChain infra; picks self-hosted Phoenix or Langfuse.
Published Aug 6, 2026self-described: Local-first multi-agent coding harness on Claude Code / claude-agent-sdk
Positive
John Capobianco, YouTube creator building AI agents
Walks through adding @traceable and the OpenAI wrapper to their LangGraph agent, praising waterfalls with latency, tokens and cost, and noting it cost them nothing as an individual.
"…wrapper that wraps around our open AI client so we're just simply going to wrap our openai client and we're going to make traceables at traceable so what does this look like in the code I'm not going to show you myv file but my…"
Published Mar 9, 2025self-described: Own LangGraph agent project instrumented with @traceable and the OpenAI client wrapper
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Plus is US$39 per seat per month with 10,000 base traces included. LangChain's pricing page lists 0.005 LSU per further base trace and 0.0025 LSU to upgrade a trace to extended retention, at US$1 per LSU. Base traces are kept 14 days and extended traces 180 days, and online evaluators and automation rules upgrade the traces they touch unless each opts out. Usage and billing
3LangChain Coupling8 of 9 sources on it raise it as a concernWhether LangSmith feels bound to LangChain and LangGraph, and whether those frameworks pull in LangSmith as a dependency.
Measured that importing core LangChain primitives eagerly loads the whole langsmith SDK, adding roughly 85 to 100 ms of cold start even when nothing is traced.
Published Sep 6, 2026self-described: CLIs, serverless entry points and test collection importing langchain_core
Likes LangGraph's abstractions but feels LangSmith is creeping further into LangChain and LangGraph, with AWS-like lock-in vibes that make them hesitant to invest.
Published Dec 12, 2025self-described: Builds agents with LangGraph workflows
Ruled LangSmith out because it seemed tightly coupled to LangChain, which they had removed, and chose open-source, on-prem Langfuse for data governance.
"Langsmith appeared popular, but we had encountered challenges with Langchain from the same company, finding it overly complex for previous NonBioS tooling. We rewrote our systems to remove dependencies on Langchain and chose not to proceed with Langsmith as it seemed strongly coupled with Langchain."
Excerpt, Amit
Published Mar 5, 2025self-described: NonBioS AI Engineer product; runs consume over a million tokens and about a hundred inference calls in five minutes, with sensitive customer data
After a three-month evaluation the small team found LangSmith smoothest inside LangChain, but chose Langfuse over its LangChain ties and Enterprise-only self-hosting.
Published May 30, 2026self-described: Small team shipping agents
Discussed without concern, 1
Positive
Markus Eisele, Java developer and newsletter author
Java teams can get LangSmith traces over plain OTLP with no custom instrumentation, though they would add sampling or redaction before shipping full prompts from production.
Published May 30, 2026self-described: Example Quarkus LangChain4j support assistant on Ollama exporting OpenTelemetry traces to LangSmith
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.LangSmith documents tracing without LangChain through its SDK wrappers and OpenTelemetry. LangSmith Deployment runs agents built with Google ADK, the Claude Agent SDK, Strands, CrewAI, and AutoGen as well as LangGraph. LangSmith Deployment
4Self-Hosting & Data Control8 of 12 sources on it raise it as a concernTraces can contain prompts and retrieved documents, including customer data. Hosting and region determine where those records live.
Counted for All practitioners.
Raised as a concern, 8
Negative
Andre Kanmegne, on andrelair-platform, his personal homelab project
Removed LangSmith from the RAG backend of his personal homelab platform, which the author calls an external US cloud service sending traces out of an EU-resident cluster, and moved its five LangChain call sites to the Langfuse instance already running in the cluster.
Published Oct 11, 2026self-described: RAG and contract-analysis services on a self-hosted Kubernetes cluster with EU data residency and outbound traffic denied by default
Negative
obarton, contributor to Cue Labs' cue-app repository
Cue Labs retired its LangSmith tracing and moved production tracing and evals to Langfuse, citing data residency for customer messages, personal data and one vendor standard, and kept the option to self-host Langfuse so that data stays inside its own boundary.
Published Oct 9, 2026self-described: Cue Labs' customer-support agents for Instagram direct messages, chat and SMS, built on LangChain and LangGraph
Negative
pallasaisrujan28, developer of an enterprise agent framework
Rejects LangSmith for multi-agent tracing because self-serve is cloud-only, self-hosting is an Enterprise add-on, and traces go to LangChain infra; picks self-hosted Phoenix or Langfuse.
Published Aug 6, 2026self-described: Local-first multi-agent coding harness on Claude Code / claude-agent-sdk
Akinloye, who also wrote a LangSmith evaluation guide, finds LangSmith more polished inside LangChain and LangGraph but picks Phoenix when evaluation data must stay on the team's own machines.
Published Jul 12, 2026self-described: Agent evaluation when traces cannot leave the team's own infrastructure
After a three-month evaluation the small team found LangSmith smoothest inside LangChain, but chose Langfuse over its LangChain ties and Enterprise-only self-hosting.
Published May 30, 2026self-described: Small team shipping agents
Mixed
Aryan Randeriya, founder and CEO of Experience Inc., which builds GAIA
GAIA added a self-hosted Langfuse beside LangSmith because LangSmith is paid and its development workspace kept hitting the monthly trace limit; LangSmith kept receiving the same traces in parallel during the move.
Published May 28, 2026self-described: GAIA, an open-source personal AI assistant whose agents, sub-agents and MCP tools are traced in LangSmith
Ruled LangSmith out because it seemed tightly coupled to LangChain, which they had removed, and chose open-source, on-prem Langfuse for data governance.
"Langsmith appeared popular, but we had encountered challenges with Langchain from the same company, finding it overly complex for previous NonBioS tooling. We rewrote our systems to remove dependencies on Langchain and chose not to proceed with Langsmith as it seemed strongly coupled with Langchain."
Excerpt, Amit
Published Mar 5, 2025self-described: NonBioS AI Engineer product; runs consume over a million tokens and about a hundred inference calls in five minutes, with sensitive customer data
Discussed without concern, 4
Negative
Chris (chrizefan), Owner/approver of tooling decisions at digithings.ai
Approved an epic to replace LangSmith with self-hosted Langfuse on Cloudflare, then on October 9, 2026 switched the plan to Cloudflare-native tracing with MLflow, keeping LangSmith until a dual-run parity window proves the new path.
Published Oct 1, 2026self-described: digithings.ai LangGraph workloads (house-run, OpenWiki, digiquant-baseline)
Mixed
Aviad Rozenhek, Developer and maintainer of the open-source langsmith-cli
Calls LangSmith excellent for live debugging but warns extended retention costs 10x a base trace and online evaluators can silently upgrade retention, so archives traces to private S3.
Published Aug 21, 2026self-described: Operates LangSmith for live debugging of production AI systems; built an S3/Parquet archive workflow for traces
Positive
Markus Eisele, Java developer and newsletter author
Java teams can get LangSmith traces over plain OTLP with no custom instrumentation, though they would add sampling or redaction before shipping full prompts from production.
Published May 30, 2026self-described: Example Quarkus LangChain4j support assistant on Ollama exporting OpenTelemetry traces to LangSmith
Prefers Langfuse: open source, fewer bugs, and cheaper, since LangSmith bills per seat and per trace, charges more for retention past 14 days, and caps it at 400 days even self-hosted.
Published Aug 11, 2025
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Self-hosted LangSmith is an add-on to the Enterprise plan. LangSmith Cloud runs in GCP US, EU, and APAC regions and an AWS US region, and the SDK can hide or mask inputs and outputs before they are sent. Self-hosted LangSmith
5Closed Source & Vendor Dependence4 of 6 sources on it raise it as a concernA preference for open-source or self-hostable tracing over a proprietary platform whose data lives with the vendor.
Counted for All practitioners.
Raised as a concern, 4
Negative
Andrew Kaszubski (akaszubski), Developer, maintainer of the autonomous-dev Claude Code plugin
Rejects LangSmith for multi-agent tracing because self-serve is cloud-only, self-hosting is an Enterprise add-on, and traces go to LangChain infra; picks self-hosted Phoenix or Langfuse.
Published Aug 6, 2026self-described: Local-first multi-agent coding harness on Claude Code / claude-agent-sdk
Likes LangGraph's abstractions but feels LangSmith is creeping further into LangChain and LangGraph, with AWS-like lock-in vibes that make them hesitant to invest.
Published Dec 12, 2025self-described: Builds agents with LangGraph workflows
Prefers Langfuse: open source, fewer bugs, and cheaper, since LangSmith bills per seat and per trace, charges more for retention past 14 days, and caps it at 400 days even self-hosted.
Mason reviews every agent conversation and its tool calls in LangSmith and keeps eval datasets there. He runs the evals in his own promptfoo harness to avoid lock-in, and says LangSmith's displayed costs ignored prompt caching.
Published Jun 22, 2025LangGraph agents Stride built to guide telemedicine patients through at-home treatment by text message
Ruled LangSmith out because it seemed tightly coupled to LangChain, which they had removed, and chose open-source, on-prem Langfuse for data governance.
"Langsmith appeared popular, but we had encountered challenges with Langchain from the same company, finding it overly complex for previous NonBioS tooling. We rewrote our systems to remove dependencies on Langchain and chose not to proceed with Langsmith as it seemed strongly coupled with Langchain."
Excerpt, Amit
Published Mar 5, 2025self-described: NonBioS AI Engineer product; runs consume over a million tokens and about a hundred inference calls in five minutes, with sensitive customer data
Questions the sources split on, with the count on each side.
Evidence remains split
When practitioners weigh LangSmith against another platform, which do they keep?
916
Chose or kept LangSmith, 9 sources
Some kept LangSmith or moved to it from self-hosted Langfuse, for its traces and evals and for fewer containers to run.
Chose another tool, 16 sources
Others picked Langfuse, a local tracer, or plain OpenTelemetry, most often to self-host, to cut cost, or to get away from LangChain.
Evidence remains split
Does LangSmith earn its place outside the LangChain ecosystem?
34
Works well beyond LangChain, 3 sources
Some trace code built without LangChain and find LangSmith just as useful.
Most useful inside LangChain, 4 sources
Others find it most valuable only with LangChain or LangGraph, or feel it ties them to that ecosystem.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Teams and leaders have 19 accounts; GILD prints their sentiment from 20.
Teams and technical leaders
29 sources. Named teams and small companies describe production use and evaluations, with reasons for choosing another platform.
Individual builders
81 sources. Developers describe setup and debugging for their own LLM apps, along with pricing and UI or SDK problems.
All practitioners
110 sources. These accounts combine named teams with small startups and solo developers. Trace volume and hosting requirements differ across these groups.
110 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual builderDevelopers building on the platform on their own81 sources, counted here
Emphasizes Setup, debugging, price, and UI
Small product team2 to 10 engineers, or an unnamed startup team9 sources, counted here
Emphasizes Tracing value and platform choice
Product or platform team11 to 50 engineers, or a named company's team13 sources, counted here
Emphasizes Evaluation workflows and production monitoring
Technical leadershipLeaders setting model and platform choices across teams6 sources, counted here
Emphasizes Evaluation with domain experts, self-hosting, and tool choice
Organization-wideEnterprise or company-wide AI platform1 sources, counted here
Emphasizes Watching every agent on an enterprise platform
What changes with scale. Individual developers praise setup and trace debugging. They report pricing concerns, SDK bugs, and a slow UI. Named teams describe evals reviewed by clinicians, lawyers, and operations staff, many of them at LangChain's Interrupt conference, which counts toward nothing. Small teams that left chose Langfuse to self-host, to keep trace data in their own boundary, or for distance from LangChain.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 110 sources. Change group
125 sources for this group, 15 of them documentation
Developer Communities69, 55% of 125 sources
Engineering Blogs & Reviews26, 21% of 125 sources
Podcasts, Talks & Videos15, 12% of 125 sources
Product Documentation15, 12% of 125 sources
Earlier evidence remains when it still applies. Records tied to changed prices, retention periods, or product names carry Needs a recheck.
Nov 1, 2026: since Oct 30 the page prints one vote per author, and a figure given on the weighted reading is the second view. Individual builders read +14 and all practitioners +17; teams and leaders are unscored.
Oct 28, 2026: adds 16 accounts. They are Parlance Labs' 100-trace test of LangSmith Engine, Lyft's AI Engineer World's Fair 2026 talk, pull requests in which Cue Labs, GAIA, an insurance platform's team and five developers moved onto or off LangSmith, an NVIDIA engineer's OpenTelemetry tags, four GitHub issues and one Reddit post. Leaders and teams reach 20 counted sources from 20 authors and now print a score; all practitioners move from +20 to +19, now Mixed. Six records show their ledger passage on the Signals page.
Every source record links to a public page and names its author and publication date.
The page shows a finding when at least 5 sources from 3 different authors discuss it. A disagreement also requires at least 2 sources on each side.
Keeps LangChain's own blog posts and customer stories out of the practitioner count; conference talks by customers at LangChain's Interrupt conference are counted and labeled as such.
Checks the pricing, retention, self-hosting, and LangChain-coupling findings against LangChain's current documentation.
Oct 25, 2026: adds Hamel Husain's side-by-side evals tool panel, 2 posts by a London AI engineer, and 5 GitHub issues with reproductions.
Oct 26, 2026: adds leader and team accounts from Stride, Tavily, SonderMind, Harvey, and monday.com, taken from AI Engineer conference transcripts and company engineering blogs. Evan Kormos's role at Coinbase is as his AI Engineer speaker page states it.
Oct 30, 2026: a second-model check moved one pull request to individual builders, because its author's andrelair-platform, earlier counted as an insurance platform's team, is his personal homelab. On the weighted reading, leaders and teams fall to 19 counted sources, one short of a score, and all practitioners move from +19 to +18. Lyft's speakers' roles are as their talk states them, Cue Labs' author is a contributor to its repository, and GAIA's card keeps to its May pull request and names its author by his GitHub handle, aryanranderiya, as the pull request does. It also corrected monday.com's CI judge, which checks for regressions before deploying, the posting dates of SonderMind's and SuperDial's talks, and Parlance Labs' card.
Method
A running review of what teams building AI features on LangSmith report, from individual builders to company-wide platforms. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Teams and technical leaders
Small product team, Product or platform team, Technical leadership, Organization-wide
Individual builders
Individual builder
All practitioners
Everyone in the teams and leaders and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among technical leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +18 mixed (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +20 Positive; with one vote per author it reads +19 Mixed. No evidence changed.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: teams and leaders 1 of 19, individual builders 10 of 77, all practitioners 11 of 96.
Limits
These figures describe 110 practitioner accounts; they do not represent all LangSmith users. GitHub issues are bug reports and feature requests, which tilt GitHub toward problems, so a bug report counts as mixed unless its author rejects LangSmith. GitHub pull requests show a team changing its own setup, toward LangSmith or away from it. Ten of the 15 talks are customer talks at LangChain's Interrupt conference, published on LangChain's own channel, so they are listed and not counted. Reddit posts and comments come from r/LangChain, r/LLMDevs and r/AI_Agents through the Arctic Shift archive; posts that promote another tool are left out.
Sources state plan names and retention periods inconsistently. Each record preserves what its source says. LangGraph Platform and LangGraph Cloud are now LangSmith Deployment. Agent Builder is now LangSmith Fleet. SaaS extended retention fell from 400 to 180 days on September 14, 2026. Records tied to earlier terms carry Needs a recheck.
Every count, and the sources behind it
19 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Datasets & Evaluations. LangSmith documents offline evaluation on datasets and online evaluation on production traces, with human, code, LLM-as-judge, decision model, and pairwise evaluators. Its documentation says LLM-as-judge evaluators need careful review of scores and prompt tuning. Evaluation concepts, checked Oct 12, 2026
Quick Setup. LangChain and LangGraph code traces with LANGSMITH_TRACING=true and an API key. Other code uses the traceable wrapper, the OpenAI, Anthropic, and Gemini wrappers, or OpenTelemetry spans. Tracing quickstart, checked Oct 12, 2026
Seat & Trace Pricing. Plus is US$39 per seat per month with 10,000 base traces included. LangChain's pricing page lists 0.005 LSU per further base trace and 0.0025 LSU to upgrade a trace to extended retention, at US$1 per LSU. Base traces are kept 14 days and extended traces 180 days, and online evaluators and automation rules upgrade the traces they touch unless each opts out. Usage and billing, checked Oct 12, 2026
Self-Hosting & Data Control. Self-hosted LangSmith is an add-on to the Enterprise plan. LangSmith Cloud runs in GCP US, EU, and APAC regions and an AWS US region, and the SDK can hide or mask inputs and outputs before they are sent. Self-hosted LangSmith, checked Oct 12, 2026
LangChain Coupling. LangSmith documents tracing without LangChain through its SDK wrappers and OpenTelemetry. LangSmith Deployment runs agents built with Google ADK, the Claude Agent SDK, Strands, CrewAI, and AutoGen as well as LangGraph. LangSmith Deployment, checked Oct 12, 2026