diff --git a/src/langsmith/billing.mdx b/src/langsmith/billing.mdx
index 4a35f0ed99..59aa8d022f 100644
--- a/src/langsmith/billing.mdx
+++ b/src/langsmith/billing.mdx
@@ -7,7 +7,7 @@ This page describes how to manage billing for your LangSmith organization:
- [Set up billing for your account](#set-up-billing-for-your-account): Complete the billing setup process for Developer and Plus plans, including special instructions for legacy accounts.
- [Update your information](#update-your-information): Modify invoice email addresses, business information, and tax IDs for your organization.
-- [Optimize your tracing spend](#optimize-your-tracing-spend): Learn how to reduce costs through data retention management and usage limits.
+- [Enforce spend limits](#enforce-spend-limits): Learn how to manage your spend through usage limits and data retention.
## Set up billing for your account
@@ -15,65 +15,39 @@ This page describes how to manage billing for your LangSmith organization:
Before using this guide, note the following:
- If you are interested in the [Enterprise](https://www.langchain.com/pricing) plan, please [contact sales](https://www.langchain.com/contact-sales). This guide is only for our self-serve billing plans.
-- If you created your LangSmith organization before pricing was introduced on April 2nd, 2024, please [skip to the final section](#set-up-billing-for-accounts-created-before-pricing-was-introduced-on-april-2-2024).
-To set up billing for your LangSmith organization, navigate to the [Usage and Billing](https://smith.langchain.com/settings/payments) page under **Settings**. Depending on your organization's settings, there are different setup guides:
+To set up billing for your LangSmith organization, navigate to the [Billing and Usage](https://smith.langchain.com/settings/payments) page under **Settings**. Depending on your organization's settings, there are different setup guides:
- [Developer plan](#developer-plan%3A-set-up-billing-on-your-personal-organization)
- [Plus plan](#plus-plan%3A-set-up-billing-on-a-shared-organization)
-- [Setup for accounts created before April 2, 2024 pricing introduction](#set-up-billing-for-accounts-created-before-pricing-introduction)
### Developer Plan: set up billing on your personal organization
-Personal organizations are limited to 5000 traces per month until a credit card is added. You can add a credit card on the **Plans and Billing** page as follows:
+Personal organizations are limited to 5,000 traces per month until a credit card is added. To add a card:
-1. Click **Set up Billing**.
-1. Add your credit card information. After this step, you will no longer be rate limited to 5000 traces, and you will be charged for any excess traces at rates specified on the [pricing](https://www.langchain.com/pricing-langsmith) page.
+1. Click **Add card to remove trace limit**.
+1. Add your credit card information.
+1. Once complete, you will no longer be rate limited to 5,000 traces, and you will be charged for any excess traces at rates specified on the [pricing](https://www.langchain.com/pricing-langsmith) page.
### Plus Plan: set up billing on a shared organization
-
-If you have not yet created an organization, you need to follow [this guide](/langsmith/set-up-a-workspace#set-up-an-organization) before setting up billing. The following steps assume you are already in a new organization.
+Team organizations are given an initial 10,000 traces per month. Any excess traces will be charged at rates specified on the [pricing](https://www.langchain.com/pricing-langsmith) page.
-You can't use a new organization until you enter credit card information. After you complete the following steps, you will gain complete access to LangSmith.
+New organizations that you manually create are required to be on the Plus Plan. If you see a message about needing to upgrade to Plus to use this organization, follow these steps.
-1. Click **Subscribe** on the **Plus** page.
-
- If you are a startup building with AI, instead click **Apply Now** on the Startup Plan. You may be eligible for discounted prices and a free, monthly trace allotment.
-
-1. Review your existing members. Before subscribing, LangSmith lets you remove any added users that you do **not** want to be included in the bill.
-1. Enter your credit card information. Then, enter business information, invoice email, and tax ID. If this organization belongs to a business, check the **This is a business** checkbox and enter the information accordingly.
-
-For more information, refer to the [Update your information section](#update-your-information).
-
-Once this step is complete, your organization will have access to the rest of LangSmith.
-
-### Set up billing for accounts created before pricing introduction
-
-If you joined LangSmith before pricing was introduced on April 2, 2024, you have the option to upgrade your existing account to set up billing. If you did not set up billing by July 8, 2024, then your account is now rate limited to a maximum of 5,000 traces per month.
-
-1. Navigate to the [Settings](https://smith.langchain.com/settings) page.
-2. Click **Set up Billing**.
-
- 
+1. Click **Upgrade to Plus**.
+1. Invite members to your organization, as desired.
+1. Enter your credit card information. Then, enter business information, invoice email, and tax ID. If this organization belongs to a business, check the **This is a business** checkbox and enter the information accordingly. For more information, refer to the [Update your information section](#update-your-information).
-3. Enter your credit card information. If you are on a Personal organization, this will add you to the Developer plan. If you are on a shared organization, this will add you to the Plus plan. For more information, refer to the guides for the [Developer](#developer-plan%3A-set-up-billing-on-your-personal-organization) or [Plus](#plus-plan%3A-set-up-billing-on-a-shared-organization) plans respectively, starting at step 2.
-4. Claim free credits as a thank you for being an early LangSmith user.
+## Update your information (Paid plans only)
-## Update your information
+To update business information for your LangSmith organization, head to the [Billing and Usage](https://smith.langchain.com/settings/payments) page under **Settings**.
-To update business information for your LangSmith organization, head to the [Usage and Billing](https://smith.langchain.com/settings/payments) page under **Settings** and click on the [Plans and Billing](https://smith.langchain.com/settings/payments?tab=2) tab.
-
-
-Business information, tax ID, and invoice email can only be updated for the Plus and Startup plans. Free and Developer plans cannot update this information.
-
### Invoice email
-
-
To update the email address for invoices, follow these steps:
1. Navigate to the **Plans and Billing** tab.
@@ -89,8 +63,6 @@ You will receive all future invoices to the updated email address.
In certain jurisdictions, LangSmith is required to collect sales tax. If you are a business, providing your tax ID may qualify you for a sales tax exemption.
-
-
To update your organization's business information, follow these steps:
1. Navigate to the **Plans and Billing** tab.
@@ -105,7 +77,7 @@ To update your organization's business information, follow these steps:
This ensures that your business information is up-to-date and accurate for billing and tax purposes.
-## Optimize your tracing spend
+## Enforce spend limits
You may find it helpful to read the following pages, before continuing with this section on optimizing your tracing spend:
@@ -118,74 +90,69 @@ You may find it helpful to read the following pages, before continuing with this
Some of the features mentioned in this guide are not currently available on Enterprise plan due to its custom nature of billing. If you are on the Enterprise plan and have questions about cost optimization, reach out to your sales rep or [support@langchain.dev](mailto:support@langchain.dev).
-You will learn how to optimize existing spend and prevent future overspend in LangSmith, which includes:
-
-1. Reducing existing costs with data retention policies.
-2. Preventing future overspend with usage limits.
-
-This tutorial will use an existing LangSmith organization with high usage. You can transfer the concepts from this example to your own organization. The example organization has three [workspaces](/langsmith/administration-overview#workspaces), one for each deployment stage (`Dev`, `Staging`, and `Prod`):
-
-
### Understand your current usage
The first step of any optimization process is to understand current usage. LangSmith provides two ways to do this: [Usage graph](#usage-graph) and [Invoices](#invoices).
+LangSmith Usage is measured per workspace, because workspaces often represent development environments (as in the example), or teams within an organization.
+
+
#### Usage graph
The usage graph lets you examine how much of each usage-based pricing metric you have consumed. It does not directly show spend (which you will review later in the draft invoice).
-You can navigate to the usage graph under **Settings** -> **Usage and Billing** -> **Usage Graph**.
-
-
+Navigate to the usage graph under **Settings** -> **Billing and Usage** -> **Usage Graph**.
-This graph shows that there are two usage metrics that LangSmith charges for:
+There are two usage metrics that LangSmith charges for:
- LangSmith Traces (Base Charge): tracks all traces that you send to LangSmith.
- LangSmith Traces (Extended Data Retention Upgrades): tracks all traces that also have our Extended 400 Day Data Retention.
-For more details, refer to the [data retention conceptual docs](/langsmith/administration-overview#data-retention). Notice that these graphs look identical, which you will review later in the tutorial.
+For more details, refer to the [data retention conceptual docs](/langsmith/administration-overview#data-retention).
-LangSmith Traces usage is measured per workspace, because workspaces often represent development environments (as in the example), or teams within an organization. As a LangSmith administrator, you may want to understand spend granularly per each of these units. In this case where you just want to cut spend, you can focus on the environment responsible for the majority of costs first for the greatest savings.
#### Invoices
-You understand what usage looks like in terms of traces, but you now need to translate that into spend. To do so, navigate to the **Invoices** tab. The first invoice that will appear on screen is a draft of your current month's invoice, which shows your running spend thus far this month.
-
-
+To understand how your usage translates to spend, navigate to the **Invoices** tab. The first invoice that will appear on screen is a draft of your current month's invoice, which shows your running spend thus far this month.
LangSmith's Usage Graph and Invoice use the term `tenant_id` to refer to a workspace ID. They are interchangeable.
-In the GIF, you'll see that the charges for LangSmith Traces are broken up by "tenant\_id" (i.e., workspace ID), which means you can track tracing spend on each of the workspaces. In the first few days of June, the vast majority of the total spend of roughly $2,000 is in the production workspace. Further, the majority of spend in that workspace was on extended data retention trace upgrades.
+### Set limits on usage
+
+
+
+#### Set spend limit for workspace
-These upgrades occur for two reasons:
+1. To set limits, navigate to **Settings** -> **Billing and Usage** -> **Usage limits**.
+1. Input a spend limit for your selected workspace. LangSmith will determine an appropriate number of base and extended trace limits to match that spend. The trace limits include the free trace allocation that comes with your plan \(see details on [pricing page](https://smith.langchain.com/settings/payments)\).
-1. You use extended data retention tracing, which means by default your traces are retained for 400 days.
-2. You use base data retention tracing and use a feature that automatically extends the data retention of a trace. ([Refer to the Auto-Upgrade conceptual docs](/langsmith/administration-overview#data-retention).)
-Given that the number of total traces per day is equal to the number of extended retention traces per day, it's most likely the case that this organization is using extended data retention tracing everywhere. As a result, start by optimizing the retention settings.
+
+For organizations with **multiple workspaces only**: For simplicity, LangSmith incorporates the free traces into the cost calculation of the **first workspace only**. In actuality, the free traces can be "consumed" by any workspace. Therefore, although workspace-level spend limits are approximate for multi-workspace organizations, the organization-level spend limit is absolute.
+
-### Optimization 1: manage data retention
+#### Configure trace tier distrubution
+LangSmith has two trace tiers: base traces and extended traces. Base traces have the base retention and are short-lived (14 days), while extended traces have extended retention and are long-lived (400 days). For more information, refer to the [data retention conceptual docs](/langsmith/administration-overview#data-retention).
-LangSmith charges differently based on a trace's [data retention](/langsmith/administration-overview#data-retention), where short-lived traces are an order of magnitude less expensive than ones that last for a long time. In this optimization, you'll learn how to get optimal settings for data retention without sacrificing historical observability, and see the effect it has on the bill.
+Set the desired default trace tier by selecting an option below the **Default data retention** label. All traces will have this tier by default when they are registered. Note that because extended traces cost more than base traces, selecting **Extended** as your default data retention option will result in less overall traces allowed in the billing period. By default, updating this setting will only apply to future incoming traces. To apply to all existing traces in the workspace, select the checkbox.
-#### Change org level retention defaults for new projects
+If the default data retention is set to **Base** you can optionally use the slider to distribute trace limits across base and extended tracess. LangSmith automatically provides a suggestion for this distribution but you can tailor this to your needs. For example, if you are running lots of automations or other features that may upgrade a trace to extended, you may want to increase your extended trace limits. To see the complete list of features that may upgrade a trace, [see here](https://docs.langchain.com/langsmith/administration-overview#how-it-works:~:text=Data%20retention%20auto%2Dupgrades).
-Navigate to the **Usage configuration** tab, and look at the organization level retention settings. Modifying this setting affects all **new projects** that are created going forward in all workspaces in the organizaton.
-For backwards compatibility, older organizations may have this defaulted to **Extended**. Organizations created after June 3rd, 2024 have this defaulted to **Base**.
+The extended data retention limit can cause features other than tracing to stop working once reached. If you plan to use this feature, read more about its [functionality and side effects](/langsmith/administration-overview#side-effects-of-extended-data-retention-traces-limit).
-
+### Other methods of managing traces
-#### Change project level retention defaults
+#### Change project-level default retention
-Data retention settings are adjustable per project on the tracing project page.
+Data retention settings are adjustable per tracing project.
-Navigate to **Projects** > ***Your project name*** > Select **Retention** and modify the default retention of the project to **Base**. This will only affect retention (and pricing) for **traces going forward**.
+Navigate to **Projects** > ***Your project name*** > Select **Retention** and select the desired default retention. This will only affect retention (and pricing) for **traces going forward**.
@@ -212,72 +179,8 @@ For example, this is the expected configuration to keep 10% of all traces for ex
If you want to keep a subset of traces for **longer than 400 days** for data collection purposes, you can create another run rule that sends some runs to a dataset of your choosing. A dataset allows you to store the trace inputs and outputs (e.g., as a key-value dataset), and will persist indefinitely, even after the trace gets deleted.
-#### See results after 7 days
-
-While the total amount of traces per day stayed the same, the extended data retention traces was cut heavily. In the invoice, the spend reduced to roughly \$900 in the last 7 days, as opposed to $2,000 in the previous 4. That's a cost reduction of nearly 75% per day.
-
-
-
-### Optimization 2: limit usage
-
-In the previous section, you managed data retention settings to **optimize existing spend**. In this section, you will use usage limits to **prevent future overspend**.
-
-LangSmith has two usage limits: total traces and extended retention traces. These correspond to the two metrics tracked on the [usage graph](#usage-graph). You can use these in tandem to have granular control over spend.
-
-To set limits, navigate back to **Settings** -> **Usage and Billing** -> **Usage configuration**. There is a table at the bottom of the page that lets you set usage limits per workspace. For each workspace, the two limits appear, along with a cost estimate:
-
-
-
-Start by setting limits on production usage, since that is where the majority of spend comes from.
-
-#### Set a good total traces limit
-
-Picking the right total traces limit depends on the expected load of traces that you will send to LangSmith. It is important to consider potential growth before setting a limit. For example:
-
-- **Current Load**: The gen AI application is called between 1.2-1.5 times per second, and each API request has a trace associated with it, meaning it logs around 100,000-130,000 traces per day.
-- **Expected Growth in Load**: The expectation is that this will double in size in the near future.
-
-From these assumptions, you can calculate an approximate limit:
-
-```python
-limit = current_load_per_day * expected_growth * days/month
- = 130,000 * 2 * 30
- = 7,800,000 traces / month
-```
-
-Click on the edit icon on the right side of the table for the **Prod** row to enter the limit.
-
-
-
-
-When set without the extended data retention traces limit, the maximum cost estimator assumes that all traces are using extended data retention.
-
-
-#### Cut maximum spend with an extended data retention limit
-
-From [Optimization 1](#optimization-1-manage-data-retention), you learned that the easiest way to cut cost was through managing data retention. The same is true for limits. If you only want to keep roughly 10% of traces to be around more than 14 days, you can set a limit on the maximum high retention traces you can keep. This would result in `.10 * 7,800,000 = 780,000`.
-
-
-
-The maximum cost is cut from \~40k per month to \~7.5k per month, because you no longer allow as many expensive data retention upgrades. This ensures that new users on the platform will not accidentally cause cost to balloon.
-
-
-The extended data retention limit can cause features other than traces to stop working once reached. If you plan to use this feature, read more about its [functionality and side effects](/langsmith/administration-overview#side-effects-of-extended-data-retention-traces-limit).
-
-
-#### Set dev/staging limits and view total spent limit across workspaces
-
-Following a similar logic for the `dev` and `staging` environments, you can set limits at 10% of the production limit on usage for each workspace.
-
-While this works with this usage pattern, setting good dev and staging limits may vary depending on your use case with LangSmith. For example, if you run evals as part of CI/CD in dev or staging, you may want to be more flexible with your usage limits to avoid test failures.
-
-With the limits set, LangSmith shows a maximum spend estimate across all workspaces:
-
-
-
-You can use the cost estimate to plan for your invoice total.
### Summary
-If you have questions about further optimizing your spend, please reach out to [support@langchain.dev](mailto:support@langchain.dev).
+If you have questions about further managing your spend, please reach out to [support@langchain.dev](mailto:support@langchain.dev).
diff --git a/src/langsmith/images/base-spend-limit-only.png b/src/langsmith/images/base-spend-limit-only.png
new file mode 100644
index 0000000000..8d1fbed340
Binary files /dev/null and b/src/langsmith/images/base-spend-limit-only.png differ
diff --git a/src/langsmith/images/p1orgretention-v2.png b/src/langsmith/images/p1orgretention-v2.png
index f8ba585230..a9ccee0c16 100644
Binary files a/src/langsmith/images/p1orgretention-v2.png and b/src/langsmith/images/p1orgretention-v2.png differ
diff --git a/src/langsmith/images/p2bothlimits-v2.png b/src/langsmith/images/p2bothlimits-v2.png
index 88561297e2..9bd60ecf8e 100644
Binary files a/src/langsmith/images/p2bothlimits-v2.png and b/src/langsmith/images/p2bothlimits-v2.png differ
diff --git a/src/langsmith/images/p2totalspendlimits-v2.png b/src/langsmith/images/p2totalspendlimits-v2.png
index 9d3b83b035..2021efbda7 100644
Binary files a/src/langsmith/images/p2totalspendlimits-v2.png and b/src/langsmith/images/p2totalspendlimits-v2.png differ
diff --git a/src/langsmith/images/p2usagelimitsempty-v2.png b/src/langsmith/images/p2usagelimitsempty-v2.png
index b30f0fda8e..a58d8a803e 100644
Binary files a/src/langsmith/images/p2usagelimitsempty-v2.png and b/src/langsmith/images/p2usagelimitsempty-v2.png differ
diff --git a/src/langsmith/images/update-business-info.png b/src/langsmith/images/update-business-info.png
deleted file mode 100644
index fe547adad7..0000000000
Binary files a/src/langsmith/images/update-business-info.png and /dev/null differ
diff --git a/src/langsmith/images/update-invoice-email.png b/src/langsmith/images/update-invoice-email.png
deleted file mode 100644
index e850b55df6..0000000000
Binary files a/src/langsmith/images/update-invoice-email.png and /dev/null differ