Patient support and intake
Answer patient questions and complete intake in less time. Clinicians and domain experts review the cases that need a person.
For healthcare and life sciences teams: go live faster, spend less time on manual review, and keep costs in view as you scale. Merck Group reduced development cycles from weeks to days and runs 80+ use cases on Langfuse.
HIPAA-ready cloud region with a self-serve BAA: Sign the ClickHouse BAA, then send PHI only to the dedicated US region.
Self-host so patient data never leaves your network: Run Langfuse in your VPC or in an air-gapped environment.
Clinician or domain expert review in platform: Send traces and dataset items to annotation queues for clinicians or domain experts to review, correct, and pinpoint failure modes.
Quality gates and evidence for audits: Evaluate changes with datasets and experiments before going live, and keep traces and scores for review.
One platform for every AI team: Orchestrate one platform for tracing, evals, and cost tracking across teams. Govern centrally across the org.
Used by 21 of the Fortune 50
90B+ observations/month
100,000+ engineers building on Langfuse
Used by 21 of the Fortune 50
90B+ observations/month
100,000+ engineers building on Langfuse
HIPAA-ready cloud region
A separate US region for healthcare and life sciences workloads. Sign the ClickHouse BAA before you send PHI. Docs →
Self-host or air-gap
Run Langfuse in your own network, including a deployment with no internet access. Patient data stays there. Docs →
Masking
Remove or replace PHI in inputs, outputs, and metadata before it is stored. Docs →
Access controls
SSO and role-based access scoped to organizations and projects. Docs →
Audit logs
Record prompt changes, membership changes, and other admin actions, with the user or API key that made the change. Docs →
HIPAA-ready region in the US. BAA available.
Your app→OTel SDK→HIPAA region
Evaluate agents or datasets before release. Have clinicians and domain experts review the results and check that your AI judges agree with those labels.
Offline evals, clinician or domain expert review, judge calibration, and production checks.
Run a dataset experiment on each change. Fail the release when a score drops below your threshold.
Docs →Annotation queues are an in-app review flow. Clinicians or domain experts label traces and can save a corrected output before a release.
Docs →Score Analytics compares AI judge scores with clinician or domain expert labels. Agreement metrics include Cohen's Kappa, F1, Pearson, and Spearman.
Docs →Run compliance and quality checks with automated evaluators on production traces.
Code evaluatorsDecision model evaluatorsControl prompts, protect data, and manage access.
Keep immutable prompt versions. Use labels for staging and production, and protect the production label.
Docs →Mask inputs, outputs, and metadata in the SDK before trace data leaves your application.
Docs →Organizations and projects are the data boundary. Role-based access limits who can open a project.
Docs →Set a retention window per project. Export observations and scores to your own bucket when you need a longer archive.
Docs →Use cases
Answer patient questions and complete intake in less time. Clinicians and domain experts review the cases that need a person.
Book and change appointments with fewer failed or wrong bookings for staff to fix. Test representative cases before the agent goes live.
Turn around inquiries from healthcare professionals in less time.
Draft clinical notes from visits and conversations, with less rework on the drafts clinicians review.
Catch failing claim steps early, before they become manual rework, and keep a trace for audit.
Find where a voice conversation lost context and correct it. Evolve cut Rest's memory misses in half.
Evolve: Rest sleep coach
Share traces, prompts, evaluations, and cost across teams, so the same platform works company-wide.
Merck Group: 80+ use cases on Langfuse
Start with datasets and release gates. Then read how Merck Group and Evolve use Langfuse.
Evaluate model and prompt changes against datasets before release.
Design ground-truth datasets with clear inputs, expected outputs, and a review rubric.
How Merck Group serves 80+ AI teams on self-hosted Langfuse.
How Evolve traces and evaluates Rest, a voice-and-text sleep coach.
Create a fresh Langfuse Cloud account in the HIPAA-ready region. The region runs in Oregon (AWS us-west-2) at hipaa.cloud.langfuse.com. Subscribe to the Pro plan or higher. Complete and sign the ClickHouse Business Associate Agreement via Ironclad before you process PHI. That form is the ClickHouse BAA for Langfuse HIPAA Cloud. It asks for your Langfuse organization ID. Where to find the organization ID. Send HIPAA-regulated data only to that region. It is separate from the EU, US, and Japan regions. In a self-hosted deployment, Langfuse does not receive or process your data, so no BAA with Langfuse is involved. You implement the HIPAA safeguards in your own environment. HIPAA docs.
Configure SDK masking to remove or replace sensitive inputs, outputs, and metadata before trace data leaves your application. You can also apply masking in an OpenTelemetry Collector inside your infrastructure. Self-hosted Enterprise can mask again during ingestion. SDK masking, server-side masking.
Eligible plans are the Pro plan or higher, in the HIPAA-ready region. Customers on those plans can sign a BAA before they process PHI. HIPAA docs, Cloud pricing.
Langfuse's observability integrations collect and export traces in the background while your application continues to call its model provider or gateway. You do not need to route model requests through Langfuse to use observability. If you also use prompt management, SDK caching and fallback prompts help keep your application resilient to connectivity issues. Background export, prompt availability.
Yes, on a self-hosted deployment. LLM-as-a-judge calls the model in an LLM connection. Point that connection at a model endpoint inside your network, and allow the host in the self-hosted LLM connection settings. On Langfuse Cloud, the connection base URL has to be a public HTTPS endpoint. LLM connections, self-hosted LLM API.
Talk through the HIPAA-ready region, self-hosting, and how Merck Group and Evolve use Langfuse.
No credit card required, free tier available, self-hosting option