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

Plane ships 27 Japanese locale JSON files across UI domains. However, GitHub issue #9082 — open as of 2026-06-20 — is titled "feat(i18n): localize remaining hardcoded UI surfaces" and confirms that English strings remain hardcoded in multiple parts of the interface. This means a Japanese user switching to Japanese encounters a mixed-language product.

github.com/makeplane/plane/issues/9082 — "localize remaining hardcoded UI surfaces" (open) github.com/makeplane/plane — packages/i18n/src/locales/ja (27 files)

Project management software runs every day, across every team member's screen, for every project. When the interface is partially in Japanese and partially in English, it is not a minor issue — it is a daily friction for every user in a Japanese team. The incomplete state signals that Plane's Japanese investment is an unfinished commitment, which for enterprise software evaluation means it doesn't yet qualify as "supported in Japanese."

Complete the remaining hardcoded strings (issue #9082). A one-time engineering effort to audit every UI surface and route the strings through the i18n system. Once done, the Japanese locale moves from "partial" to "complete" — which is a material threshold for enterprise evaluation.

plane.so has legal pages (Terms, Privacy), but no 特商法に基づく表記 is present for its paid Cloud Pro ($6/user/month) or Teams ($10/user/month) tiers.

plane.so/pricing (Pro $6/mo, Team $10/mo — checked for 特商法 — absent)

Plane targets Jira as its reference competitor. Japanese enterprises using Jira have Atlassian's Japanese entity and compliance documentation as a baseline. When they evaluate Plane as an alternative, the 特商法 page is part of the vendor qualification checklist. Plane's absence at this point in the evaluation ends the conversation for procurement — not the engineering team, but the people who sign contracts.

A 特商法に基づく表記 page for the paid Cloud tiers. One-day effort using the standard template. This is the highest-leverage single action for enterprise conversion in Japan.

plane.so is fully English-only. No Japanese page exists, no language selector is present in the marketing layer, and no hrefLang tags for Japanese are included. The product's internal Japanese locale is invisible from the outside.

plane.so (lang="en", no language switcher, no Japanese content)

A Japanese project manager searching for a Jira alternative in Japanese finds no plane.so pages — despite the product having a Japanese locale that would serve them well. The discovery moment is missing. The marketing site does not signal that the product speaks Japanese, so teams that would benefit from it never make it to the product evaluation.

A Japanese landing page for the Jira alternative use case. Once the locale is complete (G1), advertising that the product is in Japanese on the landing page is a compelling differentiator vs. Jira, which is English-heavy in its interface.

Plane Cloud Pro is $6/user/month and Teams is $10/user/month. All pricing is in USD. No JPY display or currency option is available.

plane.so/pricing ($6/user/mo, $10/user/mo — USD only)

For a 20-person Japanese team evaluating Plane vs. Jira, the Plane pricing at $10/user/month translates to approximately ¥200,000/month at recent exchange rates — a recurring foreign-currency expense. Japanese companies that expense software through their finance team prefer JPY pricing because it removes the accounting overhead of tracking exchange rate variance on a monthly invoice. Jira offers JPY billing in Japan; Plane does not.

JPY display pricing. For annual Team and Enterprise contracts, JPY invoicing. This removes the last procurement friction once the technical evaluation is complete.

No Japanese-language Plane page is indexed. Searches for 「Jira 代替 OSS」, 「プロジェクト管理 オープンソース」, or 「チケット管理 無料」 return no plane.so results. The Japanese locale investment creates no search visibility benefit.

The Jira-alternative search in Japan is active. Teams that have outgrown free tools, or are looking to reduce Atlassian costs, search for alternatives in Japanese. Plane doesn't appear — it is invisible at the evaluation moment for the exact audience it is built for.

A Japanese landing page for「Jira 代替」, announcing the Japanese locale (once complete) and showing pricing. With a functional Japanese product, Plane has a legitimate claim on this search traffic that most OSS alternatives cannot make.