August 2026 · Platform

One platform, twenty languages

A product that builds for a global audience should speak to one. The dashboard and the marketing pages run in twenty languages — switch with the globe icon in the top navigation, and the interface re-renders in place, no page reload.

20languages
3,800+interface strings each
1registry driving it all

How it stays consistent

Every language lives in a single registry — code, native name, browser prefixes, text direction — consumed by both the backend and the frontend, so adding a language is one registry entry plus a generation run. English and Chinese are hand-maintained inline; the other eighteen catalogs are generated by pipeline and regenerate whenever new interface strings land, so a new feature ships translated rather than accumulating an English backlog.

Enum values from the database (statuses, triggers, agent names) are localized at the render edge with English fallback — a new status added tomorrow renders in English until its key lands, never as a raw identifier.

The agents follow your language

Interface translation is half the story. The AI assistant, the build chat, and the agent teams reply in whatever language you write to them — describe your app in Japanese and the plan comes back in Japanese. SEO reports can be produced in your tenant language too, so the loop's output reads natively end to end.

What stays English for now: long-form legal pages (Terms, Privacy, Refunds) and this blog — precision matters more than reach there. The footer chrome around them translates like everything else.
← All posts