Language Bridge

Open-source, self-hosted translation management for i18next. Store keys, let translators fill in values, and serve CDN-cached JSON with no frontend redeploy — on your own infrastructure, no per-seat pricing.

Why

Translation management should be simple: store keys, let translators fill in values, serve JSON to your frontend. Language Bridge does exactly that — self-hosted, open-source, and designed for speed. Your keys and translations live in your own database and storage, with no per-seat pricing and no vendor lock-in.

What it does

Receives missing keys

i18next's saveMissing sends new keys automatically as your app runs.

Translator interface

Non-technical translators fill in values through a web UI.

Serves translations

Public JSON endpoint with CDN caching, no frontend redeploy needed.

The pieces

This is a monorepo with two components:

App

Stores keys/translations, serves i18next JSON, web UI + API.

CLI

@language-bridge/cli — pulls translations and generates typed i18next resources.

Alternatives to

Language Bridge is a self-hosted, open-source alternative to hosted translation-management platforms:

Lokalise
Phrase
Crowdin
Locize
Tolgee

You get the same core workflow — missing-key capture, a translator UI, and CDN-served JSON — without per-seat pricing or vendor lock-in. Everything runs on your own infrastructure.

Generating types in a consumer app

npm i -D @language-bridge/cli

LB_TOKEN=lb_pat_… lb sync --project my-app --url https://your-server

This pulls the source locale and writes a typed resources.d.ts that augments i18next so t('ns:key') is autocompleted and interpolation params are typed. See the CLI docs.

License

MIT

Introduction