You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Combine self-hosted control plane and standalone container into single deployment option (#100)
....for simpler content and product packaging :)
We technically will still have four deployment options, but we will
display two of them as sub options within the broader `Self-Hosted`
option, which I think is a lot more clear
Copy file name to clipboardExpand all lines: src/langgraph-platform/control-plane.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ CPU and memory resources are per replica.
56
56
57
57
<Info>
58
58
**Self-Hosted Deployment**
59
-
Resources for [Self-Hosted Data Plane](/langgraph-platform/self-hosted-data-plane) and [Self-Hosted Control Plane](/langgraph-platform/self-hosted-control-plane) deployments can be fully customized. Deployment types are only applicable for [Cloud SaaS](/langgraph-platform/cloud) deployments.
59
+
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.
60
60
</Info>
61
61
62
62
#### Production
@@ -95,7 +95,7 @@ There is no direct access to the database. All access to the database occurs thr
95
95
The database is never deleted until the deployment itself is deleted.
96
96
97
97
<Info>
98
-
A custom Postgres instance can be configured for [Self-Hosted Data Plane](/langgraph-platform/self-hosted-data-plane) and [Self-Hosted Control Plane](/langgraph-platform/self-hosted-control-plane) deployments.
98
+
A custom Postgres instance can be configured for [Hybrid](/langgraph-platform/hybrid) and [Self-Hosted](/langgraph-platform/self-hosted) deployments.
Copy file name to clipboardExpand all lines: src/langgraph-platform/data-plane.mdx
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ All traffic from deployments created after January 6th 2025 will come through a
98
98
### Custom Postgres
99
99
100
100
<Info>
101
-
Custom Postgres instances are only available for [Self-Hosted Data Plane](/langgraph-platform/self-hosted-data-plane) and [Self-Hosted Control Plane](/langgraph-platform/self-hosted-control-plane) deployments.
101
+
Custom Postgres instances are only available for [Hybrid](/langgraph-platform/hybrid) and [Self-Hosted](/langgraph-platform/self-hosted) deployments.
102
102
</Info>
103
103
104
104
A custom Postgres instance can be used instead of the [one automatically created by the control plane](/langgraph-platform/control-plane#database-provisioning). Specify the [`POSTGRES_URI_CUSTOM`](/langgraph-platform/env-var#postgres_uri_custom) environment variable to use a custom Postgres instance.
@@ -108,7 +108,7 @@ Multiple deployments can share the same Postgres instance. For example, for `Dep
108
108
### Custom Redis
109
109
110
110
<Info>
111
-
Custom Redis instances are only available for [Self-Hosted Data Plane](/langgraph-platform/self-hosted-data-plane) and [Self-Hosted Control Plane](/langgraph-platform/self-hosted-control-plane) deployments.
111
+
Custom Redis instances are only available for [Hybrid](/langgraph-platform/hybrid) and [Self-Hosted](/langgraph-platform/self-hosted) deployments.
112
112
</Info>
113
113
114
114
A custom Redis instance can be used instead of the one automatically created by the control plane. Specify the [REDIS_URI_CUSTOM](/langgraph-platform/env-var#redis_uri_custom) environment variable to use a custom Redis instance.
@@ -119,22 +119,22 @@ Multiple deployments can share the same Redis instance. For example, for `Deploy
119
119
120
120
LangGraph Server is automatically configured to send traces to LangSmith. See the table below for details with respect to each deployment option.
121
121
122
-
| Cloud SaaS |Self-Hosted Data Plane | Self-Hosted Control Plane | Standalone Container|
| Required<br />Trace to LangSmith SaaS. | Optional<br />Disable tracing or trace to LangSmith SaaS. | Optional<br />Disable tracing or trace to Self-Hosted LangSmith. | Optional<br />Disable tracing, trace to LangSmith SaaS, or trace to Self-Hosted LangSmith. |
| 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. |
125
125
126
126
### Telemetry
127
127
128
128
LangGraph Server is automatically configured to report telemetry metadata for billing purposes. See the table below for details with respect to each deployment option.
129
129
130
-
| Cloud SaaS |Self-Hosted Data Plane | Self-Hosted Control Plane | Standalone Container|
| 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. | Self-reported usage (audit) for air-gapped license key.<br />Telemetry sent to LangSmith SaaS for LangGraph Platform License Key. |
| 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. |
133
133
134
134
### Licensing
135
135
136
136
LangGraph Server is automatically configured to perform license key validation. See the table below for details with respect to each deployment option.
137
137
138
-
| Cloud SaaS |Self-Hosted Data Plane | Self-Hosted Control Plane | Standalone Container|
| 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. |
Copy file name to clipboardExpand all lines: src/langgraph-platform/data-storage-and-privacy.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,9 @@ When running the LangGraph server (either in-memory or in Docker), LangSmith tra
27
27
`langgraph dev` runs an [in-memory development server](/langgraph-platform/local-server) as a single Python process, designed for quick development and testing. It saves all checkpointing and memory data to disk within a `.langgraph_api` directory in the current working directory. Apart from the telemetry data described in the [CLI](#cli) section, no data leaves the machine unless you have enabled tracing or your graph code explicitly contacts an external service.
28
28
29
29
<aid="langgraph-up"></a>
30
-
### Standalone Container
30
+
### Data Plane Only
31
31
32
-
`langgraph up` builds your local package into a Docker image and runs the server as a [standalone container](/langgraph-platform/deployment-options#standalone-container) consisting of three containers: the API server, a PostgreSQL container, and a Redis container. All persistent data (checkpoints, assistants, etc.) are stored in the PostgreSQL database. Redis is used as a pubsub connection for real-time streaming of events. You can encrypt all checkpoints before saving to the database by setting a valid `LANGGRAPH_AES_KEY` environment variable. You can also specify [TTLs](/langgraph-platform/configure-ttl) for checkpoints and cross-thread memories in `langgraph.json` to control how long data is stored. All persisted threads, memories, and other data can be deleted via the relevant API endpoints.
32
+
`langgraph up` builds your local package into a Docker image and runs the server as the [data plane](/langgraph-platform/deployment-options#self-hosted) consisting of three containers: the API server, a PostgreSQL container, and a Redis container. All persistent data (checkpoints, assistants, etc.) are stored in the PostgreSQL database. Redis is used as a pubsub connection for real-time streaming of events. You can encrypt all checkpoints before saving to the database by setting a valid `LANGGRAPH_AES_KEY` environment variable. You can also specify [TTLs](/langgraph-platform/configure-ttl) for checkpoints and cross-thread memories in `langgraph.json` to control how long data is stored. All persisted threads, memories, and other data can be deleted via the relevant API endpoints.
33
33
34
34
Additional API calls are made to confirm that the server has a valid license and to track the number of executed runs and tasks. Periodically, the API server validates the provided license key (or API key).
Copy file name to clipboardExpand all lines: src/langgraph-platform/deploy-data-plane-only.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
---
2
-
title: How to deploy a standalone container
3
-
sidebarTitle: Deploy a standalone container
2
+
title: How to deploy self-hosted data plane only
3
+
sidebarTitle: Deploy self-hosted data plane only
4
4
---
5
-
Before deploying, review the [conceptual guide for the Standalone Container](/langgraph-platform/standalone-container) deployment option.
5
+
Before deploying, review the [conceptual guide for the Data Plane Only](/langgraph-platform/self-hosted#data-plane-only) deployment option.
6
6
7
7
## Prerequisites
8
8
9
9
1. Use the [LangGraph CLI](/langgraph-platform/langgraph-cli) to [test your application locally](/langgraph-platform/local-server).
10
10
2. Use the [LangGraph CLI](/langgraph-platform/langgraph-cli) to build a Docker image (i.e. `langgraph build`).
11
-
3. The following environment variables are needed for a standalone container deployment.
11
+
3. The following environment variables are needed for a data plane deployment.
12
12
1.`REDIS_URI`: Connection details to a Redis instance. Redis will be used as a pub-sub broker to enable streaming real time output from background runs. The value of `REDIS_URI` must be a valid [Redis connection URI](https://redis-py.readthedocs.io/en/stable/connections.html#redis.Redis.from_url).
0 commit comments