Langfuse discovery needs project scope and prompt-data retention
Langfuse stores traces, observations, scores, prompts, datasets, and related project settings. An exposed Langfuse project can therefore reveal application behavior and user interaction data that never appears in a conventional monitoring dashboard. External discovery should identify candidates for an owner, not invite content enumeration.
A count-only ZoomEye measurement on 2026-10-29 returned 5,487 matches for app="Langfuse" and 438 for title="Langfuse". Both used sub_type=all, page 1, and page size 1. The application fingerprint is larger and selected. The numbers count matching observations at that time. They are not public projects, leaked prompts, or confirmed weak access controls.
Project keys are separate from user authority
Langfuse's data-isolation documentation describes project-scoped API keys and role-based access. User requests carry a project context, and the server checks that the user or key is authorized for that project. Project keys are not tied to a user account, which means removing a person's membership does not automatically revoke a key the person could previously read or use.
Inventory project public and secret keys by application and environment. Langfuse added permission choices for project API keys in October 2026, including viewer, ingestion, scores ingestion, and full access. Use the narrowest permission that supports the integration. A telemetry sender needs ingestion rights, not the ability to read traces or prompts. A reporting job needs read-only access. A full-access key should be rare and strongly protected.
The organization API and SCIM controls are a separate authority plane. Organization-scoped keys can administer projects, users, and memberships. They should not be stored in individual project applications. Review organization membership, SSO, SCIM deprovisioning, and the instance management key separately from project telemetry access.
Keep trace data inside the right project
Separate production, staging, and development data into projects when the access policy requires it. Use project roles for people who need visibility into one application and not another. Check whether an organization role gives every user access to every project by inheritance, then assign project roles where the organization supports them.
Prompt and response data can contain personal or confidential information. Review payload collection, redaction, retention, and export settings before assuming that a project boundary is sufficient. A viewer role can still be a disclosure risk if the project contains data that should not be retained at all. Document which datasets and prompts are allowed to leave the application.
Test key revocation and expiry. Langfuse's October 2026 changelog describes expiration options and a create-replacement then delete-old-key rotation flow. Use the Last used view to identify unused credentials. Rotate a project key before deleting it, verify that the new integration works, and then invalidate the old secret. For an incident, remove membership and revoke the keys that member could access.
Turn the external count into an ownership review
The 5,487 app matches are a candidate set. Confirm ownership through the organization's domains, certificates, cloud accounts, or internal inventory before contacting the service. Do not attempt to read unowned traces or test a public project with guessed credentials. A product fingerprint shows the technology, not authorization state.
For each owned project, record endpoint, project identifier, owner, data class, key permissions, retention period, and review date. Exercise an anonymous request, a viewer key, an ingestion key, and a full-access key against the expected operations. Verify that a key cannot select another project. Check audit logs for project creation, key creation, membership changes, and exports.
Langfuse's product is designed around project-level isolation. The control is only as good as the key assignment and membership process around it. The ZoomEye count can reveal a forgotten endpoint. The project inventory and key matrix show whether the endpoint leads to data that the organization intended to keep.
Top comments (0)