From 73a33c2b673d33ed83594769c289416eda5fa231 Mon Sep 17 00:00:00 2001 From: langchain-infra Date: Wed, 22 Apr 2026 21:39:52 -0400 Subject: [PATCH 1/2] docs: surface Valkey support on the external Redis page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Valkey has been an officially supported drop-in replacement for Redis since LangSmith Self-Hosted v0.14, but the only reference on the external Redis page was a buried inline note in the Requirements list. - Update the page title and sidebar title to "Connect to an external Redis or Valkey database" so it shows up in nav and search. - Add a dedicated intro paragraph calling out Valkey as a drop-in replacement, linking to the Requirements section. - Promote the supported versions line to a first-class bullet (Redis >= 5, or Valkey 8) instead of a "Note:" aside. - Annotate ElastiCache and Memorystore as Redis-or-Valkey. Azure intentionally unchanged — no Valkey variant exists there. --- src/langsmith/self-host-external-redis.mdx | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/src/langsmith/self-host-external-redis.mdx b/src/langsmith/self-host-external-redis.mdx index 88f5952905..53ed006f6a 100644 --- a/src/langsmith/self-host-external-redis.mdx +++ b/src/langsmith/self-host-external-redis.mdx @@ -1,10 +1,12 @@ --- -title: Connect to an external Redis database -sidebarTitle: Connect to an external Redis database +title: Connect to an external Redis or Valkey database +sidebarTitle: Connect to an external Redis or Valkey database --- LangSmith uses Redis to back our queuing/caching operations. By default, LangSmith Self-Hosted will use an internal Redis instance. However, you can configure LangSmith to use an external Redis instance. By configuring an external Redis instance, you can more easily manage backups, scaling, and other operational tasks for your Redis instance. +[Valkey](https://valkey.io/) is also officially supported as a drop-in replacement for Redis. Anywhere this page refers to Redis, you can use a compatible Valkey instance. See [Requirements](#requirements) for supported versions. + Each LangSmith installation must use its own dedicated Redis instance. Redis cannot be shared across separate LangSmith installations (for example, between an existing and new cluster during a migration). Sharing it across installations causes deployment tasks to be routed to the wrong cluster. @@ -20,14 +22,14 @@ For cloud-specific IAM/Workload Identity authentication, refer to the [IAM authe ## Requirements -* A provisioned Redis instance that your LangSmith instance will have network access to. We recommend using a managed Redis service like: +* A provisioned Redis or [Valkey](https://valkey.io/) instance that your LangSmith instance will have network access to. We recommend using a managed service like: - * [Amazon ElastiCache](https://aws.amazon.com/elasticache/redis/) - * [Google Cloud Memorystore](https://cloud.google.com/memorystore) + * [Amazon ElastiCache](https://aws.amazon.com/elasticache/redis/) (Redis or Valkey) + * [Google Cloud Memorystore](https://cloud.google.com/memorystore) (Redis or Valkey) * [Azure Cache for Redis](https://azure.microsoft.com/en-us/services/cache/) -* Note: We only officially support Redis versions >= 5 and Valkey version 8. -* We support both Standalone and Redis Cluster. See the appropriate sections for deployment instructions. +* **Supported versions:** Redis >= 5, or Valkey 8. Valkey is treated as a drop-in replacement for Redis throughout this guide. +* We support both Standalone and Redis Cluster (including Valkey Cluster). See the appropriate sections for deployment instructions. * We support no authentication, password, and [IAM/Workload Identity](#iam-authentication) authentication. * By default, we recommend an instance with at least 2 vCPUs and 8GB of memory. However, the actual requirements will depend on your tracing workload. We recommend monitoring your Redis instance and scaling up as needed. From 15c56895049d1b8a5b4ccac20178027d7489f01e Mon Sep 17 00:00:00 2001 From: langchain-infra Date: Wed, 22 Apr 2026 21:44:09 -0400 Subject: [PATCH 2/2] docs: mention Valkey on AWS/GCP/self-hosted overview pages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cross-links to the external Redis page weren't enough — a reader scanning the AWS or GCP self-hosted pages for their infra checklist could miss that ElastiCache for Valkey and Memorystore for Valkey are supported. - AWS self-hosted: card subtitle now reads "Redis or Valkey for caching"; ElastiCache reference-architecture bullet lists Redis or Valkey and spells out the supported versions (Redis >= 5, Valkey 8). - GCP self-hosted: same treatment for the Memorystore card and bullet, linking to the Memorystore for Valkey product page. - Self-hosted overview: datastore table row renamed to "Redis / Valkey", adds a sentence noting Valkey is a drop-in replacement, and updates the link label to "Connect to external Redis or Valkey". Azure intentionally unchanged — no Azure managed Valkey offering. --- src/langsmith/aws-self-hosted.mdx | 4 ++-- src/langsmith/gcp-self-hosted.mdx | 4 ++-- src/langsmith/self-hosted.mdx | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/langsmith/aws-self-hosted.mdx b/src/langsmith/aws-self-hosted.mdx index aea259d63c..f91e5b10cc 100644 --- a/src/langsmith/aws-self-hosted.mdx +++ b/src/langsmith/aws-self-hosted.mdx @@ -41,7 +41,7 @@ View the [AWS Terraform modules](https://github.com/langchain-ai/terraform/tree/ PostgreSQL database - Redis for caching + Redis or Valkey for caching Analytics database @@ -71,7 +71,7 @@ We recommend leveraging AWS's managed services to provide a scalable, secure, an - **Frontend & backend services:** Containers run on [Amazon EKS](https://aws.amazon.com/eks/), orchestrated behind the ALB. routes requests to other services within the cluster as necessary. - **Storage & databases:** - [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/) or [Aurora](https://aws.amazon.com/rds/aurora/): metadata, projects, users, and short-term and long-term memory for deployed agents. LangSmith supports PostgreSQL version 14 or higher. - - [Amazon ElastiCache (Redis)](https://aws.amazon.com/elasticache/redis/): caching and job queues. ElastiCache can be in single-instance or cluster mode, running Redis OSS version 5 or higher. + - [Amazon ElastiCache](https://aws.amazon.com/elasticache/) (Redis or Valkey): caching and job queues. ElastiCache can be in single-instance or cluster mode. LangSmith requires Redis OSS version 5 or higher, or Valkey 8. - ClickHouse + [Amazon EBS](https://aws.amazon.com/ebs/): analytics and trace storage. - We recommend using an [externally managed ClickHouse solution](/langsmith/self-host-external-clickhouse) unless security or compliance reasons prevent you from doing so. diff --git a/src/langsmith/gcp-self-hosted.mdx b/src/langsmith/gcp-self-hosted.mdx index 80dcd72512..74bc673341 100644 --- a/src/langsmith/gcp-self-hosted.mdx +++ b/src/langsmith/gcp-self-hosted.mdx @@ -41,7 +41,7 @@ View the [GCP Terraform modules](https://github.com/langchain-ai/terraform/tree/ PostgreSQL database - Redis for caching + Redis or Valkey for caching Analytics database @@ -71,7 +71,7 @@ We recommend leveraging GCP's managed services to provide a scalable, secure, an - **Frontend & backend services:** Containers run on [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine), orchestrated behind the load balancer. Routes requests to other services within the cluster as necessary. - **Storage & databases:** - [Cloud SQL for PostgreSQL](https://cloud.google.com/sql/docs/postgres): metadata, projects, users, and short-term and long-term memory for deployed agents. LangSmith supports PostgreSQL version 14 or higher. - - [Memorystore for Redis](https://cloud.google.com/memorystore/docs/redis): caching and job queues. Memorystore can be in single-instance or cluster mode, running Redis OSS version 5 or higher. + - [Memorystore](https://cloud.google.com/memorystore) ([Redis](https://cloud.google.com/memorystore/docs/redis) or [Valkey](https://cloud.google.com/memorystore/docs/valkey)): caching and job queues. Memorystore can be in single-instance or cluster mode. LangSmith requires Redis OSS version 5 or higher, or Valkey 8. - ClickHouse + [Persistent Disks](https://cloud.google.com/compute/docs/disks): analytics and trace storage. - We recommend using an [externally managed ClickHouse solution](/langsmith/self-host-external-clickhouse) unless security or compliance reasons prevent you from doing so. diff --git a/src/langsmith/self-hosted.mdx b/src/langsmith/self-hosted.mdx index cc0ee84bc7..dea63fa8bd 100644 --- a/src/langsmith/self-hosted.mdx +++ b/src/langsmith/self-hosted.mdx @@ -116,7 +116,7 @@ LangSmith will bundle all storage services by default. You can configure it to u |---------|-------------| | **ClickHouse** | [ClickHouse](https://clickhouse.com/docs/en/intro) is a high-performance, column-oriented SQL database management system (DBMS) for online analytical processing (OLAP).

LangSmith uses ClickHouse as the primary data store for traces and feedback (high-volume data).

💡 [Connect to external ClickHouse](/langsmith/self-host-external-clickhouse) | | **PostgreSQL** | [PostgreSQL](https://www.postgresql.org/about/) is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads.

LangSmith uses PostgreSQL as the primary data store for transactional workloads and operational data (almost everything besides traces and feedback).

💡 [Connect to external PostgreSQL](/langsmith/self-host-external-postgres) - AWS RDS, GCP Cloud SQL, Azure Database | -| **Redis** | [Redis](https://github.com/redis/redis) is a powerful in-memory key-value database that persists on disk. By holding data in memory, Redis offers high performance for operations like caching.

LangSmith uses Redis to back queuing and caching operations.

💡 [Connect to external Redis](/langsmith/self-host-external-redis) - AWS ElastiCache, GCP Memorystore, Azure Cache | +| **Redis / Valkey** | [Redis](https://github.com/redis/redis) is a powerful in-memory key-value database that persists on disk. By holding data in memory, Redis offers high performance for operations like caching.

LangSmith uses Redis to back queuing and caching operations. [Valkey](https://valkey.io/) is also officially supported as a drop-in replacement for Redis.

💡 [Connect to external Redis or Valkey](/langsmith/self-host-external-redis) - AWS ElastiCache, GCP Memorystore, Azure Cache | | **Blob storage** | LangSmith supports several blob storage providers, including [AWS S3](https://aws.amazon.com/s3/), [Azure Blob Storage](https://azure.microsoft.com/en-us/services/storage/blobs/), and [Google Cloud Storage](https://cloud.google.com/storage).

LangSmith uses blob storage to store large files, such as trace artifacts, feedback attachments, and other large data objects. Blob storage is optional, but highly recommended for production deployments.

💡 [Enable blob storage](/langsmith/self-host-blob-storage) - AWS S3, GCP GCS, Azure Blob | To install, follow the [Kubernetes setup guide](/langsmith/kubernetes).