Translation & Localization
POEditor
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Code Whale Inc. · poeditor.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.
POEditor at a glance
- Vendor
- Code Whale Inc.
- Headquarters
- Incorporated in United States source, captured 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 POEditor 2.5/5, the mean of 6 judges. POEditor, run by Code Whale Inc. 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
POEditor, run by Code Whale Inc. of Jeffersonville, Indiana, is an online localization platform for software strings. Its strongest areas are workflow and review and integrations and formats: translation memory, a central glossary, automated QA, proofreader roles, human translation ordered from integrated providers, a documented REST API with an OpenAPI specification, repository sync with GitHub, GitLab, Bitbucket and Azure Repos, webhooks and an official MCP server. Machine translation covers Google, Microsoft and DeepL plus AI translation on your own key. The weakest scores are portability and exit and sovereignty, both at 4: we found no public information on exporting translation memory as TMX or the glossary as TBX, and the non-European engines and LLM providers sit in the chain with no stated safeguard while the data processing agreement is available only on request. Pricing transparency scored 5-6: five tiers run from $0 to $221 per month, but the pages do not state what happens past a tier's string limit, which tier carries single sign-on, or VAT treatment. Scores cluster within a point on every criterion.
Speaks for it
- Translation memory, central glossaries, automated QA checks and a flexible proofreading stage are documented
- A documented REST API with an OpenAPI specification, error codes and throttling, plus repository sync with GitHub, GitLab, Bitbucket and Azure Repos
- Five pricing tiers are published with exact monthly figures and string limits, from $0 with 1,000 strings to $221 per month with 100,000
- AI translation runs on your own OpenAI, Anthropic, Google, Azure or AWS key, with the stated position that tokens are never marked up
- A 10-day trial requires no credit card, and software with an OSI-approved license can use the platform free of cost
Held against it
- Portability and exit scored 4: we found no public information on exporting translation memory as TMX or the glossary as TBX
- Sovereignty scored 4: the contracting entity is Code Whale Inc. of Jeffersonville, Indiana, and the data processing agreement is available only on request
- The privacy policy asks users to redact personal data from strings before loading them, and no retention period for translated strings is documented
- The pages do not state what happens when a tier's string limit is exceeded, which tier includes single sign-on, or how VAT is treated
- We found no public information on a command-line client, official SDKs, over-the-air app delivery or a public status page
Best for
- You localize app or website software strings and want repository sync with GitHub, GitLab, Bitbucket or Azure Repos wired into your build pipeline
- You want a choice of engine — Google, Microsoft or DeepL — or AI translation billed directly on your own OpenAI, Anthropic, Google, Azure or AWS key with no token markup
- Your project carries an OSI-approved license and qualifies for free use of the platform
- You want published prices before committing, from the Free tier at $0 with 1,000 strings up to Enterprise at $221 per month with 100,000
Avoid if
- Your procurement requires a European contracting entity — ask the vendor: the public pages we read do not show it
- Your strings contain personal data you cannot redact before loading, since the privacy policy puts the redaction task on the customer
- You translate Word, PowerPoint, PDF or InDesign documents that must keep their layout: the published format list stops at software strings and spreadsheets
- You expect to move your translation memory and glossary in TMX or TBX at exit: the published export format list includes neither format
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3 of 5 |
| Translation memory, terminology & review workflow | 3.5 of 5 |
| Integrations, file formats & developer tools | 3.5 of 5 |
| Confidentiality of translated content | 3 of 5 |
| Data export, portability & self-hosting | 2 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 of 5 |
Machine translation & AI quality
Show reasoningHide reasoning
How this is scored
What the machine translation does and how well it is controlled: the languages and language pairs covered, the engine (own neural or LLM model, or a choice of third-party engines such as DeepL, Google, Microsoft or an LLM), glossaries and formality applied during translation, document translation that keeps the layout (Word, PowerPoint, PDF, InDesign), custom or adaptive models trained on the customer's own translations, automatic quality estimation or scoring, and published evaluations of translation quality.
0 — No machine translation of any kind, and no way to connect an engine.
3 — Machine translation is offered or one engine can be connected; languages, glossary use and quality controls are basic or not described.
5 — Machine translation for the major European and world languages with the list published, glossaries applied during translation, a formality or tone setting, document translation that keeps formatting for common office formats, and either an own engine or a choice of several named engines.
8 — Custom or adaptive models that learn from the customer's translation memory or corrections, automatic quality estimation per segment with a threshold that routes weak segments to human review, LLM-based translation with style guides and context, engine selection per language pair stated, and a published quality evaluation with its method.
10 — Translation quality that an organisation can measure and steer: evaluations against named benchmarks or blind human review published with their method, quality estimation calibrated and explained, custom models with their training data and isolation documented, and every machine-translated segment traceable to the engine, model version and glossary that produced it.
The Localization Manager
Three named engines (Google, Microsoft, DeepL) plus bring-your-own-key LLMs from OpenAI, Anthropic, Google, Azure and AWS, with per-project instructions every AI translation follows and an Edit-with-AI control for formal or shorter output — that is real steering, and the language list with 270+ codes is published. For a documentation-heavy release cycle, we found no public information on document translation that keeps layout, custom models learning from my own corrections, or a published quality evaluation with its method. 1 3 5 6 10 11
The App Developer
As a buyer I get a real choice of engines: Google, Microsoft and DeepL in the machine translation API, plus OpenAI, Anthropic, Google, Azure and AWS through my own LLM key with no token markup, per-project instructions the AI must follow, and an Edit-with-AI rephrase to formal or shorter. The language list is published with codes (270+ languages), and a feature called AI Quality Evaluation appears in the plan list, but the captured pages describe no quality estimation thresholds, no custom models trained on my own translations, and no document translation that keeps layout. 3 5 10 6 1
The In-House Document Translator
Several named engines are on offer — Google, Microsoft and DeepL — plus LLM translation through our own API key for OpenAI, Anthropic, Google, Azure or AWS, with per-project instructions, an Edit with AI option for formal or rephrased output, and a published language list down to regional variants. For my contracts the picture is thinner: the formats are software strings such as JSON, XLIFF and RESX, and we found no public information on Word or PDF document translation that keeps a layout, on custom models trained on our corrections, or on a published quality evaluation with its method — the AI Quality Evaluation feature is named on the pricing page but never described. 1 3 5 6 10
The Data Protection Officer
Machine translation through Google, Microsoft and DeepL plus AI translation on the customer's own key for OpenAI, Anthropic, Google, Azure or AWS is documented, with a published list of 270+ languages, per-project instructions and an Edit-with-AI formality option. An AI Quality Evaluation feature is named, but we found no public information on how quality is measured, engine selection per language pair, or document translation that keeps office formatting. 1 3 5 6 10
The E-Commerce Marketer
DeepL, Google and Microsoft are named machine translation engines, I can add my own OpenAI, Anthropic, Google, Azure or AWS key, set project-wide tone instructions, and Edit with AI can make a string shorter, formal or rephrased — exactly how I would rescue a bad product name. The supported-language list is published down to regional variants like Spanish for Latin America. We found no public information on custom models trained on my corrections, on how the advertised AI Quality Evaluation works, or on a published quality study. 1 3 5 6 10
The Skeptic
Google, Microsoft and DeepL machine translation plus AI translation on your own API key for OpenAI, Anthropic, Google, Azure or AWS, with a published list of 270+ languages, glossaries applied, per-project AI instructions and an edit tool for tone and formality — the engine choice and control are real and named. What keeps it from the top: the 'AI Quality Evaluation' feature appears by name with no method described, there is no published evaluation of translation quality, and we found no public information on custom models trained on your translations or engine selection per language pair. The format list stops at software strings and spreadsheets; we found no public information on document translation that keeps the layout of Word, PowerPoint, PDF or InDesign files. 1 3 5 6 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
This is the heart of my checklist: translation memory with history, glossaries for consistency, automated QA catching broken placeholders, punctuation and markup, proofreading stages, contributors and proofreaders assigned per language, screenshots and comments for context, an activity log and per-user stats — plus ordering from integrated LSPs and custom no-code workflows. The gap to the top is governance depth: we found no public information on QA rules that block a release, translation-memory penalties and priorities, or cost reporting per vendor and language. 1 2 3 5 6 11
The App Developer
This is a proper ongoing process: Translation Memory and History, glossaries assigned to projects, automated QA that catches broken placeholders, tag markup and punctuation, a flexible proofreading stage, contributor/proofreader/administrator roles assigned per language, comments and screenshots, custom no-code workflows, and even ordering human translations from integrated language providers inside the platform. What the pages do not show is an in-context editor for apps, configurable blocking QA rules, a named linguistic quality framework, or cost reporting per language. 2 6 5 3 1 11
The In-House Document Translator
Translation memory, a central glossary assigned to projects, automated QA for placeholders, punctuation and markup, a proofreader role, comments, screenshots and contributors assigned per language are all documented, and professional human translation can be ordered from integrated agencies inside the product with quotes returned there. It stops short of the full enterprise process: we found no public information on configurable blocking QA rules, memory and termbase shared across projects with penalties and priorities, or cost reporting per language. 1 2 5 6 11
The Data Protection Officer
Translation memory with history, a central glossary, proofreader and administrator roles, automated placeholder and terminology QA, comments with screenshots, contributors assigned per language, and ordering from integrated language providers are all documented. We found no public information on quality-based routing, per-project blocking QA rules, cross-project memory sharing, or cost reporting per language. 1 2 5 6 11
The E-Commerce Marketer
Translation memory, a central glossary, automated QA for broken placeholders, punctuation and markup, a proofreading stage with proofreader roles, per-language contributors, screenshots and comments, and ordering human translation from integrated language providers with quotes are all described — that covers my translate-in-days-then-fix-by-hand reality. Custom workflows and per-project AI style instructions are also listed. We found no public information on configurable blocking QA rules, a visual in-context editor for a website, or cost reporting per language. 1 2 5 6 11
The Skeptic
Translation memory with history and backups, a central glossary assigned to projects, proofreading stages, automated QA checks catching mismatching punctuation, broken placeholders and markup, contributors and proofreaders assigned per language, comments and screenshots, audit logs, stats per contributor, and ordering human translation from integrated language service providers — that is the working core of a managed process. We found no public information on QA rules configurable per project with blocking behaviour, in-context editing against a live app or website, memory and termbase penalties and priorities, or cost reporting per language. 1 2 3 5 6 11
Integrations, file formats & developer tools
Show reasoningHide reasoning
How this is scored
How content gets in and out: the file formats supported (XLIFF, PO, JSON, YAML, Android XML, iOS strings and xcstrings, Office documents, InDesign), a REST API and CLI, SDKs and over-the-air updates for apps, Git repository sync (GitHub, GitLab, Bitbucket) and CI pipelines, connectors for CMS, shop and design tools (WordPress, Contentful, Shopify, Figma), browser and office add-ins, webhooks, and a JavaScript snippet or proxy for website translation.
0 — No documented way to get content in or out except typing or pasting by hand.
3 — File upload and download or a basic API; formats, repository sync and connectors are basic or not described.
5 — A documented REST API, a list of supported file formats covering the common software and document formats, sync with at least one Git host or CI, and connectors or plugins for several named CMS, shop or design tools.
8 — A CLI and SDKs for named platforms, over-the-air updates for mobile or web apps, Git sync with branching, webhooks, connectors for the main CMS, shop, design and support tools, office or browser add-ins, a public status page, and API limits documented.
10 — Integration that scales across an organisation: an API covering every function of the product with versioning and SDKs, an app or connector framework third parties build on, continuous localization in CI with pull requests opened automatically, and every connector documented with its limits and the fields it syncs.
The Localization Manager
Twenty-eight export formats spanning XLIFF, xcstrings, Android strings, PO and Excel, sync with GitHub, GitLab, Bitbucket and Azure Repos including pull-request presets, webhooks and callbacks, a WordPress plugin, Figma, Slack and Teams, and an API with an OpenAPI spec, documented error codes, throttling and request examples in thirteen languages — enough for my repo-to-release loop. We found no public information on a CLI, official SDKs, over-the-air delivery for mobile apps, or a public status page. 1 2 3 5 12
The App Developer
This is nearly my wish list: a documented REST API with an OpenAPI specification, error codes and throttling rules, a format list that actually includes xcstrings, stringsdict, Android strings, YAML, JSON and XLIFF, Git sync with GitHub, GitLab, Bitbucket and Azure Repos plus webhooks, callbacks and pull request presets, and Figma, WordPress, Slack and Teams connectors plus an official MCP server. What keeps me scripting instead of installing: we found no public information on a CLI, official SDKs beyond user-contributed libraries, over-the-air updates for mobile apps, or a public status page. 5 12 2 3 11
The In-House Document Translator
A documented REST API with an OpenAPI specification, error codes, throttling limits and request examples in a dozen languages, more than twenty string formats including XLIFF, JSON, RESX, iOS and Android strings, sync with GitHub, GitLab, Bitbucket and Azure Repos plus Figma and a WordPress plugin, webhooks, callbacks, pull-request presets and an MCP server for AI tools. We found no public information on a command-line client, over-the-air app updates, or browser or office add-ins, which is what would take this to the top of the scale. 2 3 5 12
The Data Protection Officer
A documented REST API with an OpenAPI specification, error codes and throttling rules covers projects, terms, translations and contributors, and more than twenty formats including XLIFF, JSON, YAML, Android strings and iOS xcstrings are supported, with sync to GitHub, GitLab, Bitbucket and Azure Repos, webhooks, pull-request presets, WordPress and Figma connectors and Slack or Teams notifications. We found no public information on official SDKs, a CLI, over-the-air delivery or a public status page. 2 3 5 12
The E-Commerce Marketer
A fully documented REST API with an OpenAPI specification, rate limits, error codes and code examples, more than twenty software formats from XLIFF and xcstrings to Android strings and YAML, sync with GitHub, GitLab, Bitbucket and Azure Repos including pull-request presets, webhooks, a WordPress plugin, Figma and Slack or Teams. As a Shopify shop owner with no developer, we found no public information on a Shopify connector, an official CLI or SDKs — only user-contributed libraries — so wiring my shop to it would be manual work. 2 3 5 11 12
The Skeptic
A documented REST API with an OpenAPI specification and request examples in thirteen languages, twenty-seven export formats including XLIFF, XLIFF 1.2, xcstrings and Android strings, repository sync with GitHub, GitLab, Bitbucket and Azure Repos with pull-request presets, plus Figma, WordPress, Slack, Microsoft Teams, webhooks, callbacks and an official MCP server, with throttling and error codes documented. We found no public information on a CLI, official SDKs (only user-contributed libraries), over-the-air updates for apps, browser or office add-ins, or a public status page behind the claimed 99.9%+ uptime. 1 2 3 5 12
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 foundations are stated: TLS, encryption at rest, ISO 27001, a DPA available on request, single sign-on in the feature list, audit logs, granular roles, and a clear statement that the vendor itself never trains on customer data, with the engines and LLM providers named. I hold it back because the privacy policy assumes localization strings carry no personal data and asks me to redact before loading, and we found no public information on retention of translated texts, switching third-party AI processing off per project, or zero-retention terms with the LLM providers. 1 3 5 6 9 11
The App Developer
The vendor states plainly that it never trains on customer data, encrypts in transit and at rest, offers a data processing agreement on request, names the machine translation engines and lets me bring my own LLM key, lists audit logs and single sign-on, and claims ISO 27001 certification without stating its scope. Two things hold me back: the privacy policy asks users to redact personal data from strings before loading them because content may go to third-party translation services, and no retention period for translated texts or zero-retention terms with the LLM providers is documented. 3 1 5 9 6
The In-House Document Translator
There is a written statement that POEditor itself never trains on our data, TLS and at-rest encryption, named machine translation engines and LLM providers, single sign-on, audit logs, roles and an ISO 27001 claim, with a data processing agreement available on request. For a draft contract that is not enough: retention of translated strings is answered only by deleting the account, we found no public information on switching third-party AI off per project or on zero-retention terms with the named LLM providers, and the privacy policy instead asks me to redact personal data before loading content. 1 3 5 6 9
The Data Protection Officer
The statement that POEditor itself never trains on your data, TLS and at-rest encryption, ISO 27001, a data processing agreement on request, audit logs and single sign-on are documented, and the LLM link runs on the customer's own API key so the provider relationship stays with the customer. We found no stated retention period for translated strings, no zero-retention terms with the named engines or LLM providers, and no scope for the certification; the privacy policy also puts the burden of redacting personal data on the customer before strings are loaded. 1 3 6 9 11
The E-Commerce Marketer
The pages state that POEditor itself never trains on my data, TLS in transit and encryption at rest, ISO 27001 certification, audit logs and a data processing agreement available on request, with the third-party engines and LLM providers named and AI billed through my own key. Single sign-on appears in the feature list. We found no public information on how long translated strings are retained beyond account deletion, on the certification's scope or on zero-retention terms with the LLM providers, and the privacy policy asks users to redact personal data before loading strings. 1 3 6 8 9 11
The Skeptic
'POEditor itself never trains on your data' is a clear statement, the third-party engines are named — Google, Microsoft, DeepL, plus OpenAI, Anthropic, Google, Azure and AWS billed on your own API key — TLS and encryption at rest are claimed, single sign-on and audit logs are listed, and a data processing agreement is available on request. The privacy policy puts the burden on the customer, telling them to redact personal data before loading strings because content may be sent to third-party translation services, and processing runs only until you delete your account. We found no public information on switching third-party processing off per project, zero-retention terms with the LLM providers, or the scope of the claimed ISO 27001 certification. 1 3 5 6 9
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
All translations and terms come out through the API in XLIFF, CSV, JSON, PO and more, with filters, and the pages state customers own their data and can end processing by deleting the account. For an exit audit, we found no public information on translation memory export as TMX or glossary export as TBX, a documented migration path from a named competitor, or the fate of every asset when a contract ends. 5 8 9 12
The App Developer
Every language exports in 27 formats including XLIFF, CSV and XLS, the API can read all terms and translations, and the terms state I own my data, with account deletion ending processing of personal information. But we found no public information on exporting the translation memory as TMX or the glossary as TBX, on a documented migration path from another tool, or on what happens to project content on termination, and no self-hosted edition I could run myself if the vendor changes course. 12 8 9 5
The In-House Document Translator
Terms and translations export in more than twenty formats including CSV and XLIFF over the API, the API can read everything back, and the terms state we own our data, with personal information removed when the account is deleted. We found no public information on exporting the translation memory as TMX or the glossary as TBX, on importing memory from another tool, on the return or deletion of translation data at the end of a subscription, or on a self-hosted edition. 5 8 9 12
The Data Protection Officer
Customer ownership of the data and deletion when the account is deleted are stated, and terms and translations can be exported through the API in many formats including XLIFF and CSV. We found no public information on translation memory export as TMX, glossary export in a terminology format, import from another translation tool, or what is returned when a contract ends. 5 8 9 12
The E-Commerce Marketer
Every project language can be exported through the API in open interchange formats such as XLIFF, CSV and JSON with filters, terms and translations are readable via the API, and the pages state that I own my data and personal data is deleted with the account. We found no public information on exporting the translation memory or glossary in TMX or TBX, on a documented migration path from another tool, or on a self-hosted edition. 5 8 9 12
The Skeptic
Export runs through a documented API in twenty-seven formats including XLIFF and CSV, with filters for translated, fuzzy and proofread strings, and XLIFF import is documented in detail; the terms state you own your data and the account can be deleted to terminate. But the published format list contains neither TMX nor TBX — the formats another translation tool would want — and we found no public information on exporting the translation memory and glossary as such, a migration path from named competitors, or what project data is returned or deleted on termination beyond personal information. 8 9 12 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where texts are translated, stored and processed, and who the subprocessors are (hosting, machine translation engines, LLM providers, CDN for over-the-air delivery, support and payment tools). Independently sourced by the sovereignty pipeline; translated texts often hold personal data and trade secrets, so the whole chain counts, including the engines a TMS calls. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (machine translation or LLM providers, CDN, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations including the engines and LLM providers, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every text on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, engine and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Localization Manager
The contracting entity is Code Whale Inc. of Jeffersonville, Indiana, while the vendor's own pages state hosting "on our own physical infrastructure within the European Union" and storage in EU data centres; some subprocessors are named (Stripe for payments, Amazon SES for email, anonymised Google Analytics, UserVoice) and ISO 27001 is claimed. The engines and LLM providers in the translation chain are US companies with no stated safeguard, the DPA exists only on request, and we found no public information on an EU contracting entity or EU representative. 1 3 5 7 8 9
The App Developer
The contracting entity is Code Whale Inc. of Jeffersonville, Indiana, but the hosting claim is unusually concrete: own physical infrastructure inside the European Union, no third-party clouds, data in EU data centres. The rest of the chain is thinner — the data processing agreement is only available on request, subprocessors such as Amazon SES, Google Analytics, Stripe and UserVoice appear without locations, and the machine translation engines and LLM providers are non-European with no stated safeguard; we found no public information on an EU representative or a self-hosted edition. 8 7 1 9 5 3
The In-House Document Translator
The contracting entity is Code Whale Inc. of Jeffersonville, Indiana, while the vendor's pages state storage on its own physical infrastructure in EU data centres with no third-party clouds. Amazon SES, Google Analytics, UserVoice and Stripe are named as subprocessors but without locations, the translation engines and LLM providers that see the text sit in the chain with no documented safeguard, the data processing agreement exists only on request, and we found no public information on an EU contracting entity or representative. 1 3 5 7 8 9
The Data Protection Officer
Hosting is documented unusually strongly as the vendor's own physical infrastructure in the European Union with no third-party clouds, and subprocessors such as Stripe, Amazon SES, Google Analytics and UserVoice are named. The contracting and operating entity is Code Whale Inc. of Jeffersonville, Indiana, with no documented European entity or representative, and the machine translation engines and LLM providers are named without locations or stated safeguards; the data processing agreement is available only on request. 1 3 5 8 9
The E-Commerce Marketer
The homepage and privacy policy state that all data is stored on the vendor's own physical infrastructure in EU data centres with no third-party clouds, and ISO 27001 is claimed — good news for a Munich shop. The contracting entity, though, is Code Whale Inc. of Jeffersonville, Indiana, and the visible chain includes Stripe for payments, Amazon SES for email and Google Analytics; we found no public information on an EU contracting entity or EU representative. 1 7 8 9
The Skeptic
The contracting entity is Code Whale Inc. of Jeffersonville, Indiana, while the vendor claims hosting 'on our own physical infrastructure within the European Union' with data stored in EU data centres — a claim on the vendor's own pages that we cannot independently verify. Some subprocessors are named — Stripe for payments, Amazon SES for email, Google Analytics, UserVoice, and Google, Microsoft and DeepL for machine translation — but with no locations, and no EU representative is documented. The data processing agreement is available only on request rather than published, which leaves the chain asserted rather than evidenced. 1 5 7 8 9
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
Five tiers sit in public with exact figures and string limits — Free at $0 with 1000 strings, unlimited projects and up to 5 contributors, Start at $17 per month for 3000 strings, Plus $51, Premium $136, Enterprise $221 for 100 000 — plus a 10-day automatic trial, free use for OSI-approved open source, and AI translation costs paid directly to your own LLM provider. What stops me computing a real annual budget: we found no public information on what happens when string counts pass a tier's limit, which tier carries single sign-on, or VAT treatment and any minimum term beyond the billed-in-advance, non-refundable terms. 3 6 8
The App Developer
The ladder is public and clean: $0 for 1000 strings, then $17, $51, $136 and $221 per month for 3000, 10000, 30000 and 100000 strings, with a 10-day trial needing no card, upgrade proration and non-refund terms stated, and AI translation paid directly to my own LLM provider with no token markup. What I cannot compute from the pages: what happens when I exceed a tier's string limit, which tier carries single sign-on, and any annual, VAT or minimum-term treatment. 6 3 8
The In-House Document Translator
Five tiers are published with exact prices and string limits — Free at $0 per month with 1,000 strings, Start at $17 per month with 3,000, Plus at $51 per month with 10,000, Premium at $136 per month with 30,000, Enterprise at $221 per month with 100,000 — plus a 10-day trial without a card, prorated upgrades, a stated no-refund policy, and AI translation costs paid directly to our LLM provider through our own key with no token markup. What the pages leave open is what happens when strings exceed a tier, whether single sign-on carries its own price, and VAT or minimum term. 3 6 8
The Data Protection Officer
Every tier is public with its monthly price and string limit — Free at $0 per month with 1 000 strings, Start at $17 per month with 3 000, Plus at $51 per month with 10 000, Premium at $136 per month with 30 000 and Enterprise at $221 per month with 100 000 — and AI translation is billed through the customer's own LLM key with the statement that POEditor never marks up tokens. What happens beyond the string limit, which tier includes single sign-on, contributor limits on higher tiers and VAT treatment are not stated, so a full annual cost is not computable. 3 6 8
The E-Commerce Marketer
Five public tiers run from a free plan with 1,000 strings and no card up to $221 per month for 100,000 strings, priced per string, so I can see that a growing catalogue steps from $17 to $51 to $136 per month — the cost curve I need before spring. Upgrade proration, cancellation, non-refundable advance billing and free use for OSI-licensed open source are spelled out, and AI translation costs go straight to my own LLM provider key with no token markup. We found no public information on what happens when the string limit is exceeded, on which tier includes single sign-on, or on how VAT is treated. 3 6 8 13
The Skeptic
Five tiers are public with prices and string limits — Free $0 per month with 1,000 strings and 5 contributors, Start $17 per month for 3,000 strings, Plus $51 per month for 10,000, Premium $136 per month for 30,000, Enterprise $221 per month for 100,000 — with a ten-day no-card trial, free use for OSI-licensed open-source projects, upgrade proration, cancellation terms and a strictly no-refund policy all stated, and AI token costs billed directly by your own LLM provider with no markup. We found no public information on what happens above 100,000 strings, which tier carries single sign-on, or VAT treatment — a buyer above the top tier still cannot compute their annual cost. 3 6 8
European sovereignty — proven facts
1 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 | Incorporated in US ⚠ unverified | 0/2 pts | 8 Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined ⚠ unverified | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about POEditor
Is POEditor European?
No. whats-best.ai classifies POEditor as Rest of world. Its vendor, Code Whale Inc., is incorporated in United States, per the vendor’s page captured 1 Nov 2026.
Where does POEditor store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does POEditor have a free plan?
Yes. POEditor has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to POEditor?
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: POEditor 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, Hosting location, Open source. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The pages give only a company address, with no commercial register or state of incorporation named.
- 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.
- 27 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
- 3 subprocessors 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 product 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 (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage poeditor.com Checked 1 Nov 2026 Details →
- 2 Features page poeditor.com Checked 1 Nov 2026 Details →
- 3 Features page (AI localization) poeditor.com Checked 1 Nov 2026 Details →
- 4 Integrations page poeditor.com Checked 1 Nov 2026 Details →
- 5 API documentation poeditor.com Checked 1 Nov 2026 Details →
- 6 Pricing page poeditor.com Checked 1 Nov 2026 Details →
- 7 Legal notice (company details) poeditor.com Checked 1 Nov 2026 Details →
- 8 Terms of service poeditor.com Checked 1 Nov 2026 Details →
- 9 Privacy policy poeditor.com Checked 1 Nov 2026 Details →
- 10 Machine translation & AI quality — found from sitemap poeditor.com Checked 1 Nov 2026 Details →
- 11 Translation memory, terminology & review workflow — found from sitemap poeditor.com Checked 1 Nov 2026 Details →
- 12 Integrations, file formats & developer tools — found from sitemap poeditor.com Checked 1 Nov 2026 Details →
- 13 Integrations, file formats & developer tools — found from sitemap poeditor.com Checked 1 Nov 2026 Details →