Langfuse Self-Hosted

Self-hosted LLM observability, evaluations and prompt-management platform.

10 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Langfuse GitHub Enterprise SSO SSRF fix

Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO.

Scope: Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.

Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target.

Action: Upgrade to v4.82.0 or later and restrict outbound SSO connectivity.

Primary source · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.

  2. Operated by

    Your team

    Customer operates the deployment, persistence, access policies, retention, backups and scaling.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.
InfrastructureServers / containers
The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.
Licensing modelOpen Source / Open Core
The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.
LicenseMIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review.

Self-hosted OAuth/OIDC sign-in · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity.

Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note. · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports.

Upstream Compose recipe; supporting-service operations remain customer responsibilities · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint.

Langfuse Web/Worker resource recommendation; backing services additional · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional.

Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse.

Upstream Langfuse self-hosted release · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Show all fields (6 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.

Category fit

AI observability & LLMOps
LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.
AI tools & infrastructure
Self-hosted LLM observability, evaluations and prompt-management platform.
Observability
Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling.

Compare within AI observability & LLMOps

  • Arize Phoenix Self-HostedAI observability and evaluation server for traces, datasets and application experiments.
    • AWS
    • Azure
    • Google Cloud
    • Railway
    • Render
    Customer-operated · Source Available
  • MLflow Tracking Server Self-HostedSelf-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • OpenLITOpenTelemetry-based AI tracing and evaluation platform for model and agent operations.
    • DigitalOcean
    Customer-operated · Open Source / Open Core

These products address related workflows; read their category-fit notes before comparing scope. See all of AI observability & LLMOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Langfuse customer cloud deployment on AWS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

    • Langfuse customer cloud deployment on Azure ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

    • Langfuse customer cloud deployment on Google Cloud ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.

    • Langfuse v3 community Railway deployment ↗ · Railway

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.

    • Langfuse v4 community Render Blueprint ↗ · Render

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory