LangSync · AI localization

Ship in every language. Let AI do the translating

Manage all your translation strings in one place. AI translates them with context, glossary awareness, and your custom tone — then export as i18n JSON via API.

AI-powered translations 100+ languages Glossary & custom prompts i18n JSON export via API CLI for your terminal Free tier included
ai translation waterfall key → ai → 6 locales
checkout.order_shipped
en-US
es-ES
fr-FR
de-DE
ja-JP
ar-SA
01 ai translation

Translate your entire product in minutes.

Add your terms, select target languages, and let the AI translate everything — with glossary awareness and your custom tone. Review, adjust, and export. That's it.

  • Batch translate all missing translations in one click
  • Context-aware — uses term keys, descriptions, and glossary
  • Custom prompts for tone, formality, and domain context
Try LangSync free
ai translation waterfall key → ai → 6 locales
checkout.order_shipped
en-US
es-ES
fr-FR
de-DE
ja-JP
ar-SA
02 glossary

Consistent terminology, every language, every time.

Define your brand terms, technical vocabulary, and domain-specific language once. The glossary feeds directly into every AI translation — ensuring consistency across all languages and all team members.

  • Type categorization — brand, UI, technical, billing
  • Translatability flags — keep brand names as-is
  • Auto-included in every AI translation prompt
Try LangSync free
glossary-aware translation → es
billing.upgrade_cta
Upgrade your Norcube plan to access the Dashboard and manage Webhooks.
Norcube keep Dashboard translate Webhooks keep
Translation will appear here…
03 api & export

From dashboard to production in one API call.

Generate API keys and pull translations as i18n-ready JSON files. Plug it into your CI/CD pipeline so every deploy ships with the latest translations — no manual export, no stale strings.

  • REST API with API key authentication
  • i18n JSON format — drop into any frontend framework
  • Automate exports in your build pipeline
See API docs
api export GET /api/v1/terms
en-US
100% ·
es-ES
100% ·
de-DE
98% ·
ja-JP
93% ·
fr-FR
100% ·
pt-BR
90% ·
04 cli

Translations from your terminal.

The norcube CLI keeps your local i18n JSON files in sync with the LangSync dashboard, fills the gaps with AI, and writes the result back. One command per repo, one install for the whole team — no more copy-pasting between your editor and a web app.

  • Two-way sync with one command
  • Write in your language, AI translates the rest
  • Resumable jobs survive backend restarts
Read the CLI guide
ai translation waterfall key → ai → 6 locales
checkout.order_shipped
en-US
es-ES
fr-FR
de-DE
ja-JP
ar-SA
Who it's for

Built for teams that ship products globally

Dev teams · Product teams · Startups

SaaS products

Manage all your UI strings in namespaces, translate with AI, and pull the latest translations into your build via API. Ship new languages in hours, not weeks.

Agencies · Freelancers · Consultancies

Agencies & multi-client

One namespace per client project. Separate glossaries, separate languages, separate progress tracking. Manage dozens of localization projects from one account.

Growth teams · Market entry · Localization leads

Global expansion

Entering a new market? Add target languages, let AI translate your entire product, review with native speakers, and launch — in days, not months.

iOS · Android · React Native · Flutter

Mobile apps

Manage all your mobile app strings in one place. Export as JSON via API and integrate into your build pipeline — ship localized updates without manual file wrangling.

Shopify · WooCommerce · Custom stores

E-commerce & marketplaces

Translate product descriptions, checkout flows, and transactional emails across all your target markets. Glossaries keep brand and product names consistent.

Maintainers · Contributors · Communities

Open source projects

Manage community translations with namespace-level access control. Contributors work on their language, you keep full oversight. Export as i18n JSON for any framework.

What it does

Everything you need to go multilingual

04

100+ languages

IETF BCP 47 standard with support for country-specific variants like en-US, pt-BR, and zh-TW. Add custom languages per organization.

05

POEditor migration

Import your existing projects from POEditor in one click. All terms, languages, and translations migrate automatically — no manual re-entry.

06

Team collaboration

Manage namespace-level access with roles and permissions. Invite contributors for specific languages. API keys for third-party integrations.

our promise

Fair pricing, no surprises

