Translation & Localization
Locize
UK / wider Europe Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by inweso GmbH · www.locize.com
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.
Locize at a glance
- Vendor
- inweso GmbH
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention Ireland source, captured 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Starting price
- “STARTER $7 /mo billed monthly” (vendor’s words) source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Locize 3/5, the mean of 6 judges. Locize, a Swiss translation management platform from inweso GmbH, earned persona-weighted totals of 6.7 to 6.9 from five judges, while the in-house document translator came in at 0.0 — the bench's sharpest split. 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
Locize, a Swiss translation management platform from inweso GmbH, earned persona-weighted totals of 6.7 to 6.9 from five judges, while the in-house document translator came in at 0.0 — the bench's sharpest split. That zero traces to the vendor's own documentation: the service generally handles keys and values and does not preserve original file structure, so no Word or PDF document comes back with its layout. The judges working in software strings scored machine translation, workflow and review, integrations and formats, content confidentiality and sovereignty at 7, citing XLIFF through 2.2, gettext, JSON and YAML coverage, a REST API, CLI, GitHub Actions and a 28-tool MCP server with CDN delivery that needs no redeploy, and machine translation and AI that can be switched off entirely or run on the buyer's own keys. Pricing transparency sits lowest at 5-6: seven tiers are public from Free at $0 /mo to ENTERPRISE at $199 /mo billed monthly, but volume limits are documented only for the free tier. Portability and exit splits 7 against 6; we found no public information on a self-hosted edition.
Speaks for it
- Software-string format coverage runs from XLIFF 1.2 through 2.2 to gettext, JSON, YAML, Android, iOS strings and xcstrings, resx, Laravel and Fluent, served by a REST API, CLI, GitHub Actions, webhooks and a 28-tool MCP server
- Machine translation and AI can be switched off entirely, or run on your own provider keys or a self-hosted OpenAI-compatible endpoint, keeping the data flow under your own contract
- Every AI translation carries a quality-estimation confidence score with a stated reason, and low-confidence output becomes a pending review instead of being saved silently
- The data chain is documented: Swiss contracting entity inweso GmbH, hosting on AWS in Ireland, encrypted disaster-recovery copies on BunnyCDN Storage in the EU under vendor-held offline keys, and a published DPA under Swiss law
- Prices are public and flat monthly — Free at $0 /mo up to ENTERPRISE at $199 /mo billed monthly — with a 14-day full-feature trial and no credit card required
Held against it
- The vendor states the original file structure is not preserved, so no Word or PDF document comes back with its layout
- Volume limits are documented only for the free tier, and we found no public information on paid-tier inclusions, overage handling or AI-credit pricing
- We found no public information on connectors for CMS or shop systems, office or browser add-ins, a public status page or documented API limits
- The certifications shown are the AWS hosting provider's rather than the vendor's own, and we found no public information on a vendor-held ISO 27001 or SOC 2 certificate
- We found no public information on a self-hosted or on-premise edition of the product or on a documented migration path from named competitors
Best for
- You localize software strings — JSON, YAML, XLIFF, gettext, Android or iOS — and want CI/CD delivery with a CLI, GitHub Actions and CDN updates that ship without a redeploy
- You handle confidential strings: machine translation and AI can be switched off entirely, or run under your own provider keys or a self-hosted OpenAI-compatible endpoint, keeping the data flow under your own contract
- You are a European buyer who wants the chain in writing: a Swiss contracting entity, hosting on AWS in Ireland, encrypted disaster-recovery copies on BunnyCDN Storage in the EU, and a published DPA under Swiss law with Zurich jurisdiction
- You want AI pre-translation with guardrails: glossary terms in every AI request, a style guide per language, and low-confidence AI output routed into human review before it goes live
Avoid if
- You translate contracts or other office documents (Word, PDF) and need the original layout back — the vendor states the original file structure is not preserved and only keys and values are handled
- You rely on the Pro CDN and must keep every delivery hop inside the EU — published translations on the Pro CDN go out through AWS CloudFront with edge locations in the United States and worldwide
- You need the vendor's own ISO 27001 or SOC 2 certificate for procurement — the certifications shown are the AWS hosting provider's rather than the vendor's own
- You must budget a large catalogue before committing — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3.5 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 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 3 of 5 |
Machine translation & AI quality
panel disagrees
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
AI and machine pre-translation covers 150+ languages with a genuine choice of engines — Google, DeepL, OpenAI, Gemini, Mistral, Anthropic, Lara — plus my own keys and even a self-hosted OpenAI-compatible endpoint, which keeps the data flow under my contract. Glossary terms are injected into every AI request and checked on every save, and a style guide sets tone and formality per language — exactly what I demand. Quality estimation scores every AI translation with a reason and routes low-confidence output into human review, but plain machine translation gets no score, the review threshold is fixed at 0.7, and we found no public information on custom models trained on the customer's own translations or a published quality evaluation. 1 7 10 11
The App Developer
Multiple named engines from Google Translate to DeepL and LLM providers including OpenAI, Gemini, Mistral, Anthropic and Lara, with my own API keys supported and even a custom OpenAI-compatible endpoint covering self-hosted vLLM — that is exactly the control I want, plus glossary terms and a per-language styleguide injected into every AI request. Quality estimation scores each AI translation with a confidence value and reason and routes low-confidence output into review, but traditional machine translation is not scored, the needs-review level is fixed at 0.7, and we found no public information on document translation that keeps layout, custom models, or a published quality evaluation with its method. 1 7 10 11
The In-House Document Translator
The engine list is named (Google Translate, MyMemory, DeepL, OpenAI, Gemini, Mistral, Anthropic, Lara), I can bring my own keys or a self-hosted model endpoint, glossary terms go into every AI request and are checked on every save, and a per-language style guide sets tone and formality. Quality estimation scores every AI translation between 0 and 1 with a stated reason and routes low-confidence output into human review instead of saving it silently — the control I want before a contract leaves the house. What holds it down: only AI output is scored, not plain machine translation; we found no public information on a published quality evaluation; and the vendor's own documentation states the service generally handles keys and values and does not preserve the original file structure, so no Word or PDF document comes back with its layout. 1 7 10 11 14
The Data Protection Officer
Eight named engines and AI providers drive pre-translation, glossary terms go into every AI request, a per-language styleguide sets tone and formality, and every AI-produced segment carries a confidence score with a reason, low-confidence output being routed into human review below the 0.7 default. The documentation states the product handles keys and values rather than preserving original file structure, so layout-preserving Office-document translation is not what this tool does; we found no public information on custom models trained on the customer's own corrections or on a published quality evaluation, and traditional machine translation output is not scored. 1 7 10 11
The E-Commerce Marketer
For my five shop languages this is strong: Google Translate, DeepL, MyMemory and the LLM providers OpenAI, Gemini, Mistral, Anthropic and Lara are named and selectable, glossary terms go into every AI request and are checked on every save, and a style guide sets tone and formality per language. Every AI translation carries a confidence score with a reason and weak output is routed to human review below a default cut-off of 0.7, though plain machine translation output is not scored and the cut-off cannot be changed per project. We found no public information on models trained on my own past translations, on engine choice per language pair, or on a published evaluation of translation quality. 1 7 10 11
The Skeptic
Eight named engines including several LLM providers, a glossary injected into every AI request, a per-language style guide with tone and formality, and an AI evaluator that scores each AI translation between 0 and 1 and routes the doubtful ones into human review — all documented, including the admission that plain machine translation output goes unscored and the 0.7 default boundary cannot be changed per project. I found no public information on custom or adaptive models trained on the customer's own corrections, engine selection per language pair, or a published quality evaluation with its method. 7 10 11 12
Translation memory, terminology & review workflow
panel disagrees
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
The translation memory spans multiple projects with fuzzy and same-family-language matches, the termbase imports and exports TBX and UTX with approved and forbidden terms surfaced in the editor, review runs per language with proposals and marked values, and placeholders, plurals and markup are protected with checks that flag issues — most of what my team runs daily, down to screenshots and per-language review permissions. We found no public information on configurable multi-step workflows, blocking QA rules per project, or cost and productivity reporting per vendor, and the vendor itself states quality estimation is not MQM. 3 4 11 12 13 18
The App Developer
Translation memory with exact and fuzzy matches runs across projects, glossaries import and export as TBX and UTX with approved and forbidden terms surfaced in the editor, and review is one queue of proposals and marked values with per-language permissions and notifications into Slack, Teams, webhooks and GitHub dispatches. The in-context editor with screenshots, origin tracking per segment, and provenance recording every accept and decline is real workflow, and ordering third-party translation is in the product. We found no public information on configurable multi-step approval chains or cost reporting per language, and the quality estimation docs state it is explicitly not MQM. 3 4 10 12 13 18
The In-House Document Translator
The review process is documented end to end: one queue with proposals that wait for a decision before going live and live values flagged for review, enabled per language, confirmed only by an admin, a manager, or a user holding review permission for that language, with notifications when a language's queue crosses a set count. The translation memory searches exact and fuzzy matches across multiple projects with links back to the source, the glossary imports TBX or UTX with approved and forbidden terms per language surfacing in the CAT view, placeholders and plural forms are protected with checks that flag issues, and every accept and decline is recorded with who, when and the confidence at decision time. Ordering translations from third-party providers and pairing with any agency are described; the vendor states plainly that its quality estimation is not MQM, and we found no public information on per-translator productivity metrics. 3 4 10 12 13 18
The Data Protection Officer
A translation memory with exact and fuzzy matches reused across projects, a termbase with approved and forbidden terms surfaced in the editor, per-language review queues holding proposals and marked values, checks that flag broken placeholders, screenshots for context, and roles down to review permission per language are documented, with every accept and decline recorded and exportable as audit evidence. We found no public information on a named linguistic-quality framework, per-translator productivity and cost metrics, or quality checks configurable per project with blocking rules. 3 4 12 13 18
The E-Commerce Marketer
The editor surfaces translation memory matches, exact and fuzzy, across all my projects, imported TBX/UTX glossary terms appear as preferred terminology while translating, and one review queue holds proposals and flagged values with per-language reviewer permissions and a recorded who-decided-what history. The AI applies my style guide, checks protect placeholders and plurals, and human translation can be ordered from third-party providers inside the product — with the vendor stating it does not verify the quality of those translations. We found no public information on configurable multi-step approval chains, on quality checks configured per project with blocking rules, or on cost reporting per language. 4 6 11 12 13 18
The Skeptic
Translation memory with exact and fuzzy reuse across multiple projects, termbases imported and exported as TBX and UTX with approved and forbidden terms surfaced in the CAT view, an in-context editor with screenshots, per-language review permissions, placeholder checks, third-party translation ordering, and a one-year audit trail. The review process is documented as a single queue of proposals and marked values rather than configurable multi-step stages, and I found no public information on QA rules that block publishing, cost reporting per language, or productivity metrics per translator. 3 4 12 13 18
Integrations, file formats & developer tools
panel disagrees
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
XLIFF 1.2 through 2.2, gettext with fuzzy mapping both directions, Android strings, Apple strings and string catalogs, resx, properties, Laravel, Fluent, YAML, JSON, CSV and TMX cover every format my developers touch, backed by a CLI, a REST API with token permission control, GitHub Actions and repository dispatch, webhooks, Slack and Teams notifications, a Figma plugin, real-time CDN delivery and a 28-tool MCP server for AI coding agents. The gaps are office and CMS territory: we found no public information on Word, PowerPoint or InDesign with layout kept, on WordPress, Contentful or Shopify connectors, on browser or office add-ins, a public status page or documented API limits. 1 4 9 14 15
The App Developer
This is the strongest part for a developer like me: a documented CLI and REST API with scoped tokens, a GitHub Action and repository dispatch, webhooks, twenty-eight MCP tools, translation branches you can create and merge, and CDN delivery so a typo fix ships without a redeploy. The format list covers JSON, YAML, XLIFF 1.2 through 2.2, Android XML, iOS strings and xcstrings, gettext, resx and more, with a Figma plugin on top. We found no public information on connectors for CMS or shop systems, office or browser add-ins, a public status page, or the GitHub Action opening pull requests. 1 4 14 15
The In-House Document Translator
The software-format list is broad and specific — XLIFF through 2.2, gettext with fuzzy flags preserved in both directions, JSON, YAML, CSV/XLSX, Android, iOS strings and xcstrings, resx, properties, Laravel, Fluent, TMX, TBX and UTX — served by a documented REST API under token permission control, a CLI, GitHub Actions, webhooks, Slack and Teams, a Figma plugin and an MCP server with OAuth and 28 tools. Published translations ship over a CDN in real time without an app redeploy, and a private publish option keeps downloads behind an API key. We found no public information on SDKs, CMS or shop connectors, a public status page or documented API limits — and the vendor states the original file structure is not preserved, so office documents are not part of this round trip. 1 4 9 14 15 16
The Data Protection Officer
Import and export cover XLIFF through 2.2, gettext, Android, iOS strings and xcstrings, resx, properties, YAML, JSON, Laravel, Fluent, CSV, XLSX and TMX, next to a documented REST API, a CLI, GitHub Actions, webhooks, Slack, Microsoft Teams, a Figma plugin and a 28-tool MCP server with OAuth and personal access tokens. We found no public information on connectors for named CMS or shop systems, browser or office add-ins, a public status page, or documented API limits. 1 4 14 15
The E-Commerce Marketer
The format list is the widest I have seen for a software-string tool: XLIFF in four versions, gettext with fuzzy mapping, Android XML, iOS strings and string catalogs, JSON, YAML, CSV/XLSX, resx, Laravel, Fluent and TMX, plus a documented REST API, a CLI, GitHub Actions, webhooks and CDN delivery that updates translations without redeploying my site. There is a Figma plugin, Slack and Teams integrations, and an MCP server exposing 28 tools including branching and publishing. We found no public information on a connector for my Shopify shop or other CMS platforms, on office or browser add-ins, a public status page, or documented API limits. 1 4 14 15
The Skeptic
Software-format coverage is about as complete as it gets — XLIFF through 2.2, gettext with fuzzy flags preserved in both directions, Apple string catalogs, resx, Fluent — alongside a documented REST API with token permission control, a CLI, GitHub Actions, webhooks, Slack, Teams, a Figma plugin, and an MCP server with 28 tools and scoped tokens. For the top level I found no public information on CMS or shop connectors, an office or browser add-in, API rate limits, or a status page. 4 9 14 15
Confidentiality of translated content
panel disagrees
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 privacy policy names the AI and machine translation providers the service can call, says machine translation can be switched off entirely so nothing leaves the network, and lets me run my own keys or a self-hosted endpoint instead — the right answer for confidential strings. Data is TLS-encrypted in transit and encrypted at rest, SAML single sign-on, granular roles and a one-year audit trail exist, and the DPA deletes all data within 20 business days of termination. We found no public information on the vendor's own ISO 27001 or SOC 2 certification — the ISO 27001 list shown refers to AWS — and zero-retention terms with the LLM providers are only partially documented. 7 8 9 11 16 17
The App Developer
A published DPA with SCCs, encryption in transit and at rest, limited employee access, SAML single sign-on, granular roles and an audit trail, and machine translation and AI can be switched off entirely or run on my own provider keys under my own contract — the confidential-content docs even show private publish and bundling translations to self-host them. Gemini and Anthropic are stated not to train on content. The ISO 27001 we found is AWS's hosting certification rather than the vendor's own, and we found no public information on a dedicated or private deployment option. 6 7 8 9 11 16
The In-House Document Translator
The engines are named, the privacy policy states Gemini processes only the text segments necessary and does not store or use them for training, aggregated use is explicitly barred from containing translation content or personal data, and machine translation and AI can be switched off entirely — or run on my own keys, even a self-hosted model — so a draft contract need never touch a third party. Encryption in transit and at rest, SAML single sign-on, hardware-key multi-factor, granular roles, a one-year audit trail under Pro retention and a published DPA promising deletion within 20 business days of contract end are all documented. The gaps: the no-training statement covers the Gemini path rather than every provider, the certifications listed on the captured pages are AWS's rather than the vendor's own, and we found no public information on a private or dedicated deployment of the product itself. 6 7 8 9 11 16 17
The Data Protection Officer
The engines and AI providers that receive our texts are named, machine translation and AI can be switched off so confidential content never leaves our network — or run under our own provider keys — the privacy policy states Gemini does not store or train on the segments, encryption is stated in transit and at rest, and a one-year audit trail, granular roles, SAML single sign-on, multi-factor authentication and a DPA with deletion within twenty business days are published. Retention is tied to the subscription rather than a period we set, and we found no public information on an ISO 27001 or SOC 2 certificate for the vendor's own operation or on a private deployment option. 6 7 8 9 16 17
The E-Commerce Marketer
Everything is encrypted in transit and at rest, machine translation and AI can be switched off entirely so confidential product text never leaves the network, and I can bring my own provider keys so the data flows under my own contract; the built-in Gemini is documented not to train on my text, and the Anthropic contract runs through Anthropic Ireland with no retention by the model provider. Single sign-on via SAML, multi-factor options, granular roles and a one-year audit trail on Pro retention round it out, and a GDPR/FADP data processing agreement is published. The captured pages list certifications of the AWS hosting infrastructure rather than a certification of the vendor itself with its scope, and we found no public information on a private or dedicated deployment. 6 7 8 9 16 17
The Skeptic
The engines and AI providers are named one by one, machine translation and AI can be switched off by the controller so nothing leaves the network, encryption in transit and at rest, MFA with hardware keys, SAML single sign-on, granular roles, a published DPA with audit rights and breach notification, and a page that walks through confidential content — even advising against the ordering services for it. What holds it back: the only ISO 27001 list on the captured pages is the hosting provider's own, retention of the translation store follows the vendor's stated terms rather than a period the customer sets, and I found no public information on an on-premise or dedicated deployment or on retention terms with Google Translate specifically. 7 8 9 16 17
Data export, portability & self-hosting
panel disagrees
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
My assets can leave: translation memory exports as TMX, the glossary as TBX or UTX on demand, whole projects as a zip or an "all" format carrying namespace, tags, context and character limits, and the DPA returns or deletes data within 20 business days of termination — though the customer is responsible for exporting before deleted projects vanish. We found no public information on a documented migration path from named competitors or on a self-hosted edition of the platform itself; self-hosting and bundling cover only the delivered translation files. 6 8 14 16 18
The App Developer
TMX for translation memory, TBX and UTX for the glossary, whole-project zip export, API and MCP read access to translations and keys, and backups downloadable as ZIPs — my assets can leave. On termination the DPA promises deletion or return of personal data, and projects are deleted after the subscription ends with export the customer's responsibility. We found no public information on a documented migration path from named competitors, export of comments, or any self-hosted or open-source edition, which matters to me if the vendor changes course. 4 6 8 14 17 18
The In-House Document Translator
My assets can leave: the translation memory exports as TMX, the glossary as TBX or UTX in both directions, a whole project exports as a zip or "all" format carrying namespace, tags, context and maxCharacters columns, snapshots download as ZIPs of every namespace, and provenance reports go out as CSV and JSON — with an API that reads it all. The exit terms are stated: projects are deleted after the subscription ends, the customer is responsible for exporting first, and the DPA promises return or deletion of personal data. We found no public information on a self-hosted or on-premise edition of the product or on a documented migration path from named competitors. 6 8 10 14 17 18
The Data Protection Officer
Translation memory moves as TMX and terminology as TBX or UTX in both directions, a whole project exports as an all-format file or zip, backups download as a ZIP of all namespace files, and the API and MCP tools read projects, translations, memory and glossary. On termination the DPA promises deletion or return within twenty business days and ten days' advance notice with retrieval help; we found no public information on a migration path from named competitors, export of comments, or a self-hosted edition. 4 6 8 14 17 18
The E-Commerce Marketer
My data stays mine: the terms state the customer owns all Customer Data, translation memory moves as TMX, glossaries import and export as TBX and UTX with on-demand export, whole projects export as a zip, backup snapshots download as a ZIP, and on termination the processor deletes or returns personal data within 20 business days — with the customer responsible for exporting content before projects are deleted. We found no public information on a self-hosted edition of the product itself, on a documented migration path from named competing tools, or on the export of comments alongside memory and files. 6 8 14 17 18
The Skeptic
Leaving looks cheap: translation memory exports as TMX, termbases as TBX and UTX on demand, the whole project as a zip with metadata columns, backups downloadable as a zip of namespace files, and review decisions packaged as CSV and JSON. The end is documented too — projects are deleted after the subscription ends with the customer responsible for exporting first, and suspension comes with ten days' notice and retrieval help. I found no public information on a self-hosted edition of the platform itself or a documented migration path from named competitors. 6 14 17 18
European sovereignty
panel opinion
panel disagrees
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
The contracting entity is inweso GmbH in Switzerland, translations are hosted on AWS in Ireland with encrypted disaster-recovery copies on BunnyCDN Storage in the EU, business mail runs on Hostpoint in Switzerland, and the privacy policy lists the subprocessors including the AI providers — with Claude running through Amazon Bedrock in AWS Ireland under a contract with Anthropic Ireland and EU standard contractual clauses published in the DPA. Two caveats for my compliance colleagues: the Pro CDN delivers published translations through AWS CloudFront with edge locations in the United States, and the certifications shown are the hosting provider's, not the vendor's own. 2 7 8 9 16
The App Developer
Hosting is named as AWS in Ireland with encrypted disaster-recovery copies on BunnyCDN in the EU under keys Locize holds offline, the contracting entity is the Swiss inweso GmbH with a published DPA under Swiss law, and the privacy policy lists the subprocessors with locations and training statements, including Claude via Amazon Bedrock in AWS Ireland under contract with Anthropic Ireland. Parts of the chain — Google for the built-in AI and machine translation, Stripe for billing, CloudFront edges for the Pro CDN — sit outside the EU, with stated safeguards such as SCCs and the Data Privacy Framework. The entity is Swiss rather than EU, and the vendor's own certifications beyond AWS's are not shown. 2 7 8 9 16
The In-House Document Translator
The chain is unusually legible: a Swiss contracting and processing entity (inweso GmbH of Altnau, named with its company number and a data protection officer in the privacy policy and DPA; the footers give the name as "inweso Ltd liab. Co."), customer data hosted on AWS in Ireland by default, and encrypted disaster-recovery copies on BunnyCDN storage in the EU under keys the vendor holds offline. A Swiss-law DPA is published, transfers outside the EEA rest on adequacy decisions, the Data Privacy Framework and standard contractual clauses, and the subprocessors — Stripe, Cloudflare, Amazon SES, Google Analytics, Hostpoint — are listed with their purposes. For my desk the weak link is the default translation path through Google's Gemini and Google Translate, and we found no public information on the vendor's own ISO 27001 or SOC 2 certification or on the location of every subprocessor. 2 7 8 9 16
The Data Protection Officer
Customer data is hosted on named infrastructure, AWS in Ireland, under a Swiss contracting entity whose DPA is published and governed by Swiss law, and the privacy policy lists the subprocessors and their purposes, from Google Translate and Gemini for the default engines to Stripe for billing and Cloudflare for DNS. Transfers outside the EEA carry adequacy, Data Privacy Framework or standard contractual clause safeguards, and disaster-recovery copies sit on BunnyCDN in the EU under vendor-held offline keys; the Pro CDN nonetheless delivers from edge locations in the United States and worldwide, and we found no public information on a security certification held by the vendor itself. 2 7 8 9 16
The E-Commerce Marketer
The chain is unusually well documented for a European buyer: the contracting and processing entity is inweso GmbH in Switzerland with company number CHE-412.131.272, personal data is stored primarily in Switzerland and the EEA on AWS in Ireland, business email sits with Hostpoint in Switzerland, encrypted disaster-recovery copies sit on BunnyCDN Storage in the EU, and a published data processing agreement runs under Swiss law with Zurich jurisdiction and transfers covered by standard contractual clauses. Subprocessors are listed in the privacy policy by name and several with locations (AWS Ireland, Anthropic Ireland, BunnyCDN EU, Hostpoint Switzerland), but the locations of other engine and payment providers are not stated, and the certifications shown are the host's rather than the vendor's own with their scope. 2 7 8 9 16
The Skeptic
A Swiss contracting entity with a company number and named data protection officer, a published DPA under Swiss law with Zurich courts, hosting named as AWS in Ireland, disaster-recovery copies encrypted under vendor-held offline keys on BunnyCDN in the EU, and a subprocessor list in the privacy policy with locations for several of them. Switzerland is not the EU, the captured ISO 27001 list is the hosting provider's, the Pro CDN reaches United States edge locations, and the machine translation and LLM providers are named without their own locations beyond the general adequacy and contractual-clauses language. 2 7 8 9 16
Pricing transparency
panel disagrees
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
Every tier is public and flat monthly — Free at $0/mo, Starter at $7/mo up to Enterprise at $199/mo — with no per-seat or per-word fees, a free tier with stated word, language and CDN download limits, AI credits included in paid plans and backups sold as a fixed monthly add-on, so the base annual cost is simple arithmetic. The pricing page details only the Free plan's limits though, and we found no public information on the paid tiers' word or download limits, on overage handling, or on the actual price of the backup add-on. 1 5 6 11 17
The App Developer
Every tier is public and priced flat per month — FREE at $0, STARTER at $7, STARTER-PLUS at $19, GROWTH at $49, PROFESSIONAL at $99, PROFESSIONAL-PLUS at $149 and ENTERPRISE at $199, with the free tier's 100K CDN downloads and 2,000 words stated, AI credits included in paid plans, and the backups add-on sold at a fixed monthly price. Cancellation channels, auto-renewal and the refund policy are published. We found no public information on the volume and user limits each paid tier covers, extra AI credit pricing, or VAT treatment, so the real annual cost is not fully computable from the captured pages. 1 5 6 11 17
The In-House Document Translator
The ladder is public and refreshingly simple: Free at $0 with 100K standard CDN downloads a month, 2,000 words, 2 languages and 1 user, then STARTER at $7 /mo, STARTER-PLUS at $19, GROWTH at $49, PROFESSIONAL at $99, PROFESSIONAL-PLUS at $149 and ENTERPRISE at $199, each billed monthly, flat with no per-seat or per-word charges, a 14-day full-feature trial with no card, and cancellation from the in-app Billing tab. The fine print is stated outright: automatic renewal, refunds at the vendor's sole and absolute discretion with no prorated refunds, price changes on 10 days' notice. What I could not compute from these pages: what each paid tier includes in words or downloads, how many AI credits a plan carries, the price figures of the backup add-ons beyond "fixed monthly", or VAT treatment. 1 5 6 11 17
The Data Protection Officer
Seven tiers are public from a free plan to $199 /mo billed monthly, with the free tier's limits spelled out, a flat monthly model without per-seat or per-word charges, and a 14-day full-feature trial without credit card. I still could not compute a real annual cost: the paid tiers' word, language and user inclusions, overage handling, the monthly figure of the backup add-on, and the tier that carries single sign-on are not stated on the captured pages. 1 5 6 11 17
The E-Commerce Marketer
The prices are fully public and flat — a free tier at $0 /mo with 100K standard CDN downloads/mo, 2,000 words, 2 languages and 1 user, then STARTER $7 /mo, GROWTH $49 /mo up to ENTERPRISE $199 /mo billed monthly, with no per-seat or per-word charges, a 14-day trial without a credit card, in-app cancellation and backups as a fixed-monthly add-on. What I cannot compute is the cost at my catalogue size: the volume limits are documented only for the free tier, and we found no public information on overage handling, AI credit volumes per plan, the pricing of the usage-based subscriptions, or VAT treatment. 1 5 6 11 17
The Skeptic
Seven tiers priced in public, from a free plan with its limits spelled out to "$199 /mo billed monthly" at Enterprise, flat monthly billing with no per-seat or per-word charges, a 14-day trial without a card, and backups as a fixed-monthly add-on. What I cannot compute from the captured pages: what each paid tier includes, how the AI credits scale or cost beyond inclusion in paid plans, overage handling, and VAT treatment. 5 6 11 17
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 | — | uncited Report an error |
| Open source | Not determined | — | 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 Locize
Is Locize European?
Yes, though not from the EU. whats-best.ai classifies Locize as UK / wider Europe.
Where does Locize store data?
The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention Ireland as hosting location, per the vendor’s page captured 1 Nov 2026.
Does Locize have a free plan?
Yes. Locize has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Locize?
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: Locize 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 — Legal entity, Hosting location, Data processing agreement. 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.
- 2 compliance 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
- 2 integrations 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
- 2 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
- 2 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
- 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
- 1 subprocessors 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (18)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.locize.com Checked 1 Nov 2026 Details →
- 2 Company page (Swiss ownership) www.locize.com Checked 1 Nov 2026 Details →
- 3 Documentation www.locize.com Checked 1 Nov 2026 Details →
- 4 Documentation (MCP integration) www.locize.com Checked 1 Nov 2026 Details →
- 5 Pricing page www.locize.com Checked 1 Nov 2026 Details →
- 6 Terms of service www.locize.com Checked 1 Nov 2026 Details →
- 7 Privacy policy www.locize.com Checked 1 Nov 2026 Details →
- 8 Data processing agreement (dpa) www.locize.com Checked 1 Nov 2026 Details →
- 9 Security / trust page www.locize.com Checked 1 Nov 2026 Details →
- 10 Machine translation & AI quality — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 11 Machine translation & AI quality — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 12 Translation memory, terminology & review workflow — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 13 Translation memory, terminology & review workflow — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 14 Integrations, file formats & developer tools — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 15 Integrations, file formats & developer tools — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 16 Confidentiality of translated content — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 17 Data export, portability & self-hosting — found from sitemap www.locize.com Checked 1 Nov 2026 Details →
- 18 Data export, portability & self-hosting — found from sitemap www.locize.com Checked 1 Nov 2026 Details →