Is Umami ready for the Japanese market?
— a Tokyo native's gap map

umami.is renders only in English (lang="en"). The pricing page description reads: "Simple, usage-based pricing for Umami Cloud. Start free, scale as you grow." No Japanese version of the marketing or pricing exists.

umami.is — lang="en" confirmed umami.is/pricing — English only

A Japanese marketing manager or developer evaluating a privacy-friendly GA alternative reads the product page in Japanese or doesn't evaluate it. With the entire funnel in English, they assume the product, support, and compliance documentation are English too, and move to a Japanese-language alternative instead.

Japanese landing and pricing pages, plus a language toggle. In the privacy-analytics space specifically, a Japanese page that references the domestic regulatory context (Personal Information Protection Act, not just GDPR) would convert significantly better.

umami.is/privacy renders. No 特商法に基づく表記 page was found on the site. Umami Cloud references GDPR and CCPA compliance but not Japan-specific legal disclosure.

umami.is/privacy — no 特商法 found

Before paying for a SaaS subscription, Japanese buyers look for 特商法 disclosure. It's the accountability check — who is selling to me, what's the refund policy, who do I contact if something goes wrong. GDPR compliance is reassuring for European buyers but doesn't answer the Japanese question. Without 特商法, a careful buyer won't add the subscription to a company card.

A single 特商法に基づく表記 page linked in the footer. Required fields are defined by the Specified Commercial Transactions Act; a standard template fills them in. This is one of the cheapest fixes and immediately unblocks purchase decisions.

Umami Cloud is usage-based and billed in USD. No JPY pricing option or regional display was found on the pricing page.

umami.is/pricing — USD confirmed

A USD recurring charge means exchange-rate exposure and a foreign-currency line on a Japanese expense report. For monthly analytics subscriptions, even small amounts in USD require an exchange-rate conversion on every renewal statement — a minor but consistent friction point that domestic alternatives don't have.

JPY display on the pricing page. For cloud subscriptions, a JPY payment option removes the friction entirely for Japanese buyers doing expense accounting.

GitHub issue #297 in umami-software/umami called for community translations including Japanese. The status of the Japanese locale relative to the English product is not easily verified externally; if the translation is partial or stale, it reads as abandoned.

github.com/umami-software/umami/issues/297 — translation request

A partial or stale Japanese locale in a privacy-analytics product signals that the team tried Japan and deprioritized it. For a privacy-sensitive use case where the buyer is already thinking carefully about vendor reliability, a "half-translated and stale" impression cuts against the trust the product is trying to build.

A freshness pass on the Japanese locale by a native speaker, then a clear status note (what's translated, what isn't, last updated). Even "English only for now" is better than a stale half-translation.

With no Japanese pages on umami.is, there's nothing indexed for the terms Japanese marketers or developers actually search when looking for a GA alternative.

Privacy-conscious Japanese businesses searching 「google analytics 代替」 or 「クッキー不要 アクセス解析」 don't find Umami. They find Japanese-language roundup articles that often list domestic tools or the larger English-language alternatives with Japanese pages. Umami's genuine privacy advantage is invisible in the moment when buyers are comparing options.

A Japanese landing page that explicitly addresses Japan's privacy regulatory context (個人情報保護法, cookie consent laws), plus a 「google analytics 代替」 comparison page. The privacy angle is particularly strong in Japan given increasing scrutiny of foreign analytics providers.