### Summary This is a large refactor of the content for the LangGraph Platform deployment options. Although there are a lot of changes, I do feel fairly confident that this is safe to merge and won't have any negative impact related to confusion around deployment options. However, please review thoroughly (i.e. run the docs locally). ### Goals and Non-Goals Just wanted to explicitly state goals and non-goals so that we're clear about what needs to be done now versus what can be done in a smaller follow-up PR. Goals 1. Add new content for the new deployment options (Self-Hosted Data Plane, Self-Hosted Control Plane). 1. Hide old content for deprecated deployment options (BYOC). 1. Create a pair of "conceptual" and "how-to" pages for each deployment option. As much as possible, the pages should have consistent headings. 1. Introduce the terms "control plane" and "data plane" and define them plainly without hiding/abstracting information. Non-Goals 1. Do not change the navigation of the existing deployment options. As much as possible, update content in-place or add new pages. Changing the navigation is a bigger task that can be done later. 1. Do not remove old content for deprecated deployment options. We may need to refer to this later. There are only ~2 pages (I think). ### Next Steps 1. Update the architecture diagrams for each deployment option. Commit Excalidraw file to source control. 1. Create a "how-to" page for the Control Plane UI. This page pertains to 3/4 deployment options. Most of the content lives in the "how-to" page for Cloud SaaS deployment. 1. Document required RBAC permissions for K8s for Self-Hosted Data Plane and Self-Hosted Control Plane (and update links). 1. Figure out how to consolidate plan information. 1. Figure out where to document licensing, telemetry, custom Postgres/Redis. 1. Update autoscaling content.
5.2 KiB
How to Deploy a Standalone Container
Before deploying, review the conceptual guide for the Standalone Container deployment option.
Prerequisites
- Use the LangGraph CLI to test your application locally.
- Use the LangGraph CLI to build a Docker image (i.e.
langgraph build). - The following environment variables are needed for a standalone container deployment.
-
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 ofREDIS_URImust be a valid Redis connection URI.!!! Note "Shared Redis Instance" Multiple self-hosted deployments can share the same Redis instance. For example, for
Deployment A,REDIS_URIcan be set toredis://<hostname_1>:<port>/1and forDeployment B,REDIS_URIcan be set toredis://<hostname_1>:<port>/2.`1` and `2` are different database numbers within the same instance, but `<hostname_1>` is shared. **The same database number cannot be used for separate deployments**. -
DATABASE_URI: Postgres connection details. Postgres will be used to store assistants, threads, runs, persist thread state and long term memory, and to manage the state of the background task queue with 'exactly once' semantics. The value ofDATABASE_URImust be a valid Postgres connection URI.!!! Note "Shared Postgres Instance" Multiple self-hosted deployments can share the same Postgres instance. For example, for
Deployment A,DATABASE_URIcan be set topostgres://<user>:<password>@/<database_name_1>?host=<hostname_1>and forDeployment B,DATABASE_URIcan be set topostgres://<user>:<password>@/<database_name_2>?host=<hostname_1>.`<database_name_1>` and `database_name_2` are different databases within the same instance, but `<hostname_1>` is shared. **The same database cannot be used for separate deployments**. -
LANGSMITH_API_KEY: (if using Lite) LangSmith API key. This will be used to authenticate ONCE at server start up. -
LANGGRAPH_CLOUD_LICENSE_KEY: (if using Enterprise) LangGraph Platform license key. This will be used to authenticate ONCE at server start up. -
LANGSMITH_ENDPOINT: To send traces to a self-hosted LangSmith instance, setLANGSMITH_ENDPOINTto the hostname of the self-hosted LangSmith instance.
-
Kubernetes (Helm)
Use this Helm chart to deploy a LangGraph Server to a Kubernetes cluster.
Docker
Run the following docker command:
docker run \
--env-file .env \
-p 8123:8000 \
-e REDIS_URI="foo" \
-e DATABASE_URI="bar" \
-e LANGSMITH_API_KEY="baz" \
my-image
!!! note
* You need to replace `my-image` with the name of the image you built in the prerequisite steps (from `langgraph build`)
and you should provide appropriate values for `REDIS_URI`, `DATABASE_URI`, and `LANGSMITH_API_KEY`.
* If your application requires additional environment variables, you can pass them in a similar way.
Docker Compose
Docker Compose YAML file:
volumes:
langgraph-data:
driver: local
services:
langgraph-redis:
image: redis:6
healthcheck:
test: redis-cli ping
interval: 5s
timeout: 1s
retries: 5
langgraph-postgres:
image: postgres:16
ports:
- "5433:5432"
environment:
POSTGRES_DB: postgres
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
volumes:
- langgraph-data:/var/lib/postgresql/data
healthcheck:
test: pg_isready -U postgres
start_period: 10s
timeout: 1s
retries: 5
interval: 5s
langgraph-api:
image: ${IMAGE_NAME}
ports:
- "8123:8000"
depends_on:
langgraph-redis:
condition: service_healthy
langgraph-postgres:
condition: service_healthy
env_file:
- .env
environment:
REDIS_URI: redis://langgraph-redis:6379
LANGSMITH_API_KEY: ${LANGSMITH_API_KEY}
POSTGRES_URI: postgres://postgres:postgres@langgraph-postgres:5432/postgres?sslmode=disable
You can run the command docker compose up with this Docker Compose file in the same folder.
This will launch a LangGraph Server on port 8123 (if you want to change this, you can change this by changing the ports in the langgraph-api volume). You can test if the application is healthy by running:
curl --request GET --url 0.0.0.0:8123/ok
Assuming everything is running correctly, you should see a response like:
{"ok":true}