---
date: 2026-04-27
title: Langfuse Cloud Japan
description: A new dedicated cloud region in Tokyo keeps traces, prompts, and evaluation data inside Japan.
author: Clemens
canonical: /japan
ogImage: /images/changelog/2026-04-27-langfuse-cloud-japan.png
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/japan) and the API/SDK reference (https://api.reference.langfuse.com).

Langfuse Cloud is now live in a dedicated Japan region, hosted in Tokyo (`ap-northeast-1`). Traces, prompts, and evaluation data stay in Japan. Langfuse Cloud Japan is available via https://jp.cloud.langfuse.com - you can sign up now.

## What is Langfuse Cloud Japan?

- **Full platform parity** with Cloud EU and Cloud US — same features, same API surface, same SDK support
- **Data stays in Japan** — traces, prompts, and evaluation records are stored and processed in Tokyo
- **Japanese-speaking team** based in Tokyo for sales and support
- **Migration path** from Cloud EU or Cloud US — [data migration script](/guides/cookbook/example_data_migration). You can reach out to us if you have a very large amount of trace data to migrate (>2M observations)

## Get started

- [Langfuse Cloud Japan](/japan)
- [Getting Started (日本語)](/docs)
- [Compliance & Data Residency](/security)
- [Talk to us](/talk-to-us)

<!-- 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/changelog/2026-04-27-langfuse-cloud-japan.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>.