Enterprise License Key
All core Langfuse features and APIs are available in Langfuse OSS (MIT licensed) without any limits.
When running Langfuse self-hosted, you use the same deployment infrastructure as Langfuse Cloud. There are no scalability limitations between the different versions.
Some additional Enterprise features require a license key:
- Project-level RBAC Roles
- Protected Prompt Labels
- Data Retention Policies
- Audit Logs
- Server-Side Data Masking
- UI Customization
- Organization Creators
- Org Management API and SCIM
- Instance Management API
See pricing page for more details on Langfuse Enterprise.
Activating a License Key
After purchasing a license key, you can activate it by adding the following environment variable to your Langfuse deployment (both langfuse containers):
LANGFUSE_EE_LICENSE_KEY=<your-license-key>Enterprise self-hosted deployments use limited telemetry for license compliance. See the telemetry documentation for the exact fields that are collected.
FAQ
How do I remove my Enterprise license key?
To remove the key, remove LANGFUSE_EE_LICENSE_KEY from both Langfuse containers (web and worker) and restart the deployment. All core OSS features continue to work without a license key.
Before doing so, make sure you no longer rely on any of the Enterprise features listed above. Otherwise, removing the key may cause unwanted behavior. For example:
- Project roles and protected prompt labels: Existing settings remain in effect, but their Enterprise UI controls become unavailable. Clear unwanted settings first. If you clear a project role for a user whose organization role is
NONE, they lose access to that project. - Data retention: Existing policies keep deleting expired data. Set retention to indefinite on projects where deletion should stop.
- Server-side data masking: Masking stops for new events. Move it to your application or SDK before sending sensitive data.
- Audit logs: The viewer and read API become unavailable. Export any logs you will need.
- Provisioning and administration: The Organization Management API, SCIM, and Instance Management API return
403. Replace dependent automation before removal; existing resources remain. - UI and organization creation: UI customizations revert to defaults, and the organization creator allowlist stops restricting eligible users.
Questions?
If you have any questions about licensing, please contact us.
If you experience any issues when self-hosting Langfuse, please:
- Check out Troubleshooting & FAQ page.
- Use Ask AI to get instant answers to your questions.
- Ask the maintainers on GitHub Discussions.
- Create a bug report or feature request on GitHub.
Enterprise-grade support is available when self-hosting Langfuse. Learn more on our pricing page.
Last updated on
