--- title: "Langfuse Cloud Japan Region" description: "Langfuse Cloud Japan is live. A dedicated cloud region hosted in Japan for teams that need their LLM observability data to stay in Japan." date: 2026/04/27 tag: announcement author: Marc, Clemens, Max --- Open source has no geographical borders. Japan was one of the first markets in which Langfuse gained meaningful traction. [Just search for "langfuse" on X](https://x.com/search?q=langfuse&src=typed_query&f=live). Teams in Japan could find us, self-host Langfuse, and start building before we had time to market here. Today we're launching **[Langfuse Cloud Japan](/japan)**, a dedicated cloud region hosted in Japan for teams that need their LLM observability data to stay in Japan. ## Why Japan? We have well over a hundred customers in Japan today. These are all currently running on Langfuse Cloud EU or US, or are self-hosting. For many of them, that works just fine. For others, it doesn't: data residency requirements, compliance, legal restrictions, or simply not wanting to self-host. And of course, why wouldn't you prefer to run in your own region if you could? Langfuse Cloud Japan solves this. Traces, evaluations, and prompts stay in Japan. Latency also matters: running traces through Tokyo instead of Dublin or Oregon cuts round-trip time for applications and users across Japan and the broader APAC region, which adds up quickly for high-volume tracing workloads. This is the full Langfuse platform. Nothing is cut down. Japanese teams have been building on Langfuse for a while. LayerX runs evals and prompt experiments for their Bakuraku back-office AI agents on Langfuse, and freee builds on Langfuse across its accounting and HR products. Langfuse Cloud Japan now lets teams like these keep all of that data in-region without giving up any of the platform. ClickHouse, [which acquired Langfuse in January](/blog/joining-clickhouse), is the database underlying our technology. The new Japan region runs on ClickHouse in `ap-northeast-1` (Tokyo). But the infrastructure is only one part. As ClickHouse, we now have a Japanese subsidiary, a country manager in Kaneko-san, and a GTM and technical team on the ground in Tokyo. We are actively hiring and investing in the market. That means Langfuse Cloud Japan comes with boots on the ground and the ability to sell, onboard, and support customers in Japanese. ## The community behind Langfuse Japan On Friday, we hosted the fifth Langfuse Night, a community meetup, in Tokyo. Around 100 people showed up. That's a lot for a market we hadn't formally entered yet. That number is hard to process. The community in Japan is ahead of what we've built for it, and that's exactly why we want to invest more in this market. It's been wonderful to see a Japanese community evolve even while we did not yet have a physical presence. Kamon Nobuchika of GAO has been our only reseller in Japan for the past 18 months, working directly with customers while building community. A lot of what you see today traces back to his work. ## Getting started - [Langfuse Cloud Japan Region](/japan) - [Getting Started](/docs) - [Migrating to Langfuse Cloud Japan](/docs) - [Compliance and data residency](/security) - [Japan Mailing List](https://langfuse.app.n8n.cloud/form/b6fd623f-0d23-43ba-9c69-077675fe9f62) — launch updates, events in Japan, Japan-specific news ## Our commitment to Japan We plan to keep investing in our Japanese customers and community: more events, Japanese-language support, and continued development of the region. If you're an existing customer on EU or US and want to [migrate](/guides/cookbook/example_data_migration-jp), or evaluating Langfuse for the first time with Japan requirements in mind, [reach out](/talk-to-us) (we speak Japanese) — we'd love to help you get set up. --- ## 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/blog/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**: , 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 `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .