June 2026 performance summary focused on enabling scalable self-hosted deployments for LangSmith via Helm enhancements. Delivered the Self-hosted Resource Uncapping feature in the langchain-ai/helm repository, enabling admins to allocate larger CPU and memory resources for self-hosted LangSmith deployments when needed. Implemented as a Helm chart option uncappedResourcesEnabled (default false) and wired to the ENABLE_UNCAPPED_LGP_DEPLOYMENT_RESOURCES env var, following the existing langsmith.commonEnv pattern. When enabled, host-backend ResourceSpec validators bypass the SaaS CPU/memory upper caps (retaining floors and 128MB granularity). This feature is a companion to langchain-ai/langchainplus#27405 and includes updates to values.yaml and related deployment descriptions to reflect the new capability. Commit reference: 7a4cc5e0899ab0bce8d8fe11f59a46603c73e161.

May 2026 monthly summary focusing on core business value and technical achievement across two repos. Highlights include deployment configurability improvements in Helm for LangGraph Cloud and expanded private endpoint connectivity for LangSmith deployments in EU, along with comprehensive documentation updates and quality checks.

April 2026 focused on strengthening self-hosted deployment reliability and multi-dataplane scalability in the langchain-ai/helm repo. Delivered two major features with clear business value and accompanying hygiene work: 1) Self-hosted deployment improvements in the Helm chart: wired Microsoft OAuth provider mapping to enable Outlook, Teams, SharePoint, and 365 Docs tools in self-hosted deployments; added Gateway API and Istio VirtualService ingress options; removed the studio component; cleaned ingress templates; bumped the chart version. These changes close configuration gaps, reduce silent outages for enterprise customers, and simplify upgrades. 2) Multi-dataplane scalability: introduced a configurable HOST_QUEUE to ensure unique Redis queue names per release, preventing listener collisions when multiple dataplane deployments share Redis. Default remains 'host' to preserve compatibility and avoid migrations. Additional context: changes were implemented alongside related refactors and value alignment (ingress pruning, validation, and templating hygiene) to improve maintainability and operator experience.