Translation & Localization
Localazy
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Localazy s.r.o. · localazy.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.
Localazy at a glance
- Vendor
- Localazy 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 Localazy 3/5, the mean of 6 judges. Localazy, a localization platform from Localazy 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
Localazy, a localization platform from Localazy s.r.o. of Brno, is strongest on integrations and formats, a flat 7: a documented REST API with a CLI, Android and iOS SDKs, CI pipelines and claimed 60-plus integrations, though the Shopify, WordPress and Salesforce connectors are Enterprise. Machine translation and workflow and review cluster at 6-7 on four named engines plus Localazy AI, a translation memory and a review gate, with no published language list beyond the claimed 1,100+. Pricing transparency is a flat 5 — tiers run legibly from a free plan at 200 source keys to "$175 /mo", but Localazy credits carry no published price and the captured pages give different figures for words. Portability and exit scores 4-5 and content confidentiality 5-6, with no public information on exporting the translation memory or on whether translations are used to train models. Sovereignty splits the bench 4 to 7: those crediting the Brno entity, Scaleway hosting and a published agreement score high, while those weighing the policy statement that information may be transferred outside the European Union and unstated engine locations score low.
Speaks for it
- Integrations and formats earns the top mark of 7, on a documented REST API with a CLI, Android and iOS SDKs, CI pipelines and claimed 60-plus integrations
- Four named machine translation engines plus Localazy AI are built in, with glossary and style-guide support that varies by engine
- Workflow and review scores 6-7, on a translation memory shared between projects, a glossary validated on save, and review roles with per-language permissions
- Pricing tiers are public with exact figures — a free plan up to 200 source keys, then "$34 /mo", "$78 /mo" and "$175 /mo" — with a 14-day trial and no credit card
- The contracting entity is Localazy s.r.o. of Brno, Czech Republic, with hosting stated as Scaleway and a published data processing agreement
Held against it
- Portability and exit scores 4-5, with no public information on exporting the translation memory as TMX or the glossary as TBX, and retrieval assistance billed "by agreement based on complexity and time"
- We found no public statement on whether customer translations are used to train models, and ShareTM shares translation-memory suggestions across customers' projects
- Machine translation is metered in Localazy credits with no published price, and the price depends on the selected provider
- The policy states information may be transferred outside the European Union, and the captured pages state no engine or subprocessor locations
- Retention is fixed at 24 months after use rather than customer-set, and single sign-on and audit logs sit behind the tailored Enterprise plan
Best for
- You ship apps or websites and want CLI, SDK and CI/CD localization for software formats such as JSON, YAML, XLIFF and Xcode String Catalogs
- You run a translation workflow that needs a shared translation memory, glossary validation on save, and review roles with per-language permissions
- You want to start free — up to 200 source keys with unlimited seats and languages — before stepping to a paid tier
- You want machine translation plus the option to order human translation, human review or human-assisted machine translation on the platform
Avoid if
- You need end-to-end EU confinement of translated text — the policy states information may be transferred outside the European Union, and the engine chain includes Google, Amazon and Azure
- You must control retention yourself — the agreement fixes it at 24 months after use, with backups kept one month
- You localize a Shopify, WordPress or Salesforce site without an Enterprise plan — those connectors are listed as Enterprise
- You translate office documents with layout preserved — the published format list centers on software strings and spreadsheets, and PowerPoint is an Enterprise-assisted service
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3 of 5 |
| Translation memory, terminology & review workflow | 3 of 5 |
| Integrations, file formats & developer tools | 3.5 of 5 |
| Confidentiality of translated content | 3 of 5 |
| Data export, portability & self-hosting | 2.5 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 2.5 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
Four named engines (Amazon Translate, Google Translate, DeepL, Azure Translator) plus their own Localazy AI, with a per-plan provider matrix covering suggestions, batch translation, automations and the API, glossary and style-guide support documented per engine, and batch output that can be sent into review or approved. Localazy AI reuses previous translations, follows instructions and context, and crosses plural variants where the other engines stop. I found no public information on per-segment quality estimation, published quality evaluations, or engine selection per language pair. 1 3 6 11 12
The App Developer
Four named engines — Amazon Translate as the free default, Google, DeepL, Azure — plus Localazy AI, which follows instructions and context and taps into previous translations, with glossary and style-guide support that varies per engine (DeepL glossary only on selected language pairs). The documentation itself notes machine translation currently does not apply to all plurals. We found no public information on automatic quality estimation per segment, engine selection per language pair, or a published quality evaluation with its method. 11 12 3 1
The In-House Document Translator
Four named engines plus their own AI are offered, and the glossary and style guide are applied during translation with term validation, which is exactly how I want our terminology locked. The languages count is published as 1,100+, but we found no public information on translation quality evaluations or automatic quality scoring with routing to human review. The documented file formats are developer and spreadsheet files; we found no public information on Word, PDF or InDesign translation that keeps the layout, which is what my contracts and manuals actually need. 11 12 5 6 10
The Data Protection Officer
Four named third-party engines (Amazon, Google, DeepL, Azure) plus the vendor's own AI are offered, with glossary and style-guide support documented per engine, formality via DeepL, provider choice and review routing in batch settings, and 1,100+ languages advertised. The AI is described as following instructions and tapping into previous translations rather than as a custom model trained on our memory. We found no published quality evaluation or per-segment quality scoring, and office-format support stops at spreadsheets plus a custom Enterprise PowerPoint setup. 1 3 6 10 11 12
The E-Commerce Marketer
Four named engines — Google, DeepL, Amazon and Azure — are built in alongside Localazy AI, which follows instructions, context and previous translations, and glossary and style-guide support is documented per engine, which covers my German, French, Italian, Dutch and Spanish comfortably. The captured pages give a language count of 1,100+ rather than a published list, office-document translation stops at Excel and ODS files with PowerPoint as an Enterprise-assisted service, and we found no public information on per-segment quality scoring or a published quality evaluation. 3 6 10 12
The Skeptic
Localazy AI plus four named engines (Amazon Translate as the default, Google, DeepL, Azure) applied as suggestions, in batches or through automations, with glossary and style-guide support varying by engine and translations routable to review or approval. Beyond a claimed "1,100+" languages we found no published language list, no custom models trained on the customer's own translations, no per-segment quality estimation and no published quality evaluation — and the documentation itself notes machine translation does not apply to all plurals. Solid and controlled, but unmeasured in public. 11 12 3 5 10
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
Translation memory with exact-match reuse and documented sharing between projects, a glossary with term highlighting and validation on save, style guides applied by the AI, and a real review gate: standard translators wait for a Reviewer, Manager or Owner, with language permissions and roles switchable at any time. Human translation, human review and human-assisted machine translation can be ordered on the platform, and automations pre-translate new content into review or approval. I found no public information on fuzzy matching, configurable blocking QA rules, or cost and progress reporting per language or vendor. 1 2 4 5 7 8 12 13
The App Developer
Translation memory with exact-match reuse and sharing between projects, a glossary with term highlighting and validation before saving, language permissions, rule-based automations, and a real review gate — standard Translator submissions wait for a Reviewer, Manager or Owner — cover the daily loop, and professional translation, review or human-assisted machine translation can be ordered directly on the platform. We found no public information on configurable multi-step workflow routing, an in-context visual editor, or per-language progress and cost reporting. 4 5 13 1 8
The In-House Document Translator
A translation memory with exact-match reuse and sharing between projects, a central glossary validated before saving, and a review step where a standard translator's work waits for a reviewer, with language permissions limiting who may touch which language — that is a workable process. Automations, project branching and the ability to order human review or human-assisted machine translation on the platform push it further. We found no public information on task deadlines, configurable blocking checks, or progress and cost reporting per language. 4 5 13 1 12 8
The Data Protection Officer
A translation memory is built automatically, reused on identical text and shareable between projects; a central glossary with term highlighting and pre-save validation, review roles where a standard translator waits for a Reviewer, Manager or Owner, and per-language permissions are all documented. Human translation and review services can be ordered on the platform, priced by word count and target languages, and automations can pre-translate new content and route it to review. The memory is documented as exact-match only, and we found no description of configurable QA checks with blocking rules, fuzzy-match penalties, or quality metrics per translator. 1 2 4 5 7 8 12 13
The E-Commerce Marketer
A translation memory is built in the background, can be shared between projects and reuses exact matches; glossary terms are highlighted and validated on save; and a standard translator's work waits for a Reviewer, Manager or Owner, with language permissions to keep contributors to their languages — the hand-fix path I need for a bad product name. It stops short of a full review shop: we found no public information on fuzzy matching, configurable multi-step workflows, blocking QA rules, or progress and cost reporting per language. 1 4 5 12 13
The Skeptic
Real machinery exists: a translation memory with exact-match reuse that can be shared between projects, a glossary whose terms are highlighted and validated before saving, per-language style guides, and review roles where a standard translator's work waits for a reviewer, manager or owner while a trusted translator is auto-approved, with language-level permissions. Human translation, review and localization testing are ordered inside the platform, and screenshots are managed through the API. We found no public information on what the QA checks actually check, on segment comments, or on progress and cost reporting per language. 4 5 13 1 8 7 12
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
A CLI for uploads and downloads, a REST API with a Postman collection and an npm client, Android and iOS SDKs, GitHub Actions, GitLab CI/CD and Bitbucket Pipelines, plugins for Figma, Webflow, Strapi and Directus, Zendesk and Intercom connectors, and a format list of roughly 27 entries including XLIFF 2.0, Xcode String Catalogs, TMX and CSV; the company page claims 60-plus integrations. I found no public information on over-the-air delivery for apps, a public status page, documented API limits, or browser add-ins. 1 6 7 10
The App Developer
This fits my stack almost exactly: a CLI, an Android Gradle plugin and SDK, an iOS SDK that explicitly names.xcstrings,.strings and.stringsdict, JSON, YAML, PO and XLIFF formats, GitHub Actions, GitLab and Bitbucket CI plus a Bitrise verified step, webhooks, Figma, CMS and helpdesk connectors among 60+ integrations, and a REST API with a Postman collection and an npm client said to wrap the entire API; a language CDN with metadata endpoints handles delivery. We found no public information on a public status page, documented API limits, or pull requests opened automatically, so it stops just short of the top band for me. 6 7 10 1 14
The In-House Document Translator
A documented REST API with a Postman collection and a TypeScript library, a CLI, SDKs for Android and iOS, webhooks, CI setups for GitHub, GitLab and Bitbucket, and sixty-plus integrations including Figma, WordPress, Shopify, Zendesk and Intercom — broad and well documented. The format list is long but aimed at software strings and spreadsheets, and we found no public information on Word documents or InDesign. We also found no public information on a status page or documented API limits. 6 7 10 14 1
The Data Protection Officer
A documented REST API with a TypeScript client and a Postman collection, a CLI, Android and iOS SDKs, GitHub Actions, GitLab CI/CD and Bitbucket Pipelines, webhooks, project branching and a wide format list including XLIFF 1.2 and 2.0, PO, JSON, YAML, RESX and Xcode string catalogs are published. Plugins cover Figma, Strapi, Directus and Webflow, with Enterprise connectors for WordPress, Shopify, PrestaShop and Salesforce. We found no public information on a status page, documented API limits, over-the-air app updates or a browser add-in. 1 6 7
The E-Commerce Marketer
A documented REST API with a TypeScript client, a CLI, Android and iOS SDKs, GitHub Actions, GitLab and Bitbucket pipelines, webhooks, project branching and a long format list from JSON and YAML to PO, XLIFF and Xcode catalogs make the developer side broad, with 60+ integrations claimed. For a shop like mine the catch is that the Shopify, Google Merchant Feed and WordPress connectors are listed as Enterprise, and we found no public information on a browser or office add-in, a public status page, or documented API limits. 1 6 7 10
The Skeptic
Content moves: a documented REST API with a TypeScript client and Postman collection covering projects, files, keys, translations, glossary, screenshots and webhooks, a CLI, Android and iOS SDKs, CI for GitHub Actions, GitLab and Bitbucket, and sixty-plus integrations including official Figma, Strapi, Directus and Webflow plugins plus Enterprise connectors for WordPress, Shopify and Salesforce. The format list is broad — XLIFF 1.2 and 2.0, PO, RESX, Xcode String Catalogs, TMX, YAML, CSV, spreadsheets. We found no public information on documented API limits or a public status page. 7 6 1 10 14
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 published privacy policy doubles as the data processing agreement with Localazy as Data Processor, states 24-month retention after use and one-month backups, TLS in transit and encryption for data workloads, points to a public subprocessor list, and states SOC2 and ISO27001 compliance, while SSO and audit logs come with the Enterprise plan and the third-party engines are named. I found no public information on whether customer content is used to train models, on customer-set retention or deletion immediately after translation, or on switching third-party AI processing off per project or account. 6 8 9
The App Developer
The combined privacy policy and data processing agreement states TLS in transit, encryption for all data access workloads, 24 months retention after use with deletion on request, and a published subprocessor list link, while the Enterprise tier carries SSO and audit logs and the company states ISO 27001 and SOC 2; the engines that see my strings are named and the provider is chosen per task. We found no public information on whether customer texts are used to train models, zero-retention terms with the AI providers, or a retention period the customer sets. 9 8 11 12
The In-House Document Translator
Encryption in transit and at rest, SOC 2 and ISO 27001 stated, a published data processing agreement that a signed one can supersede, audit logs and single sign-on on the Enterprise plan, and the machine translation engines named openly. But we found no public information stating that translated texts are not used to train models — the written promise I need before sending anyone a draft contract — and retention is stated as the period of use plus 24 months, with no immediate deletion after translation or zero-retention terms with the AI providers documented. 9 8 11
The Data Protection Officer
The combined privacy policy and data processing agreement names the Czech entity as processor, states TLS in transit and encryption for data access workloads, fixes retention at 24 months after use with backups kept one month and deletion on request, and links a public subprocessor list; single sign-on and audit logs sit in the Enterprise plan, and ISO 27001 and SOC 2 are stated without scope. The engines our text reaches are named — Amazon, Google, DeepL, Azure and the vendor's own AI — and the provider is selectable per translation task. We found no statement that customer translations are not used to train models, no customer-set retention or zero-retention terms for the AI providers, and a cross-project shared memory (ShareTM) whose contribution terms the captured pages do not spell out. 6 8 9 11 12
The E-Commerce Marketer
The privacy policy doubles as a published data processing agreement, TLS in transit and encryption at rest are stated, SOC 2 and ISO 27001 are claimed, translated data retention is 24 months after use, and the machine translation engines are named. We found no public information on whether customer texts are used for model training, retention is fixed rather than customer-set, third-party AI processing is not shown as switchable, and SSO and audit logs sit on the tailored Enterprise tier. 8 9
The Skeptic
The combined privacy policy and processing agreement names the customer as controller, promises TLS in transit and encryption for data workloads, enforces two-factor authentication, claims ISO 27001 and SOC 2, points to a public subprocessor list and offers deletion on request. But retention is fixed at 24 months after you stop using the service rather than a period you set, retrieval assistance is priced "by agreement based on complexity and time", and we found no public statement on whether your translations train any model — while ShareTM shares translation-memory suggestions across customers' projects. Single sign-on and audit logs sit behind the Enterprise tier. 9 8 12
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
Translation memory can be uploaded in TMX, TMX, CSV and XLIFF sit in the supported format list, the CLI automates downloads of your data, and API endpoints read files, keys, translations, glossary items and screenshots; personal data is deleted on request. I found no public information on translation memory export as TMX or glossary export as TBX or CSV, on a documented migration path from named competitors, or on the return or deletion of assets when a contract ends. 4 6 7 9
The App Developer
I can get my data out: CLI uploads and downloads of project data, an API that reads files, keys, translations, glossary and screenshots, CSV import/export documentation, and TMX upload for bringing an old translation memory in, with deletion on request under the agreement. We found no public information on exporting the translation memory or glossary as TMX or TBX, a documented migration path from named competitors, or a self-hosted edition — a public GitHub repository was captured, but we found no public information confirming the platform itself can be run by the customer. 6 7 17 9 18
The In-House Document Translator
Import of an existing translation memory via TMX is documented, and the API can read project files, keys, translations and glossary items, so content can be pulled out programmatically. But we found no public information on exporting the translation memory as TMX or the glossary as TBX or CSV, or on what is returned or deleted when the contract ends — the memory I build up would sit in their workflow rather than on my machine. 6 7 9 4
The Data Protection Officer
Upload of an existing translation memory in TMX is documented, the CLI and the API can read and download files, translations and glossary items, and deletion of personal data on request is agreed, with retrieval assistance charged by agreement based on complexity and time. We found no public information on export of the translation memory or glossary in open formats, a documented migration path from another tool, or a self-hosted edition. 6 7 9
The E-Commerce Marketer
Translation memory can be imported as TMX, project files and translations are readable through the API and CLI, glossary items are managed by API, and deletion on request is promised. We found no public information on exporting the translation memory or glossary in open formats such as TMX or TBX, on a documented migration path from named competitors, or on data return at termination beyond deletion, with retrieval assistance charged by agreement. 6 7 9
The Skeptic
TMX is documented as a format you upload to bring memory in, and the API reads projects, files, keys, translations and glossary, so a determined engineer can extract content programmatically. We found no public information showing the translation memory exporting as TMX or the termbase as TBX, no documented migration path from named competitors, and no self-hosted edition. Leaving costs extra: retrieval assistance is billed "by agreement based on complexity and time". 6 7 4 9
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 data processing agreement names the contracting entity Localazy s.r.o. of Brno, Czech Republic, hosting is stated as Scaleway, a public subprocessor list exists, and SOC2 and ISO27001 are stated. The captured pages give no location for the hosting or for the machine translation engines in the chain, and the policy says information may be transferred outside of the European Union. 8 9 10
The App Developer
The contracting entity is Localazy s.r.o. of Brno with a Czech registration number, the service is hosted on Scaleway per the agreement, a data processing agreement is published, ISO 27001 and SOC 2 are stated, and there is a public link to an up-to-date subprocessor list. The same agreement states Localazy may transfer information outside the European Union, and the engine chain includes Google, Amazon and Azure, whose locations we found no public information on — so the chain is EU-anchored but not documented end to end. 9 8 11
The In-House Document Translator
The contracting entity is Localazy s.r.o. of Brno in the Czech Republic, the service is stated to be hosted at Scaleway, a processing agreement is published and SOC 2 and ISO 27001 are claimed. The chain still worries me: the machine translation engines include Google, Amazon and Azure, transfers outside the European Union are expressly possible, and we found no public information on a stated safeguard for that or on where the listed subprocessors sit. 9 8 11
The Data Protection Officer
The contracting entity is Localazy s.r.o. of Brno, Czech Republic, with a published data processing agreement, and the hoster is named as Scaleway, but the captured pages do not state where the service runs. The agreement says information may be transferred outside the European Union, the public subprocessor list is linked without captured locations, and the machine translation chain includes Amazon, Google and Azure alongside DeepL and the vendor's own AI. Certifications are stated at company level without their scope. 6 9 11
The E-Commerce Marketer
Localazy s.r.o. is registered in Brno, Czech Republic, the service is hosted on Scaleway, a published data processing agreement exists and SOC 2 and ISO 27001 are stated — a European core I like. The same pages state that information may be transferred outside the European Union, a public subprocessor list is referenced but its entries and locations are not shown in what we captured, and the location of the built-in translation engines is not stated. 8 9 11
The Skeptic
The chain is provably European at the ends: Localazy s.r.o. in Brno as the contracting entity, hosting on the named provider Scaleway, a published processing agreement, and ISO 27001 and SOC 2 claimed alongside a public subprocessor-list link. In the middle it is not: the policy states information may be transferred outside the European Union, translated text is sent to Google, Amazon and Azure engines, and the captured pages state no engine or subprocessor locations and no safeguard for those transfers. 9 10 8 11 12
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
A free plan up to 200 source keys, Professional at $34 /mo ($408 billed annually, 1,000 keys, 12,000 words), Autopilot at $78 /mo, Business at $175 /mo ($2,100 billed annually, 10,000 keys, 68,000 words), a 14-day trial without credit card, and "2 months free" on annual billing, with machine translation covered by included Localazy credits and additional engines tied to the Autopilot plan and above. I found no public information on what happens when a tier's key or word volume is exceeded, on the price of further credits, on the Enterprise plan beyond "Tailored to your needs", or on human translation rates beyond a price that depends on word count and target languages. 1 8 11 12
The App Developer
Four tiers are public with keys and words per band — $34 /mo Professional for 1,000 keys and 12,000 words up to $175 /mo Business for 10,000 keys and 68,000 words — plus a free plan at 200 keys with unlimited seats and languages, two months free billed annually, and a 14-day trial with no credit card. But Enterprise with SSO is "tailored to your needs", AI usage runs on credits for which we found no public figures, machine translation price "depends on the selected provider", we found no public information on what happens when a tier's volume is exceeded, and the pricing page gives both tier word limits and "unlimited projects, words & languages" without explaining how they fit together. 8 11 12
The In-House Document Translator
Tiers are public with exact figures — Professional at $34 /mo, $408 billed annually for 1,000 keys and 12,000 words, Business at $175 /mo, $2,100 billed annually for 10,000 keys and 68,000 words, a free plan up to 200 source keys, and a 14-day Business trial with no credit card. But machine translation is said to depend on the selected provider and to cost credits without published amounts, single sign-on sits on a tailored Enterprise plan, and we found no public information on overage handling or VAT — so the real annual cost for our volume cannot be computed from the pages alone. 8 12
The Data Protection Officer
Tiers are public with exact figures — the free plan up to 200 source keys, Professional $34 /mo, $408 billed annually for 1,000 keys and 12,000 words, Autopilot $78 /mo, $936 billed annually, and Business $175 /mo, $2,100 billed annually for 10,000 keys and 68,000 words — plus a 14-day trial without credit card and two months free on annual billing. Machine translation spend is not computable: credits are the currency, the price depends on the selected provider, human services are quoted by word count and target languages, and Enterprise is tailored. Overage handling, VAT and minimum term are not stated on the captured pages. 8 11 12
The E-Commerce Marketer
Four tiers are public with keys and words per band — free up to 200 keys, then $34 /mo, $78 /mo and $175 /mo with annual totals shown — plus unlimited projects, languages and seats, which protects me when the catalogue grows. What I cannot compute is the rest: what happens past 10,000 keys is not stated, machine translation beyond included credits depends on the selected provider, human translation is priced only by word count and target languages, and Enterprise is tailored. 8 12
The Skeptic
The ladder is unusually legible: a free plan capped at 200 source keys, then "$34 /mo", "$78 /mo" and "$175 /mo" with stated annual totals of "$408", "$936" and "$2,100" and explicit key and word bands, a 14-day trial without a credit card, and two months free annually. The gaps are the ones that bite: nothing on what happens when you exceed a tier, machine translation metered in "Localazy credits" with no published credit price, human translation where the price "depends on the word count and target languages", and single sign-on inside a "tailored" Enterprise plan — and the captured pages give different figures for words, with per-tier caps of 12,000 to 68,000 alongside a claim of "Unlimited projects, words & languages". 8 12 11
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 | — | 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 Localazy
Is Localazy European?
Yes. whats-best.ai classifies Localazy as EU-Made.
Where does Localazy store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Localazy have a free plan?
Yes. Localazy has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Localazy?
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: Localazy 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, 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.
- 29 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 legal 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
- 6 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
- 6 support 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
- 4 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 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
- 1 hosting 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
- 2 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 localazy.com Checked 1 Nov 2026 Details →
- 2 Features page (machine translation) localazy.com Checked 1 Nov 2026 Details →
- 3 Features page (Localazy AI) localazy.com Checked 1 Nov 2026 Details →
- 4 Features page (translation memory) localazy.com Checked 1 Nov 2026 Details →
- 5 Features page (glossary) localazy.com Checked 1 Nov 2026 Details →
- 6 Integrations page localazy.com Checked 1 Nov 2026 Details →
- 7 API documentation localazy.com Checked 1 Nov 2026 Details →
- 8 Pricing page localazy.com Checked 1 Nov 2026 Details →
- 9 Privacy policy and data processing agreement (dpa) localazy.com Checked 1 Nov 2026 Details →
- 10 Company page localazy.com Checked 1 Nov 2026 Details →
- 11 Machine translation & AI quality — found from sitemap localazy.com Checked 1 Nov 2026 Details →
- 12 Machine translation & AI quality — found from sitemap localazy.com Checked 1 Nov 2026 Details →
- 13 Translation memory, terminology & review workflow — found from sitemap localazy.com Checked 1 Nov 2026 Details →
- 14 Integrations, file formats & developer tools — found from sitemap localazy.com Checked 1 Nov 2026 Details →
- 15 Confidentiality of translated content — found from sitemap localazy.com Checked 1 Nov 2026 Details →
- 16 Confidentiality of translated content — found from sitemap localazy.com Checked 1 Nov 2026 Details →
- 17 Data export, portability & self-hosting — found from sitemap localazy.com Checked 1 Nov 2026 Details →
- 18 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →