fix: change cloud SaaS to cloud (#111)

samecrowder · web-flow · commit 1fdbdca9122f · 2025-08-04T17:42:29.000-07:00
diff --git a/src/langgraph-platform/api-ref-control-plane.mdx b/src/langgraph-platform/api-ref-control-plane.mdx
@@ -8,7 +8,7 @@ Click <a href="https://api.host.langchain.com/docs" target="_blank">here</a> to
 
 ## Host
 
-LangGraph Control Plane hosts for Cloud SaaS data regions:
+LangGraph Control Plane hosts for Cloud data regions:
 
 | US | EU |
 |----|----|
diff --git a/src/langgraph-platform/cloud.mdx b/src/langgraph-platform/cloud.mdx
@@ -1,16 +1,16 @@
 ---
-title: Cloud SaaS
+title: Cloud
 ---
 
-To deploy a [LangGraph Server](/langgraph-platform/langgraph-server), follow the how-to guide for [how to deploy to Cloud SaaS](/langgraph-platform/deploy-to-cloud).
+To deploy a [LangGraph Server](/langgraph-platform/langgraph-server), follow the how-to guide for [how to deploy to Cloud](/langgraph-platform/deploy-to-cloud).
 
 ## Overview
 
-The Cloud SaaS deployment option is a fully managed model for deployment where we manage the [control plane](/langgraph-platform/control-plane) and [data plane](/langgraph-platform/data-plane) in our cloud.
+The Cloud deployment option is a fully managed model for deployment where we manage the [control plane](/langgraph-platform/control-plane) and [data plane](/langgraph-platform/data-plane) in our cloud.
 
 |                   | [Control plane](/langgraph-platform/control-plane) | [Data plane](/langgraph-platform/data-plane) |
 |-------------------|---------------------------------------------------|-----------------------------------------------|
 | **Managed by**    | LangChain                                         | LangChain                                     |
 | **Infrastructure**| LangChain's cloud                                 | LangChain's cloud                             |
 
-![Cloud SaaS](/langgraph-platform/images/langgraph-cloud-architecture.png)
+![Cloud](/langgraph-platform/images/langgraph-cloud-architecture.png)
diff --git a/src/langgraph-platform/control-plane.mdx b/src/langgraph-platform/control-plane.mdx
@@ -56,7 +56,7 @@ CPU and memory resources are per replica.
 
 <Info>
   **Self-Hosted Deployment**
-  Resources for [Hybrid](/langgraph-platform/hybrid) and [Self-Hosted](/langgraph-platform/self-hosted) deployments can be fully customized. Deployment types are only applicable for [Cloud SaaS](/langgraph-platform/cloud) deployments.
+  Resources for [Hybrid](/langgraph-platform/hybrid) and [Self-Hosted](/langgraph-platform/self-hosted) deployments can be fully customized. Deployment types are only applicable for [Cloud](/langgraph-platform/cloud) deployments.
 </Info>
 
 #### Production
diff --git a/src/langgraph-platform/data-plane.mdx b/src/langgraph-platform/data-plane.mdx
@@ -51,8 +51,8 @@ This section describes various features of the data plane.
 ### Data Region
 
 <Info>
-  **Only for Cloud SaaS**
-  Data regions are only applicable for [Cloud SaaS](/langgraph-platform/cloud) deployments.
+  **Only for Cloud**
+  Data regions are only applicable for [Cloud](/langgraph-platform/cloud) deployments.
 </Info>
 
 Deployments can be created in 2 data regions: US and EU
@@ -78,8 +78,8 @@ Scale down actions are delayed for 30 minutes before any action is taken. In oth
 ### Static IP Addresses
 
 <Info>
-  **Only for Cloud SaaS**
-  Static IP addresses are only available for [Cloud SaaS](/langgraph-platform/cloud) deployments.
+  **Only for Cloud**
+  Static IP addresses are only available for [Cloud](/langgraph-platform/cloud) deployments.
 </Info>
 
 All traffic from deployments created after January 6th 2025 will come through a NAT gateway. This NAT gateway will have several static IP addresses depending on the data region. Refer to the table below for the list of static IP addresses:
@@ -119,22 +119,22 @@ Multiple deployments can share the same Redis instance. For example, for `Deploy
 
 LangGraph Server is automatically configured to send traces to LangSmith. See the table below for details with respect to each deployment option.
 
-| Cloud SaaS | Hybrid | Self-Hosted |
+| Cloud | Hybrid | Self-Hosted |
 |------------|------------------------|----------------------|
 | Required<br />Trace to LangSmith SaaS. | Optional<br />Disable tracing or trace to LangSmith SaaS. | Optional<br />Disable tracing, trace to LangSmith SaaS, or trace to Self-Hosted LangSmith. |
 
 ### Telemetry
 
 LangGraph Server is automatically configured to report telemetry metadata for billing purposes. See the table below for details with respect to each deployment option.
 
-| Cloud SaaS | Hybrid | Self-Hosted |
+| Cloud | Hybrid | Self-Hosted |
 |------------|------------------------|----------------------|
 | Telemetry sent to LangSmith SaaS. | Telemetry sent to LangSmith SaaS. | Self-reported usage (audit) for air-gapped license key.<br />Telemetry sent to LangSmith SaaS for LangGraph Platform License Key. |
 
 ### Licensing
 
 LangGraph Server is automatically configured to perform license key validation. See the table below for details with respect to each deployment option.
 
-| Cloud SaaS | Hybrid | Self-Hosted |
+| Cloud | Hybrid | Self-Hosted |
 |------------|------------------------|----------------------|
 | LangSmith API Key validated against LangSmith SaaS. | LangSmith API Key validated against LangSmith SaaS. | Air-gapped license key or LangGraph Platform License Key validated against LangSmith SaaS. |
diff --git a/src/langgraph-platform/deploy-to-cloud.mdx b/src/langgraph-platform/deploy-to-cloud.mdx
@@ -1,8 +1,8 @@
 ---
-title: How to deploy to cloud SaaS
-sidebarTitle: Deploy to cloud SaaS
+title: How to deploy to cloud
+sidebarTitle: Deploy to cloud
 ---
-Before deploying, review the [conceptual guide for the Cloud SaaS](/langgraph-platform/cloud) deployment option.
+Before deploying, review the [conceptual guide for the Cloud](/langgraph-platform/cloud) deployment option.
 
 ## Prerequisites
 
diff --git a/src/langgraph-platform/deployment-options.mdx b/src/langgraph-platform/deployment-options.mdx
@@ -9,30 +9,30 @@ You can [run LangGraph Platform locally for free](/langgraph-platform/local-serv
 
 There are 3 main options for deploying with [LangGraph Platform](/langgraph-platform/index):
 
-1. [Cloud SaaS](#cloud-saas)
+1. [Cloud](#cloud)
 2. [Hybrid](#hybrid)
 3. [Self-Hosted](#self-hosted)
 
 A quick comparison:
 
-|                      | **Cloud SaaS** | **Hybrid** | **Self-Hosted** |
+|                      | **Cloud** | **Hybrid** | **Self-Hosted** |
 |----------------------|----------------|-------------|-----------------|
 | **Description** | All components run in LangChain's cloud | Control plane runs in LangChain's cloud; data plane in your cloud | All components run in your cloud |
 | **CI/CD** | Managed internally by platform | Managed externally by you | Managed externally by you |
 | **Data/compute residency** | LangChain's cloud | Your cloud | Your cloud |
 | **LangSmith compatibility** | Trace to LangSmith SaaS | Trace to LangSmith SaaS | Trace to Self-Hosted LangSmith |
 | **[Pricing](https://www.langchain.com/pricing-langgraph-platform)** | Plus | Enterprise | Enterprise |
 
-## Cloud SaaS
+## Cloud
 
-The [Cloud SaaS](/langgraph-platform/cloud) deployment option is a fully managed model for deployment where the [control plane](/langgraph-platform/control-plane) and [data plane](/langgraph-platform/data-plane) run in our cloud. This option provides a simple way to deploy and manage your LangGraph Servers.
+The [Cloud](/langgraph-platform/cloud) deployment option is a fully managed model for deployment where the [control plane](/langgraph-platform/control-plane) and [data plane](/langgraph-platform/data-plane) run in our cloud. This option provides a simple way to deploy and manage your LangGraph Servers.
 
 Connect your GitHub repositories to the platform and deploy your LangGraph Servers from the [control plane UI](/langgraph-platform/control-plane#control-plane-ui). The build process (i.e. CI/CD) is managed internally by the platform.
 
 For more information, please see:
 
-* [Cloud SaaS Conceptual Guide](/langgraph-platform/cloud)
-* [How to deploy to Cloud SaaS](/langgraph-platform/deploy-to-cloud)
+* [Cloud Conceptual Guide](/langgraph-platform/cloud)
+* [How to deploy to Cloud](/langgraph-platform/deploy-to-cloud)
 
 ## Hybrid
 
diff --git a/src/langgraph-platform/egress-metrics-metadata.mdx b/src/langgraph-platform/egress-metrics-metadata.mdx
@@ -3,7 +3,7 @@ title: Egress for subscription metrics and operational metadata
 sidebarTitle: Egress for metrics and metadata
 ---
 
-<Note> **Important: self-hosted only.** This section only applies to customers who are not running in offline mode and assumes you are using a [self-hosted LangGraph Platform instance](/langgraph-platform/deployment-options). This does not apply to cloud SaaS or hybrid deployments.</Note>
+<Note> **Important: self-hosted only.** This section only applies to customers who are not running in offline mode and assumes you are using a [self-hosted LangGraph Platform instance](/langgraph-platform/deployment-options). This does not apply to cloud or hybrid deployments.</Note>
 
 Self-hosted LangGraph Platform instances store all information locally and will never send sensitive information outside of your network. We currently only track platform usage for billing purposes according to the entitlements in your order. To better support our customers remotely, we do require egress to `https://beacon.langchain.com`.
 
diff --git a/src/langgraph-platform/env-var.mdx b/src/langgraph-platform/env-var.mdx
@@ -18,7 +18,7 @@ Specifies, in seconds, how long the server will wait for background jobs to fini
 
 ## `BG_JOB_TIMEOUT_SECS`
 
-The timeout of a background run can be increased. However, the infrastructure for a Cloud SaaS deployment enforces a 1 hour timeout limit for API requests. This means the connection between client and server will timeout after 1 hour. This is not configurable.
+The timeout of a background run can be increased. However, the infrastructure for a Cloud deployment enforces a 1 hour timeout limit for API requests. This means the connection between client and server will timeout after 1 hour. This is not configurable.
 
 A background run can execute for longer than 1 hour, but a client must reconnect to the server (e.g. join stream via `POST /threads/{thread_id}/runs/{run_id}/stream`) to retrieve output from the run if the run is taking longer than 1 hour.
 
diff --git a/src/langgraph-platform/faq.mdx b/src/langgraph-platform/faq.mdx
@@ -33,7 +33,7 @@ LangGraph is a stateful, orchestration framework that brings added control to ag
 | Streaming           | Basic                                                     | Dedicated mode for token-by-token messages                                                             |
 | Checkpointer        | Community contributed                                     | Supported out-of-the-box                                                                               |
 | Persistence Layer   | Self-managed                                              | Managed Postgres with efficient storage                                                                |
-| Deployment          | Self-managed                                              | • Cloud SaaS <br /> • Free self-hosted <br /> • Enterprise (paid self-hosted)                      |
+| Deployment          | Self-managed                                              | • Cloud <br /> • Free self-hosted <br /> • Enterprise (paid self-hosted)                      |
 | Scalability         | Self-managed                                              | Auto-scaling of task queues and servers                                                                |
 | Fault-tolerance     | Self-managed                                              | Automated retries                                                                                      |
 | Concurrency Control | Simple threading                                          | Supports double-texting                                                                                |
@@ -45,7 +45,7 @@ LangGraph is a stateful, orchestration framework that brings added control to ag
 
 No. LangGraph Platform is proprietary software.
 
-There is a free, self-hosted version of LangGraph Platform with access to basic features. The Cloud SaaS deployment option and the Self-Hosted deployment options are paid services. [Contact our sales team](https://www.langchain.com/contact-sales) to learn more.
+There is a free, self-hosted version of LangGraph Platform with access to basic features. The Cloud deployment option and the Self-Hosted deployment options are paid services. [Contact our sales team](https://www.langchain.com/contact-sales) to learn more.
 
 For more information, see our [LangGraph Platform pricing page](https://www.langchain.com/pricing-langgraph-platform).
 
diff --git a/src/langgraph-platform/index.mdx b/src/langgraph-platform/index.mdx
@@ -23,4 +23,4 @@ LangGraph Platform makes it easy to get your agent running in production —  wh
 * **[Checkpointers and memory management](https://langchain-ai.github.io/langgraph/concepts/persistence/#checkpoints)**: For agents needing persistence (e.g., conversation memory), deploying a robust storage solution can be complex. LangGraph Platform includes optimized [checkpointers](https://langchain-ai.github.io/langgraph/concepts/persistence/#checkpoints) and a [memory store](https://langchain-ai.github.io/langgraph/concepts/persistence/#memory-store), managing state across sessions without the need for custom solutions.
 * **[Human-in-the-loop support](/langgraph-platform/add-human-in-the-loop)**: In many applications, users require a way to intervene in agent processes. LangGraph Server provides specialized endpoints for human-in-the-loop scenarios, simplifying the integration of manual oversight into agent workflows.
 * **[LangGraph Studio](/langgraph-platform/langgraph-studio)**: Enables visualization, interaction, and debugging of agentic systems that implement the LangGraph Server API protocol. Studio also integrates with LangSmith to enable tracing, evaluation, and prompt engineering.
-* **[Deployment](/langgraph-platform/deployment-options)**: There are three ways to deploy on LangGraph Platform: [Cloud SaaS](/langgraph-platform/cloud), [Hybrid](/langgraph-platform/hybrid), and [Self-Hosted](/langgraph-platform/self-hosted).
+* **[Deployment](/langgraph-platform/deployment-options)**: There are three ways to deploy on LangGraph Platform: [Cloud](/langgraph-platform/cloud), [Hybrid](/langgraph-platform/hybrid), and [Self-Hosted](/langgraph-platform/self-hosted).
diff --git a/src/langgraph-platform/langgraph-server.mdx b/src/langgraph-platform/langgraph-server.mdx
@@ -15,7 +15,7 @@ To use the `Enterprise` version of the LangGraph Server, you must acquire a lice
 
 You can run the `Enterprise` version of the LangGraph Server on the following deployment options:
 
-- Cloud SaaS
+- Cloud
 - Hybrid
 - Self-hosted
 
diff --git a/src/langgraph-platform/plans.mdx b/src/langgraph-platform/plans.mdx
@@ -6,14 +6,14 @@ mode: "wide"
 
 LangGraph Platform is a solution for deploying agentic applications in production:
 
-* **Plus**: All [LangSmith](https://smith.langchain.com/) users with a [Plus account](https://docs.smith.langchain.com/administration/pricing) have access to this plan. You can sign up for this plan simply by upgrading your LangSmith account to the Plus plan type. This gives you access to the [Cloud](/langgraph-platform/deployment-options#cloud-saas) deployment option.
+* **Plus**: All [LangSmith](https://smith.langchain.com/) users with a [Plus account](https://docs.smith.langchain.com/administration/pricing) have access to this plan. You can sign up for this plan simply by upgrading your LangSmith account to the Plus plan type. This gives you access to the [Cloud](/langgraph-platform/deployment-options#cloud) deployment option.
 * **Enterprise**: This is separate from LangSmith plans. You can sign up for this plan by contacting sales@langchain.dev. This gives you access to all [deployment options](/langgraph-platform/deployment-options).
 
 ## Plan Details
 
 |                                                                  | Plus                                                  | Enterprise                                          |
 |------------------------------------------------------------------|-------------------------------------------------------|-----------------------------------------------------|
-| Deployment Options                                               | Cloud SaaS                                         | <ul><li>Cloud SaaS</li><li>Hybrid</li><li>Self-Hosted</li></ul> |
+| Deployment Options                                               | Cloud                                         | <ul><li>Cloud</li><li>Hybrid</li><li>Self-Hosted</li></ul> |
 | Usage                                                            | See [Pricing](https://www.langchain.com/langgraph-platform-pricing) | Custom                                              |
 | APIs for retrieving and updating state and conversational history | ✅                                                     | ✅                                                   |
 | APIs for retrieving and updating long-term memory                | ✅                                                     | ✅                                                   |
diff --git a/src/langgraph-platform/scalability-and-resilience.mdx b/src/langgraph-platform/scalability-and-resilience.mdx
@@ -27,7 +27,7 @@ If a hard shutdown occurs due to a server crash or an infrastructure failure, an
 
 ## Postgres resilience
 
-For deployment modalities where we manage the Postgres database, we have periodic backups and continuously replicated standby replicas for automatic failover. This Postgres configuration is available in the [Cloud SaaS deployment option](/langgraph-platform/cloud) for [`Production` deployment types](/langgraph-platform/control-plane#deployment-types) only.
+For deployment modalities where we manage the Postgres database, we have periodic backups and continuously replicated standby replicas for automatic failover. This Postgres configuration is available in the [Cloud deployment option](/langgraph-platform/cloud) for [`Production` deployment types](/langgraph-platform/control-plane#deployment-types) only.
 
 All communication with Postgres implements retries for retry-able errors. If Postgres is momentarily unavailable, such as during a database restart, most/all traffic should continue to succeed. Prolonged failure of Postgres will render the LangGraph Server unavailable.
 