We built LangSync the way we'd want a localization tool to work. These are the rules we follow — no exceptions.

principle 01

Empty translations are free

You only pay for strings that actually have content. Untranslated terms don't count toward your usage — ever.

principle 02

No per-seat pricing

Invite your whole team. Contributors, translators, developers — everyone. We charge for strings stored, not people added.

principle 03

No vendor lock-in

Export everything via API at any time. Your translations are yours. Cancel and take your data — we make it easy, not painful.

Pricing

Pay per string stored. Volume discounts built in

Your first 1,000 strings are free — forever. After that, pricing scales down automatically as you grow. No per-language multiplier, no seat fees.

Free tier: 1,000 strings

A "string" is one term key plus each of its translations. For example, one term translated into 5 languages = 6 strings (1 key + 5 translations). Only non-empty translations count. Pricing is based on the total across all namespaces.

Strings storage — Per-string monthly storage. Volume discounts applied automatically.
First 1,000 Free
1,001 – 10,000 $1.25 / 1K strings
10,001 – 50,000 $1.00 / 1K strings
50,001 – 150,000 $0.80 / 1K strings
150,001 – 500,000 $0.65 / 1K strings
500,001 – 1,000,000 $0.55 / 1K strings
1,000,001 – 2,500,000 $0.50 / 1K strings
Over 2,500,000 $0.45 / 1K strings
Common questions

Questions, answered

Quick answers to what teams ask us most about LangSync. Need something else? Email [email protected].

Which languages does LangSync support?
Any language the underlying AI model speaks — we do not maintain a fixed list. In practice that covers all major world languages plus most regional and minority ones. If a model can translate it, LangSync can manage it.
Can I bring my own glossary or translation memory?
Yes. Terms and glossaries are first-class — you define source terms, target translations per language, and optional notes. The AI uses them on every translation so brand-specific terminology stays consistent across your product.
How does LangSync handle context for translations?
You write a custom prompt in plain language — tone, audience, formality, product-specific rules, anything else the AI should know. Every translation sees the source string, your glossary, and your prompt together, so output matches your voice rather than generic machine translation. Prompts can be personal or shared with your whole organization.
How do I move translations in and out of LangSync?
Import existing translations via CSV, JSON, or XLSX — optionally auto-translate everything during import, so a single upload bootstraps the whole product. Export as i18n JSON over a REST API: pull at build time, fetch at runtime, or use the norcube CLI to keep your local i18n files in sync with the dashboard.
Do you store or train on our content?
Your strings are stored so you can edit, version, and re-export them — that is the product. They are never used to train models. All data is encrypted in transit and at rest, processed in the EU under GDPR.
How does pricing work?
There is a free tier so you can start without a credit card. Above that, you pay per 1,000 translated strings, with the price dropping at higher volumes. See the pricing table above for the full schedule.
Quickstart

Translate your first project in under five minutes

Five steps, the last two for shipping to production. No SDK install, no schema migration, no language ENUM updates — just glossary, prompt, and JSON.

About 5 min
  1. Create a namespace

    A namespace is one isolated translation workspace — one per app, module, or client project. Pick a source language and the target languages you want to ship in.

  2. Add your terms

    Type them in, paste from clipboard, or bulk-import from CSV, JSON, or XLSX. Imports can auto-translate every missing language at once, so a single upload bootstraps the whole product.

  3. Define glossary entries (optional, recommended)

    Lock down brand names, technical vocab, and anything where a literal translation breaks meaning. The glossary is injected into every AI translation prompt, so terminology stays consistent across languages and across team members.

  4. Translate

    Run AI translation across all missing strings with a single click, or edit translations manually in the dashboard. Custom prompts (tone, audience, formality) can be personal or shared organization-wide.

  5. Get an API key and export

    Generate an API key in the dashboard, then fetch translations as i18n JSON. Pull at build time from your CI, fetch at runtime for hot reloads, or wire the norcube CLI to keep local i18n files in sync with the dashboard.

Ready when you are

Start translating in 60 seconds

Free tier included. No credit card required. Add your first terms and let AI do the rest.

Free tier Get started at no cost
No credit card Start building now
100+ languages IETF BCP 47 standard
API-first i18n JSON export
// tick. tick. tick.
0 ticks since founding