Skip to main content

Frequently Asked Questions:

How does load balancing/ingress work?

  • You will need to expose the frontend container/service to your applications/users. This will handle routing to all downstream services.
  • You will need to terminate SSL at the ingress level. We recommend using a managed service like AWS ALB, GCP Load Balancer, or Nginx.

How can we authenticate to the application?

  • Currently, our self-hosted solution supports SSO with OAuth2.0 and OIDC as an authn solution. Note, we do offer a no-auth solution but highly recommend setting up oauth before moving into production.

You can find more information on setting up SSO in the configuration section.

Can I use external storage services?

  • You can configure LangSmith to use external versions of all storage services. In a production setting, we strongly recommend using external storage services. Check out the configuration section for more information.

Does my application need egress to function properly?

Our deployment only needs egress for a few things:

  • Fetching images (If mirroring your images, this may not be needed)
  • Talking to any LLMs
  • Talking to any external storage services you may have configured
  • Fetching OAuth information

Your VPC can set up rules to limit any other access.
Note: We require the X-Organization-Id and X-Tenant-Id headers to be allowed to be passed through to the backend service. These are used to determine which organization and workspace (previously called "tenant") the request is for.

Resource requirements for the application?

  • In kubernetes, we recommend a minimum helm configuration which can be found in here. For docker, we recommend a minimum of 16GB of RAM and 4 CPUs.
  • For Postgres, we recommend a minimum of 8GB of RAM and 2 CPUs.
  • For Redis, we recommend 4GB of RAM and 2 CPUs.
  • For Clickhouse, we recommend 32GB of RAM and 8 CPUs.

Was this page helpful?

You can leave detailed feedback on GitHub.