Plans for teams of any size

Our Developer plan is a great choice for personal projects. You will have 1 free seat with access to LangSmith (5k base traces/month included).  

‍

The Plus plan is for teams that want to self-serve with moderate usage and collaboration needs. You can purchase up to 10 seats with access to LangSmith (10k base traces/month included). You will be able to ship agents with our managed LangSmith Deployment service, with 1 free dev-sized deployment included. 

‍

The Enterprise plan is for teams that need more advanced administration, security, support, or deployment options. Contact our sales team to learn more.

Yes! We offer a Startup Plan for LangSmith, designed for early-stage companies building agentic applications. You’ll get discounted rates and generous free trace allotments to build with confidence from day one.

‍

‍Apply here to get started with startup pricing. Customers can stay on the Startup Plan for 1 year before graduating to the Plus Plan.

For the Developer or Plus Plan, seats are billed monthly on the 1st or pro-rated if added mid-month (no credit for removed seats); traces are billed monthly in arrears for your usage. Enterprise plans are invoiced annually upfront.

We will not train on your data, and you own all rights to your data. See our Terms of Service for more information.

A trace represents a single execution of your application—whether it’s an agent, evaluator, or playground session. It can include many individual steps, such as LLM calls and other tracked events. Here's an example of a single trace.

Base traces have a shorter retention period of 14 days and cost $0.50 per 1k traces. Extended traces have a longer retention period of 400 days and cost $5.00 per 1k traces. You can "upgrade" base traces to extended traces at $4.50 per 1k traces.

Base traces are short-lived (14-day retention) and ideal for quick debugging or ad-hoc analysis. They’re priced for volume and short-term utility.

‍

Extended traces, on the other hand, are retained for 400 days and often include valuable feedback—whether from users, evaluators, or human labelers. This feedback makes them essential for ongoing improvement and model tuning (higher utility), which comes with a higher price point.

‍

LangSmith lets you choose the right retention for each trace, helping you balance cost and value.

Base traces are short-lived (14-day retention) and ideal for quick debugging or ad-hoc analysis. They’re priced for volume and short-term utility.

‍

Extended traces, on the other hand, are retained for 400 days and often include valuable feedback—whether from users, evaluators, or human labelers. This feedback makes them essential for ongoing improvement and model tuning (higher utility), which comes with a higher price point.

‍

LangSmith lets you choose the right retention for each trace, helping you balance cost and value.

Plus plans include 1 free dev-sized deployment. If you spin up additional dev-sized or production-sized deployments, you’ll be charged by usage (agent runs and uptime).

If you’re on the Plus plan, you get 1 free dev-sized agent deployment – all usage in this deployment will be free no matter how many agent runs you execute.

An agent run is one end-to-end invocation of a LangGraph agent deployed via LangSmith Deployment. Nodes and subgraphs within a single agent execution are not charged separately. Calls to other LangGraph agents (through RemoteGraph or the LangGraph SDK or the API directly) are charged separately, to the deployment that hosts the agent being called. An interrupt for human-in-the-loop creates a separate agent run when resuming.

Uptime is the duration your deployment’s database is live and persisting state. Uptime will be tracked as soon as your deployment is live and ends when you shut it down. Dev agent deployments are typically short-lived (used during iteration, then deleted) – whereas Production agent deployments stay live and are updated via revisions (rather than being deleted). 

We recommend using the production-sized deployment for any customer-facing agent. Dev-sized agent deployments are intended for testing and do not support horizontal scaling, backups, or performance optimizations needed in production.

An Agent Builder run is a single execution (a complete invocation) of an agent. Runs occur when you create, test, or run an agent. An Agent Builder run includes any message delivered to the agent through configured triggers (including third-party integrations or other connected services) as well as messages sent directly through the Agent Builder user interface (e.g., via the chat interface). An interrupt for human-in-the-loop creates a separate Agent Builder run when resuming. An execution failure does not count as an Agent Builder run.

No. Model usage is billed separately by your model provider. Agent Builder lets you choose the model you want (for example, Anthropic, OpenAI, Gemini, or another provider) and connect it using your provider API key. More information on configuring models in our docs.

Agent Builder includes built-in tools and supports connecting third-party tools via a remote MCP server. Third-party tools typically require you to authenticate with your account, and any fees or usage charges are billed by the third-party provider. More information on setting up tool keys in our docs.

Yes. Every Agent Builder run is automatically traced in LangSmith. These traces are attributed to the user’s account and count toward usage-based billing under the customer’s LangSmith plan.

Self-hosting for Agent Builder is currently available in Beta. Contact our sales team to learn more.