Langfuse project keys sit below organization authority
Langfuse collects traces, prompts, scores, datasets, and other data from applications using language models. Its public management surface may be only the beginning of the review. The API key model determines which project data a client can read or send, and the organization key model determines whether that client can manage projects and memberships.
A count-only ZoomEye query on 2026-11-21 measured app="Langfuse" at 5,524 index matches. title="Langfuse" returned 599. Both used sub_type=all, page 1, and page size 1. The product fingerprint is larger than the exact title count. That is an inventory observation, not proof that the matched deployments are self-hosted or that their project keys are exposed.
Langfuse documentation describes project API keys as scoped to one project and not tied to a user. Organization-scoped keys use Basic authentication and can administer projects, users, and project or organization memberships. Project keys are also used with Basic authentication for the general API. The project key pair should be shared only with the application or reporting job that needs that project. The organization key belongs in an administrative workflow with stronger controls.
The documentation shows project API key permissions introduced in 2026, including full access, viewer, ingestion, and scores ingestion. An ingestion key can send traces and scores without reading them. A viewer key is read-only. A full-access key is not the right default for an application that only reports telemetry. If the deployment predates scoped keys, rotate existing keys and recreate them with the narrowest permission that the integration supports.
The secret key is shown once and stored as a one-way hash. A lost secret cannot be recovered; create a new key and remove the old one. That makes key inventory and rotation practical controls, not just documentation details. Check the last-used column, expiry, and owner. Remove keys that are no longer used. If a key was placed in browser code, treat it as exposed even if the visible API has not shown suspicious use.
Review project boundaries separately from organization roles. A user can have an organization role and a project-level role. The effective role for a project may be the project role when one is assigned. A person who can see one project should not automatically see another. Test this with an authorized test user and an API key for each project. Do not attempt to enumerate projects belonging to another organization.
The public Langfuse surface should sit behind a strong identity provider and management network where possible. Separate production, staging, and development projects. Give each integration its own key. Monitor key creation, deletion, and last use. Reconcile the ZoomEye count with DNS, certificate, and deployment records before contacting an owner.
Langfuse needs application data to do its job. The key model should ensure that observability access does not become organization administration.
Exact query: app="Langfuse"
Open the normalized ZoomEye search
Top comments (0)