Translation & Localization
Tolgee
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Tolgee s.r.o. · tolgee.io
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Tolgee at a glance
- Vendor
- Tolgee s.r.o.
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Tolgee 3.5/5, the mean of 6 judges. Tolgee, an open-source localization platform from Tolgee s.r.o. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Tolgee, an open-source localization platform from Tolgee s.r.o. of Brno, is sold as a cloud service or self-hosted. Its strongest criterion is workflow and review, where scores cluster at 7: a translation memory with similarity suggestions shared across projects, Untranslated/Translated/Reviewed states, severity-configurable QA checks, assignable tasks, and in-context editing that works in production. Content confidentiality, portability and exit, and integrations and formats score 6-7, resting on an Apache 2.0-licensed core with documented self-hosting, export through the UI, CLI and REST API, and a wide software format list. Pricing transparency is the weakest criterion at 5-6: cloud prices are published — Free with 30,000 hosted words, 10,000 MT credits and 3 seats, then Translate €58/mo, Optimise €133/mo and Manage €373/mo billed annually — but the self-hosted licence is tailored and unpriced, Enterprise carries no public price, and judges found no public information on overage handling or extra credit costs. On content confidentiality and sovereignty, both 6-7, judges weighing the open-replay inspection clause and the on-request data processing agreement scored lower than those crediting the no-AI-training statement, named subprocessors and the self-hosted option.
Speaks for it
- Full review workflow documented, from translation-memory suggestions shared across projects to Reviewed states, severity-configurable QA checks and assignable tasks
- Platform core licensed under Apache 2.0, with self-hosting documented and export via UI, CLI and REST API
- Free self-hosted edition with unlimited keys and up to 10 seats, upgradeable to a licence without data loss
- Published cloud pricing, from a Free tier with 30,000 hosted words, 10,000 MT credits and 3 seats with no card required to word tiers from 50k to 10M in EUR or USD
- Stated policy that customer data is not used to train AI models, with machine-translation providers named and switchable off
Held against it
- Terms reserve the vendor's right to look into user projects via open-replay to improve UX and debug
- Data processing agreement available only on request and only to enterprise customers
- No published price for the self-hosted licence, based on keys and seats, or for the Enterprise plan
- We found no public information on overage handling or the cost of machine-translation credits beyond the free 10,000
- We found no public information on CMS or shop connectors, Git repository sync, or layout-preserving document translation for Word, PDF or InDesign
Best for
- You build web or mobile apps with React, Angular, Vue, Svelte or Next.js and want in-context editing plus worldwide content delivery without rebuilding the app
- You must keep localization content on your own servers — the documented self-hosted edition states the vendor sees no projects, users or logs
- Your team runs a review cycle with tasks, QA checks and a translation memory shared across projects
- You want machine-translation flexibility: five named engines configurable per language, and bring-your-own API keys when self-hosted
Avoid if
- Your content is Word, PDF or InDesign documents rather than software strings — the documented formats cover software and tabular files, and we found no public information on layout-preserving document translation
- You run a shop or CMS and rely on connectors — the captured integrations pages list Figma, Slack and browser plugins alongside the SDKs, and we found no public information on shop or CMS connectors
- Your terms review cannot accept a clause under which the vendor looks into user projects via open-replay to improve UX and debug
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3 of 5 |
| Translation memory, terminology & review workflow | 3.5 of 5 |
| Integrations, file formats & developer tools | 3.5 of 5 |
| Confidentiality of translated content | 3.5 of 5 |
| Data export, portability & self-hosting | 3.5 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 3 of 5 |
Machine translation & AI quality
Show reasoningHide reasoning
How this is scored
What the machine translation does and how well it is controlled: the languages and language pairs covered, the engine (own neural or LLM model, or a choice of third-party engines such as DeepL, Google, Microsoft or an LLM), glossaries and formality applied during translation, document translation that keeps the layout (Word, PowerPoint, PDF, InDesign), custom or adaptive models trained on the customer's own translations, automatic quality estimation or scoring, and published evaluations of translation quality.
0 — No machine translation of any kind, and no way to connect an engine.
3 — Machine translation is offered or one engine can be connected; languages, glossary use and quality controls are basic or not described.
5 — Machine translation for the major European and world languages with the list published, glossaries applied during translation, a formality or tone setting, document translation that keeps formatting for common office formats, and either an own engine or a choice of several named engines.
8 — Custom or adaptive models that learn from the customer's translation memory or corrections, automatic quality estimation per segment with a threshold that routes weak segments to human review, LLM-based translation with style guides and context, engine selection per language pair stated, and a published quality evaluation with its method.
10 — Translation quality that an organisation can measure and steer: evaluations against named benchmarks or blind human review published with their method, quality estimation calibrated and explained, custom models with their training data and isolation documented, and every machine-translated segment traceable to the engine, model version and glossary that produced it.
The Localization Manager
Tolgee offers a choice of named engines — its own AI translator alongside AWS, DeepL, Google and Azure — with providers configurable per language, a formality setting, custom AI prompts, glossaries, and self-hosted lets us bring our own keys for engines and LLMs including self-hosted models, with machine translation switchable off. We found no published list of supported languages, no layout-preserving document translation for Office or InDesign formats, no custom models learning from our translation memory, and no quality estimation or published quality evaluation. 2 11 12 15
The App Developer
Five named engines plus any LLM provider including self-hosted ones, configured per language with a formality setting, custom prompt fragments, glossaries and automatic context extraction from my app — genuinely more control than I expected, and there's an AI playground to compare models on my own data. What I found no public information on: quality estimation that flags weak segments, adaptive models, any published evaluation of translation quality, or document translation that keeps layout — this is built for software strings, which suits me. 2 12 11 15
The In-House Document Translator
There is a real choice of engines — Tolgee's own AI translator plus DeepL, Google, AWS and Azure — configurable per language, with a formality setting, glossaries whose terms are highlighted in translations, and LLM translation I can steer through custom prompt fragments, project context, automatic context extraction and a playground for testing models on my own data. For contract and manual work, we found no public information on document translation that keeps Word or PDF layout, on automatic quality estimation routing weak segments to human review, or on a published quality evaluation with its method. 2 8 11 12
The Data Protection Officer
Machine translation runs through five named engines — an own AI translator plus AWS, DeepL, Google Translate and Azure — with provider choice per language, a formality setting, glossary terms, and an AI playground where models can be switched and prompt fragments edited, with automatic context extraction feeding the prompts and GPT-4o shown as the default. Engine use is optional and can be switched off. We found no published language list, no document translation that keeps office layout, no per-segment quality estimation and no published quality evaluation. 12 2 8 11
The E-Commerce Marketer
DeepL, Google Translate, Azure, AWS and Tolgee's own AI translator are offered side by side with per-language provider choice, a formality setting and glossaries, and the LLM side lets me pick OpenAI, Anthropic or Gemini, edit custom prompts and feed screenshots and key descriptions as context. I found no public information on a published language list, on document translation for Word or PDF files, or on any published quality evaluation — so my French, Italian, Dutch and Spanish roll-out would rest on engines I cannot verify in advance. 2 11 12
The Skeptic
Five named engines (Tolgee AI Translator, AWS, DeepL, Google Translate, Azure) with per-language provider selection, a formality setting, glossaries and editable prompt fragments give real control, and self-hosted users can point it at their own LLM keys. But we found no published language list, no public information on document translation that keeps office or InDesign layout, no automatic quality estimation routing weak segments to review, and no published quality evaluation with its method — the claim of superior results compared to machine translators appears without one. 2 12 11 15
Translation memory, terminology & review workflow
Show reasoningHide reasoning
How this is scored
How translation is managed as an ongoing process: translation memory with fuzzy matches, a termbase or glossary managed centrally, style guides, review and approval stages, automated QA checks (placeholders, tags, length, terminology, punctuation), an in-context or visual editor, screenshots and context for translators, tasks and deadlines, roles per language, and ordering or inviting human translators and agencies inside the product.
0 — No management of translations at all; text goes in and comes out with nothing stored or reviewed.
3 — Translations can be edited or a glossary kept; translation memory, review stages and QA checks are basic or not described.
5 — A translation memory reused across projects, a central glossary, at least one review or approval stage, automated QA checks for placeholders and terminology, comments and screenshots for context, and roles that limit translators to their languages.
8 — Configurable multi-step workflows with automation rules, an in-context or visual editor for apps or websites, QA checks configurable per project with blocking rules, style guides applied by the AI, translation memory and termbase shared across projects with penalties and priorities, vendor or agency management with ordering inside the product, and progress and cost reporting per language.
10 — A translation process an enterprise runs on: workflows per content type with conditional routing on quality scores, linguistic quality assessment with a named framework (MQM or similar), termbase with approval workflow and forbidden terms, full revision history per segment, and productivity and quality metrics per translator and vendor.
The Localization Manager
A translation memory with similarity-based suggestions can be shared across projects and imported or exported, a central glossary carries term types such as non-translatable, states run Untranslated, Translated and Reviewed with keys assignable as tasks, and QA checks flag placeholders, punctuation, spacing and formatting with warning, error or off severity — the gate I need before a release ships. In-context editing works even in production with one-click screenshots and comments, and professional translation can be ordered inside the product from Alconost or Dialect, though cloud only. We found no public information on configurable multi-step workflows, style guides applied by the AI, or progress and cost reporting per language and vendor. 1 3 4 7 8 12
The App Developer
The pieces I live with daily are there: translation memory with similarity suggestions shared across projects, states from Untranslated to Reviewed, tasks with progress tracking, comments, per-key history, QA checks for placeholders and punctuation with per-check severity, and an in-context editor that works even in production. Professional translations can be ordered inside the product from named partners (Alconost, Dialect), with role-based permissions. I found no public information on multi-step configurable workflows, terminology QA checks, or per-language cost and progress reporting. 12 7 4 8 11
The In-House Document Translator
The essentials of a review process are documented: translation memory with similarity suggestions shared across projects, a glossary with term types such as non-translatable and case-sensitive, the states Untranslated, Translated and Reviewed, QA checks for placeholders, punctuation, spacing and formatting that can be set to block with error severity, tasks assignable per key, comments, one-click screenshots, an activity log and translation history — plus ordering human translation from Alconost or Dialect inside the product. We found no public information on configurable multi-step workflows with automation rules or on progress and cost reporting per language. 1 3 4 7 12
The Data Protection Officer
Translation memory gives similarity-based suggestions and is shared, imported and exported across projects; states run Untranslated, Translated and Reviewed with an optional review pass; QA checks for placeholders, punctuation, spacing and formatting can each be set to warning, error or off; keys are assigned as translation or review tasks with progress tracking, and professional translation can be ordered inside the product from named agencies Alconost and Dialect, on cloud only. In-context editing with one-click screenshots is core to the product. We found no public information on configurable multi-step workflows, per-language role limits or cost reporting per language. 12 7 4 3
The E-Commerce Marketer
Translation memory with similarity suggestions shared across projects, a central glossary, Untranslated/Translated/Reviewed states, assignable tasks, comments, translation history and QA checks for placeholders, punctuation and formatting with warning or error severity are all documented, and in-context editing works even on the production site — exactly how I would fix a bad product name by hand. Professional translation can be ordered inside the product from Alconost and Dialect, though only on the cloud version, and I found no public information on cost reporting per language or style guides applied by the AI. 3 7 12 15
The Skeptic
Translation memory with similarity-percentage suggestions shared across projects, a glossary with term types, Untranslated/Translated/Reviewed states, QA checks for placeholders, punctuation, spacing and formatting with warning/error severity, tasks with assignment and progress, comments, screenshots, an activity log, per-key history, fine-grained permissions — and ordering professional translation from Alconost or Dialect inside the product. We found no public information on configurable multi-step workflow rules, style guides the AI applies, or progress and cost reporting per language. 12 7 4 11
Integrations, file formats & developer tools
Show reasoningHide reasoning
How this is scored
How content gets in and out: the file formats supported (XLIFF, PO, JSON, YAML, Android XML, iOS strings and xcstrings, Office documents, InDesign), a REST API and CLI, SDKs and over-the-air updates for apps, Git repository sync (GitHub, GitLab, Bitbucket) and CI pipelines, connectors for CMS, shop and design tools (WordPress, Contentful, Shopify, Figma), browser and office add-ins, webhooks, and a JavaScript snippet or proxy for website translation.
0 — No documented way to get content in or out except typing or pasting by hand.
3 — File upload and download or a basic API; formats, repository sync and connectors are basic or not described.
5 — A documented REST API, a list of supported file formats covering the common software and document formats, sync with at least one Git host or CI, and connectors or plugins for several named CMS, shop or design tools.
8 — A CLI and SDKs for named platforms, over-the-air updates for mobile or web apps, Git sync with branching, webhooks, connectors for the main CMS, shop, design and support tools, office or browser add-ins, a public status page, and API limits documented.
10 — Integration that scales across an organisation: an API covering every function of the product with versioning and SDKs, an app or connector framework third parties build on, continuous localization in CI with pull requests opened automatically, and every connector documented with its limits and the fields it syncs.
The Localization Manager
The format list covers the software side well — JSON, XLIFF, PO, YAML, RESX, Android XML, Apple strings and stringsdict, Flutter arb, CSV and XLSX — with a REST API stated to do anything the UI can, a CLI, webhooks, over-the-air content delivery, an MCP server, and SDKs for React, Angular, Vue, Svelte and Next.js plus browser plugins, Figma and Slack. We found no public information on Git repository sync, CI pipelines, or connectors for CMS, shop and support tools beyond Figma and Slack, and no documented API limits or public status page. 4 5 7 13 14
The App Developer
This is nearly my wishlist: a CLI to push and pull localization data, a REST API that 'can do everything the UI can do', webhooks, an MCP server, and content delivery that deploys translations to servers worldwide 'without rebuilding your app' — that's the over-the-air fix I want for a typo. My JSON, Android XML, Apple.strings/.stringsdict, XLIFF, PO, RESX and Flutter arb are all covered, plus Figma, Slack and browser plugins. What keeps it short of the top: I found no public information on Git repository sync opening pull requests, CMS or shop connectors, a public status page, or documented API limits. 13 5 4 14 7
The In-House Document Translator
Content moves well for software teams: a REST API that can do anything the UI can, a CLI for pushing and pulling localization data, SDKs for React, Angular, Vue, Svelte and Next.js, formats from JSON, XLIFF, PO, YAML and RESX to Apple strings, Android XML, Flutter arb, CSV and XLSX, plus a Figma plugin, Chrome and Firefox add-ons, Slack, webhooks, an Unreal integration, an MCP server and worldwide content delivery without rebuilding the app. For my documents the format list stops at tabular CSV and XLSX; we found no public information on Word, PDF or InDesign handling, Git repository sync with a named host, or CMS and shop connectors. 3 4 5 7 13 14
The Data Protection Officer
Supported formats cover JSON, XLIFF, PO, YAML, RESX, Apple strings and stringsdict, Android XML, Flutter arb and CSV/XLSX; a CLI pushes and pulls data, the REST API is stated to do everything the UI can, webhooks are supported, and SDKs exist for React, Angular, Vue, Svelte and Next.js as well as Unreal, with instant worldwide content delivery, a Figma plugin, Slack, and Chrome and Firefox add-ons. We found no public information on Git host synchronisation, CMS or shop connectors, a public status page or documented API limits. 5 13 14 4 7
The E-Commerce Marketer
A REST API that can do everything the UI can, a CLI, webhooks, instant worldwide content delivery and SDKs for React, Angular, Vue, Svelte, Next.js, Apple, Android and Flutter are documented, with JSON, XLIFF, PO, YAML, RESX, Apple, Android and Flutter formats plus CSV and XLSX and a Figma plugin. As a store owner I have to note I found no public information on a Shopify connector or any other shop or CMS connector, on Git repository sync, or on documented API limits and a status page — so getting my catalogue in and out looks like manual file work for me. 4 5 13 14
The Skeptic
A developer story with substance: a REST API stated to do everything the UI can do, a CLI for pushing and pulling localization data, SDKs for React, Angular, Vue, Svelte and Next, formats from JSON and XLIFF to Apple strings, Android XML, Flutter arb and RESX, webhooks, worldwide content delivery without rebuilding the app, an MCP server and an Unreal integration. The connector story is thinner — the captured pages show Figma, Slack and browser plugins, and we found no public information on CMS or shop connectors, Git host sync, a status page or documented API limits. 5 13 3 4 14 7
Confidentiality of translated content
Show reasoningHide reasoning
How this is scored
What happens to the text a customer translates: whether source and target texts are stored and for how long, deletion after translation, whether customer content is used to train the vendor's or a third party's models, which machine translation and LLM providers a TMS sends text to and whether that can be restricted or switched off, encryption in transit and at rest, single sign-on, roles and audit logs, and certifications (ISO 27001, SOC 2) with their scope. Where the text is processed is scored under sovereignty.
0 — Customer texts are stored indefinitely and used for the vendor's own purposes, or no statement on data handling exists at all.
3 — The product is described as secure or GDPR-compliant and a privacy policy exists; retention of translated texts, model training and third-party engines are basic or not described.
5 — A documented statement that customer texts are not used to train models, retention or deletion of translated texts stated, the third-party engines or LLM providers named, encryption in transit and at rest, single sign-on on a business tier, and a data processing agreement offered.
8 — Texts deleted immediately after translation or after a retention period the customer sets, third-party AI processing switchable per project or account, zero-retention terms with the named LLM providers, audit logs, granular roles, ISO 27001 or SOC 2 certification stated with its scope, and a private or dedicated deployment option.
10 — Confidentiality that can be verified: an on-premise or customer-controlled deployment, customer-managed encryption keys, every subprocessor that sees content listed with its role, independent audit reports available, and every data flow of a translation request documented end to end.
The Localization Manager
The vendor states that customer data is not used to train AI models, names the machine translation and LLM providers text can go to with an opt-out, and says LLM providers are chosen whose API terms do not train on submitted data, with deletion from production and backups within seven days, TLS and AES-256, ISO 27001, role-based access, audit logging and a self-hosted option where the vendor sees no projects, users or logs. The data processing agreement is available only on request for enterprise customers, and the terms disclose that the vendor sometimes looks into user projects via session replay for UX improvement and debugging, which matters for confidential marketing copy. 9 10 11 15
The App Developer
Encryption in transit and at rest (AES-256 for databases, file storage and backups), deletion from production and backups within 7 days, a flat statement that customer data is not used to train AI models, the machine-translation engines named with an opt-out, LLM providers restricted to those whose APIs do not train, plus ISO 27001, role-based access, audit-style logging, SSO and a self-hosted escape hatch where the vendor sees nothing. Two caveats: the data processing agreement is only 'available on request for enterprise customers', and the terms disclose that the vendor sometimes looks into user projects using open-replay to improve UX or debug. 11 9 8 15
The In-House Document Translator
The promise I need in writing is there: customer data is not used to train AI models, LLM providers are selected for no-training API terms, the machine translation providers are named with an opt-out, and deletion from production systems and backups happens within 7 days — alongside HTTPS/TLS, AES-256 at rest for databases, file storage and backups, granular roles, audit logging, optional two-factor authentication and ISO 27001. Two caveats decide against a higher score: the terms state they sometimes look into user projects via open-replay to improve UX and debug, and the data processing agreement is available only on request and only to enterprise customers. 9 10 11
The Data Protection Officer
The security policy states that customer data is not used to train AI models, that the optional machine-translation integrations (ChatGPT, AWS Translate, Google Translate, DeepL) can be switched off, that LLM providers are chosen for API policies excluding training, that project or account data is deleted from production and backups within 7 days, and that traffic is TLS-encrypted with AES-256 at rest, role-based access control, logging, optional SSO and 2FA, ISO 27001, a data processing agreement on request for enterprise customers, and a self-hosted edition where the vendor states it sees no projects. Two things hold me back: the terms reserve the vendor's right to look into user projects via open-replay for UX improvement and debugging — for member correspondence that is a clause I would have to take to the board — and we found no public information on the ISO 27001 scope, on zero-retention terms with the LLM providers, or on a deletion window the customer controls. 11 9 10 8
The E-Commerce Marketer
The security page states customer data is not used to train AI models, LLM providers are chosen whose APIs do not train on submitted data, deleted projects are removed from production and backups within 7 days, traffic is TLS-encrypted with AES-256 at rest, and ISO 27001, role-based access and audit logging are claimed, with a self-hosted install keeping the vendor out entirely. That is tempered by a terms clause saying the vendor looks into user projects with open-replay to improve UX and debugging, a data processing agreement available only on request for enterprise customers, and no stated customer-controlled retention, zero-retention terms or SOC 2 report for Tolgee itself. 9 10 11
The Skeptic
A strong paper trail: no use of customer data to train AI models, named engines (ChatGPT, AWS Translate, Google Translate, DeepL) with an opt-out and providers selected for no-training API policies, permanent deletion from production and backups within 7 days, TLS and AES-256 at rest, RBAC, extensive logging, ISO 27001, optional 2FA, and a self-hosted edition where the vendor states it sees no projects. Two things temper it: the terms state the vendor looks into user projects via open-replay to improve UX and that this shall not be considered a breach of confidentiality, and the data processing agreement is available only on request for enterprise customers — the ISO 27001 scope is also not described. 11 9 8
Data export, portability & self-hosting
Show reasoningHide reasoning
How this is scored
Whether translation assets stay the customer's and can leave with them: export of translation memory and termbase in open formats (TMX, TBX, XLIFF, CSV), export of all projects and files, import from another TMS, an API that can read every asset, the return or deletion of data on termination, open-source code and a self-hosted or on-premise edition.
0 — Translations cannot be exported; they exist only in the vendor's interface or engine.
3 — Translated files can be downloaded; export of translation memory and glossary, import and termination terms are basic or not described.
5 — Translation memory exportable as TMX and glossary as TBX or CSV, all project files downloadable, import of translation memory and glossaries from another tool, and an API that reads translations and keys.
8 — Complete export of every asset (memory, termbase, files, comments, history) in open formats, a documented migration path from named competitors, the data returned or deleted on termination under stated terms, and a self-hosted or on-premise edition with its own documentation.
10 — The customer owns the assets end to end: open-source code under a named licence that runs fully self-hosted with feature parity stated, a complete export another tool can import without loss, and the deletion of every copy on termination documented.
The Localization Manager
The core is Apache License 2.0 with the enterprise directories removable to build fully open-source binaries, and the free self-hosted edition has its own documentation, unlimited translation keys and an upgrade path that keeps data intact; the translation memory can be imported, exported and shared across projects, and the REST API is stated to do everything the UI can. Termination terms state all your data may be permanently erased, with a carve-out for resultant data. We found no public information on termbase, comment or history export, on named TMX or TBX interchange for memory and terms, or on a documented migration path from the competitors the vendor compares itself to. 6 9 12 13 15
The App Developer
The core is Apache 2.0, the self-hosted edition is free up to 10 seats with its own documentation, my data stays intact if I later apply a licence key, and export runs via CLI, REST API or the UI to any supported format — exactly the exit path I want if the vendor changes course, and they publicly commit to maintaining it. Translation memories import and export, but I found no public information on TMX or termbase export in those named open formats, a documented migration path from the competitors they compare themselves against, or export of comments and history; the termination clause says the vendor 'may destroy and permanently erase all Your Data'. 15 13 12 6 9
The In-House Document Translator
Assets can leave: the core is licensed under Apache 2.0, the free self-hosted version runs on our own infrastructure with published documentation and the vendor stating it does not see our projects, users or logs, translation memory imports and exports and is shared across projects, everything the UI does is readable over the REST API, stored content exports to any supported format, and upgrading the free self-hosted instance to a licence keeps data intact. We found no public information on TMX or TBX export, on a documented migration path from other tools, or on exporting comments and history; the terms allow destruction of data on termination but exclude Resultant Data from that obligation. 6 9 12 13 15
The Data Protection Officer
The platform core is open source under Apache 2.0, a fully open version can be built by removing the enterprise directories, and self-hosting is documented from Docker or Java installation through system requirements, with machine translation via the customer's own API keys; translation memory is importable and exportable, the REST API can do everything the UI can, and anything stored can be exported to any supported format. Advanced features such as SSO and granular permissions sit under the enterprise licence, we found no public information on TMX or TBX export or a documented migration path from the competitors Tolgee compares itself to, and on termination the vendor may erase all customer data with an exception for Resultant Data. 15 12 13 9 6
The E-Commerce Marketer
The platform core is Apache 2.0 licensed, self-hosting via Docker or Java is documented, the free self-hosted version has unlimited keys and up to 10 seats, and everything stored can be exported to any supported format through the UI, the CLI or an API that mirrors the whole interface, with translation memories importing and exporting. I found no public information naming TMX or TBX export formats, export of comments and history, or a documented migration path from Lokalise, Crowdin or the other tools they compare themselves with, and advanced features like SSO stay locked behind the paid licence even on my own servers. 6 12 13 15
The Skeptic
Exit is real: an Apache 2.0-licensed core you can run yourself with self-hosting documentation, export via CLI, REST API and UI into XLIFF and the other supported formats, translation memory import and export shared across projects, and an upgrade from free to licensed that keeps data intact. We found no public information on TMX or TBX export for memory and terminology, no export of comments or history, no migration path from the named competitors beyond marketing comparison pages, and the termination clause states the vendor may destroy your data with a carve-out for Resultant Data. 15 6 12 13 9 4
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where texts are translated, stored and processed, and who the subprocessors are (hosting, machine translation engines, LLM providers, CDN for over-the-air delivery, support and payment tools). Independently sourced by the sovereignty pipeline; translated texts often hold personal data and trade secrets, so the whole chain counts, including the engines a TMS calls. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (machine translation or LLM providers, CDN, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations including the engines and LLM providers, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every text on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, engine and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Localization Manager
Tolgee s.r.o. is a Czech entity registered in Brno under Czech governing law, servers are stated to sit in Germany, Czech Republic and the United States on named Microsoft Azure and AWS infrastructure, subprocessors are named including the machine translation engines, analytics and error reporting run in EU regions, and ISO 27001 is stated. A self-hosted edition is documented where the vendor says it does not see projects, users or logs, keeping every text on our own servers — the route our residency rules would push us to. The data processing agreement is available only on request for enterprise customers rather than published, and the captured pages give no allocation of which data runs in the United States or the locations of the translation engines themselves. 9 10 11 15
The App Developer
Tolgee s.r.o. in Brno under Czech governing law, servers 'located in Germany, Czech Republic, and United States' on named Microsoft Azure and AWS infrastructure, and a subprocessor list covering Stripe, PostHog (EU), Sentry (EU), Amazon SES and the machine-translation engines, with ISO 27001 stated and data stored in EU data centres 'whenever feasible'. Self-hosting keeps projects on my own servers with the vendor seeing neither projects nor logs. Holding it back: the United States sits in the cloud chain without a stated safeguard, I found no public information on where the engines themselves process text, and the data processing agreement is not published. 9 11 10 8 6
The In-House Document Translator
The contracting entity is Tolgee s.r.o. of Brno under Czech law, servers sit in Germany and Czechia as well as the United States on named Microsoft Azure and AWS infrastructure, subprocessors including the machine translation engines, Stripe for payment and EU-hosted PostHog and Sentry are listed with an opt-out for machine translation, ISO 27001 is stated, and a documented self-hosted edition keeps every text on the customer's own servers. The data processing agreement is available on request for enterprise customers rather than published, and the locations of the translation engines themselves are not stated. 6 9 10 11 15
The Data Protection Officer
The contracting entity is Tolgee s.r.o. of Brno under Czech law and Czech courts, hosting is on named Azure and AWS infrastructure with servers stated in Germany, Czech Republic and the United States, and the subprocessors are named with their roles: Stripe for payments, PostHog and Sentry in the EU, Amazon SES for mail, and ChatGPT, AWS Translate, Google Translate and DeepL for optional machine translation, alongside ISO 27001. EU data centres are promised only "whenever feasible", the data processing agreement is available on request for enterprise customers rather than published, and we found no public information on where each engine processes text. The documented self-hosted edition keeps texts on the customer's own infrastructure, though its AI translator can also be routed through Tolgee Cloud on a per-credit basis. 9 11 10 15 8
The E-Commerce Marketer
The contracting entity is Tolgee s.r.o. in Brno under Czech law, GDPR compliance and EU data centres are stated, servers sit in Germany, Czech Republic and the United States on named Azure and AWS infrastructure, and subprocessors including PostHog in the EU, Sentry in the EU, Stripe, Amazon SES and the machine-translation engines are named, with ISO 27001 certification. The data processing agreement exists only on request for enterprise customers, the engines' own locations are not stated and part of the chain runs through the US — though a self-hosted install keeps my product catalogue on servers I control. 9 10 11 15
The Skeptic
The contracting entity is Tolgee s.r.o. in Brno under Czech governing law, hosting is named as Azure (compute, databases) and AWS (storage, email) with servers in Germany, Czech Republic and the United States, and the subprocessor chain is at least listed — Stripe for payments, Amazon SES for mail, PostHog and Sentry in the EU, ChatGPT, AWS, Google and DeepL for machine translation. The engines and the payment link carry no stated processing location or data-location safeguard, the EU-data-centre promise is qualified as whenever feasible, and the DPA is on request rather than published; the self-hosted edition does keep texts on your own servers, though its AI translator can route through Tolgee Cloud. 9 10 11 8 15
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by characters, words, keys, hosted words or seats, what happens when the volume exceeds the tier, the number of users, projects and languages included, which features (machine translation volume, AI credits, SSO, integrations, API access) cost extra, the free tier and its limits, the self-hosted edition and its support, minimum term and setup.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with volume, seats or features is unclear.
5 — Tiers are public with their price per volume band and main inclusions, but at least one commonly needed piece (overage, extra seats, machine translation or AI volume, SSO, connectors) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (characters, words, keys, seats), overage handling stated, add-ons and AI credits priced, the self-hosted edition's cost or licence stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given volume, seat count and feature set, with every add-on, setup, support and overage fee and the cancellation and data-return terms published.
The Localization Manager
Cloud pricing is public: a free tier with 30,000 hosted words, 10,000 MT credits and 3 seats, then Translate at €58/mo, Optimise at €133/mo and Manage at €373/mo billed annually with two months free on annual payment, word bands from 50k to 10M in EUR or USD, unlimited seats and projects, and the conditions state fees are exclusive of taxes, non-cancelable and non-refundable with auto-renewal. Enterprise — where single sign-on sits — carries no public price, and self-hosted licensing is described as based on keys and seats and tailored to your setup, with prices not published. We found no public information on overage handling, additional MT credit pricing, or adding seats. 1 6 8 9 15
The App Developer
The cloud side is public and concrete: a free tier with 30,000 hosted words, 10,000 MT credits and 3 seats at €0 with no card required, then 'Translate €58/mo billed annually', 'Optimise €133/mo billed annually' and 'Manage €373/mo billed annually' across word tiers from 50k to 10M with unlimited seats and taxes stated as exclusive. The self-hosted licence is where it goes dark: licensing is 'based on both keys and seats, tailored to your setup' with no published price, there is no self-hosted trial, and I found no public information on overage handling or what happens when MT credits run out. 8 15 9 6 1
The In-House Document Translator
Cloud prices are public: Free at €0 with 30,000 hosted words, 10,000 MT credits and 3 seats with no card required; Translate at €58/mo billed annually, Optimise at €133/mo and Manage at €373/mo, all with unlimited seats and projects, word tiers from 50k to 10M in EUR or USD, two months free on annual billing, and taxes exclusive. But self-hosted licensing is based on keys and seats and tailored to the setup without a published price, there is no trial for the self-hosted version, we found no public price for the Enterprise plan that carries single sign-on, and no public information on overage handling or the cost of machine translation credits beyond the free 10,000. 1 6 8 9 15
The Data Protection Officer
The three cloud tiers are priced publicly — Translate at €58/mo billed annually, Optimise at €133/mo billed annually, Manage at €373/mo billed annually — with a free tier of 30,000 hosted words, 10,000 MT credits and 3 seats, unlimited seats and projects, a published definition of the hosted word, two months free on annual billing, and fees stated exclusive of taxes. The self-hosted licence is based on keys and seats but tailored and unpriced, the Enterprise plan carries no price, and we found no public information on how prices scale across the 50k to 10M hosted-word range, on machine-translation credit costs beyond the included amount, or on overage handling. 8 15 9 1
The E-Commerce Marketer
Cloud prices are published: a free tier of 30,000 hosted words, 10,000 machine-translation credits and 3 seats, then Translate at €58/mo, Optimise at €133/mo and Manage at €373/mo billed annually, with unlimited seats and unlimited projects, word tiers from 50k to 10M in EUR or USD, two months free on annual billing and VAT-exclusive fees — though each word in every translation counts separately, so my five-language catalogue multiplies the hosted-word count. What I cannot compute from the pages is the price of extra machine-translation credits, what happens when a word tier is exceeded, the Enterprise price for single sign-on, or the self-hosted licence, which is tailored to keys and seats rather than published. 1 6 8 9 15
The Skeptic
Cloud tiers are published with prices exactly as stated — Free at €0 with 30,000 hosted words, 10,000 MT credits and 3 seats, Translate €58/mo, Optimise €133/mo, Manage €373/mo billed annually, two months free on annual billing, unlimited seats and projects, word bands from 50,000 to 10 million in EUR or USD, taxes exclusive and auto-renewal terms stated. What a buyer still cannot compute: self-hosted licensing is based on keys and seats and tailored rather than priced, the Enterprise plan lists features without a price, and neither overage handling nor the cost of MT credits beyond the free allotment appears on the captured pages. 8 1 9 15
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined ⚠ unverified | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Tolgee
Is Tolgee European?
Yes. whats-best.ai classifies Tolgee as EU-Made.
Where does Tolgee store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Tolgee have a free plan?
Yes. Tolgee has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Tolgee?
As of 2 Nov 2026, the panel rates SimpleLocalize (3.5/5), LILT (3.5/5) and Phrase Localization Platform (3.5/5) highest among the other 12 Translation & Localization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is SimpleLocalize (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Tolgee alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Open source, Hosting location, Hosting options, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 13 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 5 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage tolgee.io Checked 1 Nov 2026 Details →
- 2 Features page (AI translation) tolgee.io Checked 1 Nov 2026 Details →
- 3 Features page (in-context editing) tolgee.io Checked 1 Nov 2026 Details →
- 4 Features page (localization process) tolgee.io Checked 1 Nov 2026 Details →
- 5 Integrations page tolgee.io Checked 1 Nov 2026 Details →
- 6 Documentation (self-hosting) docs.tolgee.io Checked 1 Nov 2026 Details →
- 7 Source code repository github.com Checked 1 Nov 2026 Details →
- 8 Pricing page tolgee.io Checked 1 Nov 2026 Details →
- 9 Terms of service tolgee.io Checked 1 Nov 2026 Details →
- 10 Privacy policy tolgee.io Checked 1 Nov 2026 Details →
- 11 Security / trust page tolgee.io Checked 1 Nov 2026 Details →
- 12 Translation memory, terminology & review workflow — found from sitemap tolgee.io Checked 1 Nov 2026 Details →
- 13 Integrations, file formats & developer tools — found from sitemap tolgee.io Checked 1 Nov 2026 Details →
- 14 Integrations, file formats & developer tools — found from sitemap tolgee.io Checked 1 Nov 2026 Details →
- 15 Data export, portability & self-hosting — found from sitemap tolgee.io Checked 1 Nov 2026 Details →