---
title: Where is my Langfuse project?
description: "Langfuse Cloud runs in the EU, US, Japan, and a separate HIPAA region. How to find which region holds your project, and how to move between them."
tags: [platform, auth, administration]
---

# I cannot find my project?

## Are you on the correct Langfuse tenant? (EU / US / Japan / HIPAA?)

Langfuse Cloud runs in multiple data regions: the [European Union](https://cloud.langfuse.com), the [US](https://us.cloud.langfuse.com), [Japan](https://jp.cloud.langfuse.com), and a separate [HIPAA-compliant US region](https://hipaa.cloud.langfuse.com).
Make sure that you are logged into the data region that you have created your project in. You can select the data region during log-in. You can also see it in the URL bar (`cloud.langfuse.com` = EU, `us.cloud.langfuse.com` = US, `jp.cloud.langfuse.com` = Japan, `hipaa.cloud.langfuse.com` = HIPAA).

Find out more about [Langfuse Cloud Data Regions](/security/data-regions).

## Are you using the correct email address?

If you have been invited to a project, make sure you are logging in with the exact email address that this invite has gone out to. If you log in with SSO (e.g. GitHub or Google), your email address might be different from what you expected.

If you click your name in the bottom left of the Langfuse UI, you will see the email address we have on record for you.

## Are you the project owner?

If someone else in your organization created the project, ask them to re-invite you and/or send you the link to the project you are looking for.

## Still cannot find your project?

Reach out to us via support@langfuse.com and add as much detail (e.g. project name, ID, email associated with it, workers on the project etc) as possible.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/where-is-my-project.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.