Meet LangSync: the zero-ops alternative to Tolgee
Pay only for the strings you store, with no word tiers to jump between. One CLI command keeps your repo in sync, your existing i18n library stays as it is, and there is no server to run.
Verified October 28, 2026 against the public sources listed with this comparison. Spot an inaccuracy? Email [email protected] and we'll update it within two business days.
LangSync vs Tolgee, feature by feature
Checked on October 28, 2026 against Tolgee's pricing page, documentation, information security policy and its GitHub repositories. Tolgee comes as free open-source self-hosting, Tolgee Cloud, and a paid self-hosted license, and we say which one a row is about.
Pricing model4
Billing shape
Entry price
Seats / users
Sales call to buy
Translation engine8
AI translation
Custom prompts
Labeling AI output
Machine translation engines
Glossary
Translation memory
Source language
cs.json as the source while the namespace default stays English. See the workflow.In-context editing
Developer workflow5
CLI
nrc langsync sync: one two-way command that pushes local changes, auto-translates and writes the files back. See the CLI page.push and pull commands, plus extract to find keys in your source code.Key extraction
tolgee extract check scans your code and can fail CI when keys in the code are missing from Tolgee.Runtime SDKs
Over-the-air updates
MCP server
File formats & integrations3
File formats
Integrations
nrc langsync pull or sync in the pipeline.Webhooks
Tolgee-Signature header) for project events.Team & translation3
Professional translators
Branches
Roles
Security, hosting, data7
Where data lives
Self-hosting
ee directory need a paid license.Data processing agreement
Certifications
AI training on your content
Single sign-on
Backups
Migration & lock-in3
Moving in
tolgee pull your files as JSON, then nrc langsync sync or a CSV import.History
API credentials
| Section | Feature | Tolgee | |
|---|---|---|---|
| Pricing model | Billing shape | Pay-as-you-go: billed per 1,000 stored strings (a key plus each filled translation), cheaper per thousand as you grow. No plans, no tiers. | Tolgee Cloud plans priced by hosted words: every word of the base text and of each translation. Tiers run from 50,000 to 10M words; crossing a tier moves you to the next one at the end of the month, with no pay-as-you-go overage. MT and AI usage is metered in MT credits. |
| Entry price | First 1,000 strings free, no credit card. Then from $1.25 down to $0.45 per 1,000 strings. | A Free cloud plan (30,000 words, 3 seats). At the 50,000-word tier, billed annually: Translate $66/mo, Optimise $149/mo, Manage $416/mo. Enterprise is quoted. Self-hosting the open-source core is free. | |
| Seats / users | No seat charges. Invite as many people as you need. | Unlimited seats on current paid plans. Older plans kept seat limits. | |
| Sales call to buy | No. Sign up and start. | Cloud plans are self-serve. Enterprise and the self-hosted license go through sales. | |
| Translation engine | AI translation | An LLM (OpenAI GPT-4.1) translates every string with your glossary and your prompt in the request. | Tolgee AI Translator uses Anthropic Claude and OpenAI models on Tolgee Cloud, or your own Azure OpenAI, Anthropic, Gemini or any OpenAI-compatible API. It adds context from screenshots, key descriptions, the project description and translation memory. |
| Custom prompts | Yes. Private or shared prompts, a default prompt per namespace, and a prompt per API request. | Yes. AI customization takes a custom prompt, a project description and per-language notes; the AI Playground lets you test prompts. | |
| Labeling AI output | Every AI-written translation carries an AI label until a person edits it. | We found no label in Tolgee's docs that marks a saved translation as AI-written. | |
| Machine translation engines | LLM translation only. No classic MT engines. | Google Translate, DeepL and AWS Translate alongside the AI Translator. Self-hosters can use their own keys. | |
| Glossary | Organization-wide. Translations per language, a part of speech and a don't-translate flag. Sent with every AI translation. | Glossaries with flags for non-translatable, case-sensitive, abbreviation and forbidden terms, CSV import and export, used by the AI Translator. | |
| Translation memory | None. The AI works from your glossary and your prompt. | Yes, with suggestions in the editor and TMX import and export. | |
| Source language | Per developer: someone who writes Czech keeps cs.json as the source while the namespace default stays English. See the workflow. | One base language per project. | |
| In-context editing | No. LangSync works at build time. | Tolgee's signature feature. Alt-click a string in your running app to edit it, through the Tolgee SDK's dev tools or the Chrome and Firefox extension. | |
| Developer workflow | CLI | nrc langsync sync: one two-way command that pushes local changes, auto-translates and writes the files back. See the CLI page. | Tolgee CLI (TypeScript) with separate push and pull commands, plus extract to find keys in your source code. |
| Key extraction | Not built in. Keys come from your i18n files. | tolgee extract check scans your code and can fail CI when keys in the code are missing from Tolgee. | |
| Runtime SDKs | None needed. Keep your i18n library (i18next, react-intl, FormatJS and others) and point it at the JSON files. | SDKs for JavaScript, React, Vue, Svelte, Angular and i18next, plus native iOS (Swift), Android (Kotlin), Flutter and Unreal Engine SDKs. | |
| Over-the-air updates | No. LangSync works at build time. | Content Delivery publishes translation files to a CDN or your own S3 or Azure Blob storage; apps load updates without a release. | |
| MCP server | Not for LangSync. The Norcube MCP server covers Backup and DomainRadar. | Yes, an official Tolgee MCP server for Claude, Cursor and other clients. | |
| File formats & integrations | File formats | Flat i18n JSON through the CLI; CSV import in the dashboard. | JSON, YAML, XLIFF, Apple strings, Android XML, Flutter ARB, PO, properties, RESX, CSV, XLSX and more. |
| Integrations | Your CI and git host: run nrc langsync pull or sync in the pipeline. | A Figma plugin, browser extensions, Slack notifications, an n8n node and the MCP server. Git hosts connect through the CLI in CI. | |
| Webhooks | No webhooks. CI pulls translations with the CLI. | Signed webhooks (a Tolgee-Signature header) for project events. | |
| Team & translation | Professional translators | Not built in. AI translates, people review and edit. | Order translation from agencies through Tasks. |
| Branches | Your Git branches; the CLI syncs whatever you have checked out. | Branching in projects, with its own permissions. | |
| Roles | Organization roles and access policies; private or shared prompts. | Project roles plus advanced granular permissions. | |
| Security, hosting, data | Where data lives | AWS Frankfurt, on every account. Text sent for AI translation is processed by OpenAI in the US under SCCs. See /subprocessors/. | Tolgee Cloud runs on Microsoft Azure and AWS with EU and US data centers. Self-hosting puts the data wherever you run it. |
| Self-hosting | No. LangSync is a hosted service only. | Yes, and it's Tolgee's biggest difference. The core is Apache 2.0 and free to self-host; enterprise features in the ee directory need a paid license. | |
| Data processing agreement | Published at /dpa/. | Available on request for enterprise customers. | |
| Certifications | No third-party certification yet. GDPR, EU storage, encryption at rest. | ISO 27001 and GDPR. | |
| AI training on your content | Never. We don't train models, and OpenAI doesn't use API data for training. | Tolgee says it doesn't use customer data to train AI models and picks LLM providers that don't train on API data. | |
| Single sign-on | Not yet. It's on the roadmap. | OpenID Connect SSO on Enterprise; self-hosted SSO needs the paid license. | |
| Backups | Encrypted, automated backups of the LangSync database in AWS. | Tolgee Cloud keeps continuous backups for at least 7 days; self-hosters run their own. | |
| Migration & lock-in | Moving in | Built-in POEditor importer. From Tolgee: tolgee pull your files as JSON, then nrc langsync sync or a CSV import. | File imports in many formats, plus TMX into translation memory. |
| History | Current values plus the dashboard audit log. Per-translation history isn't captured yet; it's on the roadmap. | Per-translation history through the API. | |
| API credentials | Organization API keys for the read-only API, revocable any time. | Project API keys and personal access tokens with scopes. |
Verified October 28, 2026 against the public sources listed with this comparison. Spot an inaccuracy? Email [email protected] and we'll update it within two business days.
Sources (checked October 28, 2026): pricing, information security policy, AI Translator, SSO, MCP server, webhooks, TMX import, license, Tolgee on GitHub. Spot something out of date? Email [email protected].
When Tolgee is the right call
Tolgee fills a different slot: open source you can host yourself, with a runtime SDK ecosystem. If any of these describe your team, Tolgee is the better choice today.
You want to run it on your own servers
Tolgee's Apache 2.0 core is free to self-host, which beats any SaaS on price, LangSync included, if you're happy to run the database, upgrades and backups yourself. LangSync is hosted only.
Translators should edit inside your running app
Alt-click in-context editing is Tolgee's signature feature, and the browser extension brings it to production for non-developers. LangSync works at build time only.
You want a first-class i18n SDK
Tolgee ships SDKs for React, Vue, Svelte, Angular, i18next, iOS, Android, Flutter and Unreal, with screenshots and in-context editing built in. LangSync deliberately has no runtime SDK.
You want CI to catch untracked keys
tolgee extract check scans your code and fails the build when a key in the code is missing from Tolgee. LangSync reads keys from your i18n files instead.
Your designers work in Figma
Tolgee's Figma plugin syncs keys with the platform and previews languages inside Figma. LangSync has no Figma integration.
You ship live translation updates
Content Delivery publishes translations to a CDN or your own bucket, so apps pick up fixes without a release. LangSync works at build time only.
Questions teams ask
How much will I save switching from Tolgee to LangSync?
Is LangSync's AI as good as Tolgee's AI Translator?
Tolgee is open source. Doesn't that beat LangSync on price?
ee directory) such as SSO need a paid license. LangSync is for teams that would rather not run localization infrastructure at all.What's different about where data lives?
How long does migrating from Tolgee take?
tolgee pull to get JSON files, point nrc langsync init at the folder, and run nrc langsync sync. Glossaries come across as CSV. Translation memory, screenshots and history have no LangSync equivalent, so they stay behind.What if I want to switch back to Tolgee?
nrc langsync pull writes every namespace as standard i18n JSON, which Tolgee imports natively. Your prompts are the only LangSync-specific piece, and they are plain text you can copy.Try LangSync in 60 seconds
First 1,000 strings free, no credit card, no sales call.
- Free tier
- EU storage
- No SDK
- No servers