Networking

Langfuse can be deployed in a VPC or on-premises in high-security environments. This guide covers the networking requirements and considerations.

Architecture diagram (from architecture overview):

Network Exposure & Service Configuration

Only the langfuse/langfuse (web) container needs to be accessible by users, via API, and SDKs. Optionally, this can be behind a firewall, proxy, or VPN.

By default PORT=3000 is used for the Langfuse Web container. This can be configured using the PORT environment variable (docs). Usually a network load balancer is used to expose the service and handle ssl termination (docs).

Langfuse is designed to be exposed publicly as a web service. This is penetration tested and secure by design as the Langfuse Team runs the same container for the managed Langfuse Cloud Offering. See security documentation of Langfuse Cloud for more details.

Internet Access

Langfuse does not require internet access.

Some optional components, like the LLM Playground and LLM-evals require access to an LLM API/Gateway. This can be deployed in the same VPC or peered with the VPC.

Langfuse pings a cached version of the GitHub API to check for updates to the Langfuse Server. If internet access is not available, this check will fail gracefully.

If you experience any issues when self-hosting Langfuse, please:

1. Check out Troubleshooting & FAQ page.
2. Use Ask AI to get instant answers to your questions.
3. Ask the maintainers on GitHub Discussions.
4. Create a bug report or feature request on GitHub.

---

---