greymoth · field report · 2026-06-25
How ready are foreign developer tools for the Japanese market? A live audit of 40 popular tools — measured at the surface a Japanese buyer hits before they can adopt or pay.
Each tool is scored 0–100 across five live-checked signals — 特商法 page (25), localized /ja site (25), Japanese copy (20), hreflang ja (15), JPY pricing (15) — and every number above links to the evidence. How it's scored ▾
| # | Tool | Category | 特商法 | JP site | JP copy | hreflang | JPY | Score | Tier | |
|---|---|---|---|---|---|---|---|---|---|---|
| 01 | Auth0auth0.com | Auth / Identity | ○ | ● | ● | ● | ○ | 60 | PARTIAL | ▸ |
|
特商法 ○ Footer of auth0.com/jp shows Legal / Privacy / Terms only — no 特商法 page. JP site ● auth0.com/jp = HTTP 200, <html lang="ja">, fully Japanese marketing copy (heading 「Auth0：誰もが安全にアクセスするために。」, nav 開発者/製品/料金体系). JP copy ● Entire /jp site is native Japanese, including pricing page in Japanese. hreflang ● Homepage HTML carries hrefLang="ja". JPY ○ auth0.com/jp/pricing is in Japanese but priced in USD: 「$35 / 月」, 「$385」. No JPY, no toggle. Gap. Has the strongest JP localization in this index (full Japanese site, JP search-discoverable) — but still prices in USD and has no 特商法 page, the two procurement-gate items. If you fixed it. Add a 特商法に基づく表記 page to the /jp footer and a JPY display reference on the JP pricing page. Two static changes finish an otherwise JP-ready front door. |
||||||||||
| 02 | Twilio Segmenttwilio.com | CDP / Analytics | ○ | ● | ● | ● | ○ | 60 | PARTIAL | ▸ |
|
特商法 ○ twilio.com/ja-jp footer = privacy / security / terms / careers — no 特商法 link. JP site ● twilio.com/ja-jp = <html lang="ja-jp">, native Japanese marketing (heading 「驚くような顧客体験が生まれる場所」), Segment covered (「Twilio Segment 顧客データプラットフォーム」). JP copy ● Full Japanese engagement-platform copy across the /ja-jp site. hreflang ● /ja redirects to /ja-jp; Twilio emits multi-locale hreflang. JPY ○ Segment pricing is USD-only with no JPY display. Gap. Segment rides Twilio's mature ja-jp site, so localization and JP discoverability are strong — but no 特商法 page and USD-only pricing remain. If you fixed it. Add 特商法 to the JP footer and a JPY pricing reference for the Segment line. |
||||||||||
| 03 | HashiCorp (Terraform / Vault)hashicorp.com | Infra / DevOps | ○ | ● | ● | ? | ○ | 45 | PARTIAL | ▸ |
|
特商法 ○ Footer of the JP site lists Terms / Trust Center / Trademark / Trade Controls — no 特商法 page. JP site ● hashicorp.com/ja = <html lang="ja">, full Japanese marketing copy (heading 「HashiCorp: イノベーションはインフラストラクチャからはじまります」, nav プラットフォーム/製品/開発者/会社情報). JP copy ● Extensive native Japanese product descriptions, case studies, webinars. hreflang ? Homepage hreflang not confirmed (bot rate-limit 429 on direct route probes); JP site itself renders lang=ja. JPY ○ Cloud pricing is USD-denominated; no JPY toggle observed. Gap. A genuinely localized Japanese site — but missing the 特商法 page and JPY pricing that JP procurement and finance look for. If you fixed it. Publish a 特商法 page in the JP footer; add JPY reference pricing. The localization is already done — the commercial/legal surface lags it. |
||||||||||
| 04 | Appwriteappwrite.io | BaaS (auth / DB / storage) | ○ | ○ | ◐ | ○ | ○ | 10 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page on appwrite.io. JP site ○ appwrite.io English-only, no /ja route, no language switcher. JP copy ◐ Product ships a bundled Japanese UI locale: app/config/locale/translations/ja.json exists — but at 247 keys vs en 295 it is ~16% (48 keys) behind (gh raw-file count). hreflang ○ No hreflang ja in homepage markup. JPY ○ USD-only pricing. Gap. The product UI has a Japanese locale — but it is measurably 16% behind English, and the marketing/commercial surface (site, pricing, 特商法) is fully English. The clearest 'quantifiable gap' case in this index. If you fixed it. Fill the 48 missing ja.json keys, then add a JP landing page + hreflang + 特商法 so JP buyers can find and approve it. |
||||||||||
| 05 | Coolifycoolify.io | Self-host PaaS | ○ | ○ | ◐ | ○ | ○ | 10 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page on coolify.io. JP site ○ English-only site, no /ja route. JP copy ◐ Product ships a maintained Japanese UI (lang/ja.json), a peer of en. hreflang ○ No hreflang ja. JPY ○ USD pricing. Gap. Self-host dashboard is localized to Japanese, but the marketing site offers nothing for a Japanese buyer. If you fixed it. A /ja landing page + hreflang + 特商法 page to match the already-localized product. |
||||||||||
| 06 | Formbricksformbricks.com | Surveys / Experience | ○ | ○ | ◐ | ○ | ○ | 10 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ English-only site, no /ja route. JP copy ◐ Product ships a Japanese UI (apps/web/locales/ja-JP.json), v4.0 ja support announced. hreflang ○ No hreflang ja. JPY ○ USD pricing. Gap. In-product Japanese exists, but the commercial site is English-only with no 特商法 and no JP search presence. If you fixed it. JP landing page + hreflang + 特商法 page. |
||||||||||
| 07 | Logtologto.io | Auth / Authz | ○ | ○ | ◐ | ○ | ○ | 10 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page; USD pricing on logto.io. JP site ○ logto.io English-only; no /ja route. JP copy ◐ Product ships a bundled ja UI locale (packages/phrases/src/locales/ja), a peer of en — but the marketing site has zero Japanese. hreflang ○ No hreflang ja. JPY ○ USD pricing. Gap. Solid in-product Japanese UI, but the buying surface (site, pricing, legal) is entirely English — JP buyers never see the localized product before procurement stalls. If you fixed it. Stand up a /ja landing page + hreflang + 特商法; the product is already JP-capable, only the front door isn't. |
||||||||||
| 08 | ToolJettooljet.com | Low-code / Internal tools | ○ | ○ | ◐ | ○ | ○ | 10 | CLOSED | ▸ |
|
特商法 ○ /tokushoho and /legal/tokushoho both 404; footer = Privacy/Terms only. JP site ○ /ja, /jp, /ja-jp, /japan all HTTP 404; <html lang="en">. JP copy ◐ Product UI can now display Japanese via a community ja.json PR (all 822 keys), but the marketing site has no Japanese. hreflang ○ No hreflang/alternate ja in head. JPY ○ USD only: $0 / $79 / $199 per builder/mo; Enterprise from $3,000/mo; no ¥. Gap. The builder UI is now Japanese-capable, but the commercial surface is English-only with no JPY and no 特商法 — JP buyers still stall before procurement. If you fixed it. A /ja landing page + hreflang + 特商法 + JPY reference to match the now-localizable product. |
||||||||||
| 09 | Umamiumami.is | Privacy analytics | ○ | ○ | ◐ | ○ | ○ | 10 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ umami.is English-only, no /ja route. JP copy ◐ Product ships and maintains a Japanese UI (public/intl/language/ja-JP.json). hreflang ○ No hreflang ja. JPY ○ USD pricing. Gap. Dashboard is fully Japanese-capable and actively maintained, yet the site is English-only with no JP discoverability. If you fixed it. Localized landing page + hreflang + 特商法 to surface the JP-ready product to JP search. |
||||||||||
| 10 | Algoliaalgolia.com | Search API | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ algolia.com/ja = HTTP 404; <html lang="en">. JP copy ○ Language switcher offers English/Deutsch/français/Brazilian Portuguese/Spanish/Italian — Japanese is NOT offered. hreflang ○ 3 hreflang tags present but none is ja (EN/DE/FR confirmed, no ja). JPY ○ USD pricing; no ¥. Gap. Notably, Algolia DID localize — to European languages and Brazilian Portuguese — but deliberately skipped Japanese. The infrastructure exists; Japan was simply not prioritized. If you fixed it. Add ja to the existing language switcher + hreflang ja + a JP 特商法 page + JPY. The hardest part (i18n infra) is already built. |
||||||||||
| 11 | Appsmithappsmith.com | Low-code / Internal tools | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 notice on the site. JP site ○ www.appsmith.com/ja = HTTP 404; <html lang="en">; no switcher. JP copy ○ No Japanese content; the editor has no i18n layer (1,310 hardcoded English TS string constants, no i18n library in client deps). hreflang ○ 0 hreflang tags in homepage HTML. JPY ○ USD only ($0/$15/$22 tiers); no ¥/JPY/€. Gap. Zero JP localization at both layers, and the editor lacks any i18n foundation (open issue #4404 since 2021, de-prioritized). JP-readiness here is an i18n-infra + GTM project, not a drop-in fix. If you fixed it. GTM surface (特商法 + /ja + hreflang + JPY) is the quick layer; product Japanese requires building the i18n foundation first. |
||||||||||
| 12 | BrowserStackbrowserstack.com | Testing / QA | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ browserstack.com/ja and /guide/ja both HTTP 404; <html lang="en-US">; no clean /ja site. JP copy ○ No localized Japanese marketing site. hreflang ○ 0 hreflang tags in homepage HTML. JPY ○ USD pricing; no ¥. Gap. No clean Japanese site path; the front door is English/USD with no 特商法. If you fixed it. 特商法 + a real /ja site + hreflang + JPY. |
||||||||||
| 13 | Clerkclerk.com | Auth / Identity | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page; footer = Pricing/Docs/Blog/Changelog. JP site ○ clerk.com/ja = HTTP 404; <html lang="en">; no switcher. JP copy ○ No Japanese text on the site. hreflang ○ 0 hreflang tags in homepage HTML. JPY ○ USD only: Free, $25/mo Pro, $300/mo Business, etc.; no ¥. Gap. Popular auth choice for JP indie/startup stacks, but the entire surface is English/USD with no JP entry point. If you fixed it. 特商法 page + /ja landing + hreflang + JPY reference; a bundled ja for the prebuilt auth components would also help. |
||||||||||
| 14 | Contentfulcontentful.com | Headless CMS | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ contentful.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD only: $0/forever, $300/month; no ¥. Gap. English/USD-only; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 15 | Directusdirectus.io | Headless CMS / Data platform | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ directus.io (→directus.com) /ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content on the marketing site. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. English/USD-only marketing surface; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 16 | Dopplerdoppler.com | Secrets management | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ doppler.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. English/USD-only; no JP entry point. As with Infisical, JP copy for a secrets tool needs security-literate native review. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 17 | Flagsmithflagsmith.com | Feature flags | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 notice. JP site ○ <html lang="en">; no /ja path or switcher in markup. JP copy ○ No Japanese content; no i18n layer in the React frontend (no translation lib, hardcoded English JSX across ~160 of 671 components). hreflang ○ No hreflang tags in HTML. JPY ○ USD: $7/$50/$60 per month (one stray £); no ¥. Gap. Same as Unleash — real JP feature-flag demand, but no product i18n and no JP marketing surface. If you fixed it. Product i18n foundation + ja; site 特商法 + /ja + hreflang + JPY. |
||||||||||
| 18 | Fly.iofly.io | Hosting / PaaS | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ fly.io/ja = HTTP 404; <html lang="en-US">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. English/USD-only; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 19 | Hasurahasura.io | GraphQL / API | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ hasura.io/ja = HTTP 404; <html lang="en-US">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. English/USD-only; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 20 | Infisicalinfisical.com | Secrets management | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ Footer = Terms/Privacy/Subprocessors/SLA — no 特商法 page. JP site ○ infisical.com/ja returns HTTP 404; docs English-only; no switcher. JP copy ○ No Japanese text on the site. hreflang ○ No hreflang on top page or docs. JPY ○ USD only ($0/mo, $18/mo); no currency switcher. Gap. Has JP developer awareness (Qiita/Zenn writeups) but no localized surface. For a secrets tool, future JP copy must be security-literate native review, not raw MT — a mistranslated scope/rotation instruction is a security incident. If you fixed it. A /legal/tokushoho page, a /ja landing + top-10 docs, hreflang ja, and a JPY reference price. |
||||||||||
| 21 | Inngestinngest.com | Workflow / Background jobs | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ Footer = /privacy, /terms, /security only — no 特商法. JP site ○ inngest.com/ja and /ja/docs both HTTP 404; docs English-only, no switcher. JP copy ○ No Japanese copy on the site. hreflang ○ No hreflang ja. JPY ○ USD: Hobby $0/mo, Pro from $75/mo; no JPY; no 消費税 line. Gap. Durable-execution is conceptual — adoption hinges on docs readability. English-only docs leak the very JP evaluators Inngest already attracts on Zenn/Qiita; the dev gets interested, then loses the thread translating concurrency semantics under deadline. If you fixed it. 特商法 page, /ja landing + Quick Start, hreflang, JPY + 消費税 line, and translate the 5-10 highest-traffic docs pages first. |
||||||||||
| 22 | Linearlinear.app | Project management | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ linear.app/ja = HTTP 200 but renders an English 'Loading…' SPA shell (0 Japanese chars) — not a localized page. JP copy ○ No rendered Japanese marketing copy. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. Like Vercel, /ja is an English SPA shell, not real localization. The front door is closed despite the route returning 200. If you fixed it. A genuinely localized /ja landing + hreflang + 特商法 + JPY. |
||||||||||
| 23 | Muxmux.com | Video API | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ mux.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. English/USD-only; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 24 | n8nn8n.io | Workflow automation | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ n8n.io/ja 301-redirects to /ja/ which returns HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. A /ja redirect exists but lands on 404 — no real localization. English-only surface. If you fixed it. 特商法 + a real /ja landing + hreflang + JPY. |
||||||||||
| 25 | Neonneon.com | Database (serverless Postgres) | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ neon.com/ja = HTTP 404 (neon.tech 308-redirects to neon.com); <html lang="en">. JP copy ○ No Japanese content or switcher. hreflang ○ 0 hreflang tags. JPY ○ USD only: $0/month, $0.106/CU-hour, etc.; no ¥. Gap. Serverless Postgres is a natural fit for JP SaaS, but the site is fully English/USD with no JP route. If you fixed it. 特商法 + /ja landing + hreflang + JPY toggle. |
||||||||||
| 26 | Novunovu.co | Notification infra | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ novu.co English-only; no /ja. JP copy ○ Dashboard/web app UI has no ja locale (content i18n is a feature, but the admin UI is English). hreflang ○ No hreflang ja. JPY ○ USD pricing. Gap. High-profile (39k+ stars) but the management UI and the whole marketing surface are English-only. If you fixed it. Dashboard ja locale; 特商法 + /ja + hreflang + JPY for the site. |
||||||||||
| 27 | PlanetScaleplanetscale.com | Database (MySQL) | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ planetscale.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content or switcher. hreflang ○ 0 hreflang tags. JPY ○ USD only: $5/mo, $15, $50/mo, $0.06/GB; no ¥. Gap. No Japanese surface at all; a JP buyer cannot evaluate or approve it without FX guesswork. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 28 | PostHogposthog.com | Product analytics | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ Footer = Terms/Privacy/DPA/SOC 2/HIPAA — no 特商法. JP site ○ posthog.com/ja = HTTP 404; no <html lang> found; no switcher. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ States 'All prices are in US Dollars (USD), excluding taxes.' No ¥. Gap. Explicitly USD-only and English-only; no JP surface. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 29 | Railwayrailway.com | Hosting / PaaS | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ railway.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. Popular with JP indie devs, but no localized surface and no 特商法. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 30 | Renderrender.com | Hosting / PaaS | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ render.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. English/USD-only; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 31 | Retoolretool.com | Low-code / Internal tools | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ retool.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD only: Builder $10/mo (annual), $50/mo (Business); no ¥. Gap. Strong internal-tools demand in JP enterprise, but English/USD-only with no 特商法. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 32 | Sanitysanity.io | Headless CMS | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ sanity.io/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD only: $0/forever, $15 per seat/month; no ¥. Gap. English/USD-only; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 33 | Sentrysentry.io | Observability / Error monitoring | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 link on the pricing page or footer. JP site ○ sentry.io/ja redirects to /auth/login/ja/ (an English login page with a ja locale param) — no Japanese marketing site. JP copy ○ No Japanese marketing copy; the /ja redirect lands on an English login (lang=en, 0 JP chars). hreflang ○ No hreflang ja in homepage HTML. JPY ○ USD only: $0, $26/mo, $80/mo; no ¥; no currency switcher. Gap. The /ja route is only a login-form locale, not a localized site. JP buyers see English/USD throughout with no 特商法. If you fixed it. 特商法 + a real /ja marketing landing + hreflang + JPY. |
||||||||||
| 34 | Supabasesupabase.com | BaaS (Postgres / auth / storage) | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ supabase.com/ja = HTTP 404 (308 trailing-slash then 404); <html lang="en">. JP copy ○ No Japanese content on the marketing site. hreflang ○ 0 hreflang tags. JPY ○ USD only: $0/$25/month tiers; no ¥. Gap. Huge JP developer mindshare, zero localized front door — JP traffic lands on an English/USD page with no 特商法. If you fixed it. 特商法 + /ja landing + hreflang + JPY; docs translation for the highest-traffic guides. |
||||||||||
| 35 | SuperTokenssupertokens.com | Auth | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ supertokens.com English-only; no /ja. JP copy ○ Auth UI has an i18n hook (translationFunc) but ships no bundled ja translation (only an example). hreflang ○ No hreflang ja. JPY ○ USD pricing. Gap. Auth UI in Japanese is often mandatory for JP adoption, yet no bundled ja locale ships and the site is English-only. If you fixed it. Ship a bundled ja login-UI locale; 特商法 + /ja + hreflang + JPY for the site. |
||||||||||
| 36 | Tursoturso.tech | Database (edge SQLite) | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ Footer lists Terms/Privacy/Trust/About/Contact/Support — no 特商法; /terms-of-use = CHISELSTRIKE INC., Delaware. JP site ○ turso.tech/ja and docs.turso.tech/ja both return HTTP 404; no language switcher. JP copy ○ No Japanese text anywhere on site or docs. hreflang ○ No hreflang ja. JPY ○ USD only: $0, $4.99/mo, $24.92/mo, $416.58/mo, $0.75/GB. No JPY, no toggle. Gap. Strong organic pull with Japanese indie/SaaS devs (libSQL/edge-SQLite), but every JP-facing surface is missing — the front door is fully closed at the procurement and finance gate. If you fixed it. One static 特商法 page + a /ja landing + translated quickstart + hreflang + a JPY display toggle. All footer/page-level, no product change. |
||||||||||
| 37 | Unleashgetunleash.io | Feature flags | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ getunleash.io <html lang="en">; no /ja; no switcher. JP copy ○ Dashboard English-only; no UI i18n framework (only date-fns date locales). hreflang ○ No hreflang ja. JPY ○ USD: $0/$79/$199. Gap. Feature-flag demand is solid among JP SaaS/enterprise, but the product is English-only and the site has zero JP presence. If you fixed it. Add a UI i18n layer + ja for the product; 特商法 + /ja + hreflang + JPY for the site. |
||||||||||
| 38 | Upstashupstash.com | Database (serverless Redis/Kafka) | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ upstash.com/ja = HTTP 404; <html lang="en">. JP copy ○ No Japanese content. hreflang ○ 0 hreflang tags. JPY ○ USD pricing; no ¥. Gap. English/USD-only; no JP entry point. If you fixed it. 特商法 + /ja + hreflang + JPY. |
||||||||||
| 39 | Vercelvercel.com | Hosting / Frontend cloud | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ vercel.com/ja = HTTP 200 but is an English dashboard SPA shell (<html lang="en-US">, 0 Japanese chars) — a locale param, not a localized site. JP copy ○ No rendered Japanese marketing copy. hreflang ○ 0 hreflang tags in homepage HTML. JPY ○ USD pricing; no ¥. Gap. The /ja route exists but serves English — a textbook 'looks localized, isn't' case. No real Japanese marketing site, no 特商法, no JPY. If you fixed it. Turn /ja into a real localized landing page (not an English shell) + hreflang + 特商法 + JPY. |
||||||||||
| 40 | Windmillwindmill.dev | Developer platform / Workflow | ○ | ○ | ○ | ○ | ○ | 0 | CLOSED | ▸ |
|
特商法 ○ No 特商法 page. JP site ○ windmill.dev English-only; no /ja. JP copy ○ Product UI (Svelte) has no i18n layer; English-only. hreflang ○ No hreflang ja. JPY ○ USD pricing. Gap. Workflow/automation has JP developer demand, but neither product nor site offers Japanese. If you fixed it. UI i18n foundation + ja; site 特商法 + /ja + hreflang + JPY. |
||||||||||
Click any row for the per-signal evidence, the gap, and the one-line fix. Tiers: 70–100 JP-ready · 30–69 partial · 0–29 closed. No tool reached the top tier.
| 25 | 特商法 page (Specified Commercial Transactions Act) | Legally expected for any paid online service sold in Japan. Its absence is a hard stop for many corporate procurement / legal teams — the deal dies before engineering is ever evaluated. |
| 25 | Localized Japanese site / /ja route | A real Japanese-language entry point. Scored on rendered Japanese marketing copy, not on a route merely existing — an English SPA shell served at /ja scores zero. |
| 20 | Japanese content / language switcher | Any genuine Japanese copy or a switcher that offers Japanese. Partial credit for token Japanese; zero for none. |
| 15 | hreflang="ja" alternate | Without it, Japanese-language search traffic never lands on a localized page — invisible in JP Google results. |
| 15 | JPY pricing / currency | USD-only forces JP finance to FX-convert and absorb forex fees, and gives them no clean number to approve. A JPY display toggle is enough; billing can stay USD. |
Every signal below was checked live against each company's own public marketing site on 2026-06-25 using direct HTTP requests (status codes, HTML lang, hreflang) and rendered-page reads (Japanese copy, pricing currency). No estimates. Scores are reproducible from the evidence column. Sites are the property of their respective owners; this report quotes only publicly observable facts. A 200 on /ja that resolves to an English SPA shell or a login page (Vercel, Linear, Sentry) is not counted as localization — this index scores rendered Japanese copy, not the mere existence of a route. Where a check couldn't be confirmed it is marked ? and scored as a fail, not guessed up.