Is Trigger.dev ready for the Japanese market?
— a Tokyo native's gap map

The Trigger.dev application has no Japanese locale. A community contributor submitted a pull request adding a Japanese project overview document (PR #2200 — closed without merge), and at least 7 Zenn articles in Japanese explain how to use Trigger.dev. The product team has not acted on either signal.

github.com/triggerdotdev/trigger.dev/pull/2200 — JP community doc PR (closed) zenn.dev — 「Next.jsのバックグラウンドジョブをTrigger.devで実装してみた」

When JP developers arrive at trigger.dev after reading a Zenn tutorial, they find an English-only product and no indication the team knows they exist. The funnel converts organically generated JP interest into zero Japanese revenue, because there is no Japanese surface to land on.

A Japanese UI locale and a Japanese landing page. The community has already demonstrated intent by writing the docs — Trigger.dev would only need to build the container for that energy to live in.

The trigger.dev/legal page exists but contains only a standard Privacy Policy and Terms of Service. No 特商法に基づく表記 disclosure is present.

trigger.dev/legal (footer links checked)

A Japanese engineering team evaluating a background jobs platform for production use will want sign-off from their procurement or legal department before paying. The 特商法 page is the standard gatekeeping document Japanese companies look for. Without it, Trigger.dev reads as a foreign service that hasn't set up for the Japanese market — which creates friction specifically at the moment a team is ready to commit budget.

A 特商法に基づく表記 page with: operator name, contact address, pricing, payment timing, cancellation policy. It is a template document, not a build. Takes a day to produce.

Pricing shows Hobby at $10/month and Pro starting at $20/month, billed in USD. There is no JPY display, no currency selector, and no JPY-denominated payment option.

trigger.dev/pricing

Trigger.dev is a developer tool that teams expense, not a personal purchase. A recurring USD charge on a Japanese company card means: exchange rate risk every month, a foreign-currency line on an expense report, and accounting complexity for the finance team. For developer tools with a monthly subscription, JPY display removes the last friction before a team signs up.

JPY pricing display alongside USD. For larger team contracts, a JPY-denominated invoice option. Both are configuration-level changes in most billing platforms.

A search for 「バックグラウンドジョブ SaaS」 or 「Next.js バックグラウンドタスク」 returns no trigger.dev pages because there are none in Japanese. The traffic Trigger could capture from its own Zenn community flows only to Zenn, not to trigger.dev.

The Zenn articles about Trigger.dev represent genuine, earned Japanese developer attention. None of that attention has a path from reading → evaluation → paying, because there is no JP-language landing page for the product. Discovery and conversion are disconnected.

A Japanese developer landing page (even one page, even translated from English) gives those Zenn readers somewhere to arrive at when they want to go deeper. It also means the Zenn articles start linking to something official rather than the English site.

trigger.dev renders entirely in English, including all marketing pages, pricing, and documentation. No language switcher is present anywhere in the funnel.

trigger.dev (site-wide lang="en" confirmed)

For a developer tool in a Japanese team, the person who evaluates it is likely a senior engineer who reads English, but the decision to purchase or block involves their manager and procurement. When the entire reference surface is English, those non-engineer stakeholders have no accessible documentation of what the product is. The evaluation stalls in translation.

A Japanese overview page for non-technical stakeholders — what the product does, pricing, and a contact point. Not full docs, just enough for the person who approves the purchase to understand what they're approving.