Code owns the source
Source strings live in your repository and are pushed up. Translations stay with the people who write them.
Push source strings from your repository, translate them with your team in one workbench, and serve every language to your app through a small SDK.
| Key | English | German |
|---|---|---|
| home.hero.title | Welcome back | Willkommen zurückTranslated |
| cart.checkout-button | Go to checkout | Zur KasseTranslated |
| cart.total-label | Total incl. tax | Gesamt inkl. MwSt.Outdated |
| orders.empty-text | No orders yet | —Missing |
Source strings live in your repository and are pushed up. Translations stay with the people who write them.
Change a source string and its translations are flagged for review — the old text keeps being served until someone updates it.
A CLI for CI, a typed SDK with an in-memory cache, and bindings for React and Next.js.
The whole loop, from your repository to your users. Each step takes a few minutes.
Add the languages you ship and mark the one you write in as the source. Invite your team with a join code.
Create a write key in the project settings. The CLI finds every key your code uses and pushes the source strings.
$ npx nck-translation sync ./locales
$ npx nck-translation push ./locales/en.json --language enYour team fills in each language in the workbench. When a source string changes, its translations are marked outdated until someone reviews them.
Your app reads catalogs through the SDK, with bindings for React and Next.js. Catalogs are cached and requests de-duplicated.
const t = await client.getTranslator("de");
t("home.hero.title");Sign in or create an account, set up your first project and push your first catalog.
Start