Skip to main content

Buyer guide

LangSmith Trace Spend & Retention Checklist

What tracing costs a month, and what changes on the way from a trial to production traffic or from the Developer plan to Plus, in eight checks.

Reading time
3 min read
Sources
8 cited
In this piece
LangSmith+17 Mixed

Set each project's default retention before traffic starts, turn off retention upgrades on evaluators that do not need them, and set a monthly usage limit. A trace kept 180 days costs 50% more than a 14-day trace, and LangSmith bills seats, traces and LSU-metered products separately. The limit also has to leave room for experiments, which stop when it is reached.

When you need this

  • You are moving from the Developer plan to Plus, or from a trial to production traffic.
  • Online evaluators or automation rules are about to run on production projects.
  • Finance asks what tracing costs per month, or experiments stop because a usage limit was reached.

Evaluation criteria

  1. Count seats

    Who needs an account?

    Look forCount every distinct organization user, including invited users, at US$39 per seat per month on Plus. Seats bill on the 1st. LangSmith prorates seats added mid-month and gives no credit for seats removed.

  2. Price the traces

    How many traces does the application produce each month?

    Look forA trace is one execution of the application, however many runs it contains, up to 25,000. Plus includes 10,000 base traces a month. Each base trace past that costs 0.005 LSU, billed monthly in arrears. Developer includes 5,000 traces a month and stops there until someone adds a card.

  3. Choose the default tier

    Which projects need traces kept longer than base retention?

    Look forBase keeps traces 14 days. Extended keeps them 180 days for an extra 0.0025 LSU per trace. Set the tier per tracing project, or per environment in an agent-based workspace. A change applies only to new traces.

  4. Control automatic upgrades

    Which features move a trace to extended retention?

    Look forCheck each online evaluator and automation rule for automatic retention upgrades. New rules and evaluators have the upgrade on by default. Thread-level rules upgrade every trace in the thread. API feedback upgrades only with extend_trace_retention. UI feedback and manual annotation-queue additions leave retention unchanged. Experiment runs start at extended retention.

  5. Keep what matters longer, for less

    How do you keep a slice of traces without paying for all of them?

    Look forAn automation rule with a sampling rate or a filter, for example 10% of traces or every errored trace, upgrades only that slice. For anything needed past extended retention, a rule that copies inputs and outputs into a dataset keeps them indefinitely.

  6. Confirm the rate

    Which per-trace price is your budget built on?

    Look forBudget from LangChain's pricing page, which is binding. The usage and billing docs list no per-trace price and point to it. On October 12, 2026 the page lists 0.005 LSU per base trace past the included volume, which is US$5 per 1,000 at US$1 per LSU. Upgrading a trace costs 0.0025 LSU, or US$2.50 per 1,000 for extended retention. Accounts from 2025 and August 2026 cite US$0.50 per 1,000 base traces and 400-day extended retention, the list price before 2026. LangChain cut SaaS extended retention to its current length on September 14, 2026. Check the first invoice against the page.

  7. Set usage limits

    What stops spend at the cap?

    Look forOpen Usage limits under Billing and Usage in Settings. Enter a monthly workspace spend limit. LangSmith sets matching base and extended trace limits. At the extended limit, evaluators and rules that extend retention stop, and UI feedback and annotation queues keep working. In 2025, one developer hit this limit with code-evaluator experiments and could not start new experiments.

  8. Budget the LSU products

    What else bills in LSUs?

    Look forLangSmith Deployment bills by vCPU-hour and GiB-hour. Engine costs about 7 to 45 LSU per run on a 6-hour schedule. Fleet bills past 37 included LSU a month on Plus, Sandboxes past 8 LSU, and the Perceived Error Tuned Evaluator at 0.015 LSU per evaluation run. On Plus, LSUs bill on top of seats. On Enterprise, they draw down committed credits.

Questions to ask vendors

  1. How many traces a month does each production agent produce, and how many runs does a typical trace hold?
  2. Which projects need 180-day traces, and for what purpose?
  3. Which online evaluators and automation rules keep the retention upgrade on?
  4. What monthly spend limit does each workspace get, and who is told when it is close?
  5. Is Engine turned on, and who decided?

Red flags

  • Every project left at extended retention.
  • Online evaluators on all production traffic with the retention upgrade on and no sampling rate.
  • No usage limit on a workspace that runs automated experiments.
  • Comparing LangSmith's per-trace price with another tool's per-span or per-unit price without converting to your own trace shape.

Products in this piece

Sources

Official documentation
5
Public source
3
  1. LangSmith plans and pricingOfficial documentationlangchain.com
  2. LangSmith docs: Usage and billing (retention tiers and rate limits)Official documentationdocs.langchain.com
  3. LangSmith docs: Manage billing and spend limitsOfficial documentationdocs.langchain.com
  4. LangSmith docs: Data purging for complianceOfficial documentationdocs.langchain.com
  5. LangSmith docs: LLM-as-a-judge online evaluatorsOfficial documentationdocs.langchain.com
  6. LangChain Forum: Not able to delete not used Extended Data Retention traces (Jul 29, 2025)Public sourceforum.langchain.com
  7. Hacker News comment on evaluating LangSmith for production evals (Jun 5, 2025)Public sourcenews.ycombinator.com
  8. Tyler Norlund, Portfolio issue #1727: remove the paid-LangSmith wiring after cancelling (Sep 28, 2026)Public sourcegithub.com