Redokun
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Runetek S.r.l. · www.redokun.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.
Redokun at a glance
- Vendor
- Runetek S.r.l.
- Headquarters
- Incorporated in Italy source, captured 17 Nov 2026
- Data hosting
- In the EU by default source, captured 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Redokun 2.5/5, the mean of 6 judges. Redokun is a browser-based translation platform from Redokun Srls of Montebelluna, Italy. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Redokun is a browser-based translation platform from Redokun Srls of Montebelluna, Italy. The bench scored it highest on sovereignty, 6-7: documents and translations are stated to be hosted in Ireland and Germany, a published sub-processor list gives each provider's location, and Standard Contractual Clauses cover transfers outside the EEA — though the list places OpenAI, Anthropic, Linode and Postmark in the United States. Machine translation scored 5-6 on named engines — Google Translate, DeepL and ChatGPT — applied with the customer's glossary. Portability and exit scored 3: files return in their original format, but the judges found no public information on memory or glossary export in standard formats, or on data return at termination. Workflow and review and content confidentiality spread 4-6: top scores credit the human-approval loop and written no-training commitments, bottom ones found no public information on automated QA checks or encryption at rest. Integrations and formats held at 4, with the WordPress, Webflow, Storyblok, Shopify and MCP integrations all marked coming soon. Public pricing facts stop at a 14-day free trial and the Basic and Premium plan names.
Speaks for it
- Sovereignty scored 6-7 on an Italian contracting entity, documents and translations stated to be hosted in Ireland and Germany, a published sub-processor list with locations, and Standard Contractual Clauses for non-EEA transfers.
- Translation memory with 100% and fuzzy matches is reused across projects and document types, with a central glossary editable in the editor and automatic term highlighting.
- Translated files, including InDesign.idml, return in the original format with layout intact, and translators need no InDesign license.
- The privacy terms state that documents sent to OpenAI and DeepL via API are processed temporarily and not used to train their models, with a self-serve DPA and a downloadable sub-processor list.
- AI drafts come from the named engines Google Translate, DeepL and ChatGPT, applied with the customer's glossary, an AI Tone of Voice setting, and always presented for human approval.
Held against it
- Portability and exit scored 3, and we found no public information on translation-memory export as TMX, glossary export in a standard format, or data return and deletion at contract end.
- The WordPress, Webflow, Storyblok and Shopify connectors and the MCP server are all marked coming soon, and we found no public information on Git sync, a CLI, SDKs or webhooks.
- The 'up to 90% accurate' figure is published with no stated method, no language list appears on the captured pages, and AI Fine-tuning is named without detail on what it trains on.
- We found no public information on automated QA checks, per-language roles, configurable multi-step approvals, single sign-on, audit logs, or ISO 27001 or SOC 2 certification.
- The captured pages give different names for the AI engines — product pages name Google Translate and ChatGPT, the provider list names OpenAI and DeepL — and the vendor metadata names Runetek S.r.l. while the captured pages name Redokun Srls as the contracting entity.
Best for
- You translate formatted documents — InDesign, Word, PowerPoint, Excel — and need them back in the original layout, with translators needing no InDesign license.
- You want AI pre-translation from named engines applied with your own glossary and terminology, with every AI suggestion presented for human approval.
- You run internal translators, freelancers and agencies in one shared workspace, with a translation memory and glossary reused across projects and document types.
- You are a European buyer weighing an Italian contracting entity, documents and translations hosted in Ireland and Germany, and a self-serve DPA with Standard Contractual Clauses for non-EEA transfers.
Avoid if
- You need live CMS or shop connectors today — WordPress, Webflow, Storyblok, Shopify and the MCP server are all marked coming soon, leaving the documented API (upload files, track progress, download finished documents) as the connection.
- You need to keep your translation memory portable — portability and exit scored 3, the only export signals shown are original-format download and an Export Phrases feature, so obtain export terms in writing before signing.
- You require a processing chain free of United States providers — the sub-processor list places OpenAI, Anthropic, Linode and Postmark in the United States, with Standard Contractual Clauses as the stated safeguard for those transfers.
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 2.5 of 5 |
| Translation memory, terminology & review workflow | 2.5 of 5 |
| Integrations, file formats & developer tools | 2 of 5 |
| Confidentiality of translated content | 2.5 of 5 |
| Data export, portability & self-hosting | 1.5 of 5 |
| European sovereignty | 3.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
Drafts come from several named engines — Google Translate, DeepL or ChatGPT — with the glossary followed automatically, an AI tone-of-voice setting, and pre-translation that combines AI, translation memory and glossary before assignment. Formatting survives the round trip for InDesign, Word, PowerPoint and Excel, and an AI fine-tuning option is named on the Basic and Premium plans, though we found no public information on what it trains on. The "up to 90% accurate" figure is stated without a method, and we found no published language list or per-segment quality scoring. 4 5 6 9
The App Developer
Google Translate, DeepL and ChatGPT generate drafts for every segment, the glossary is followed automatically during AI translation, there is a tone-of-voice setting and an AI fine-tuning option on higher plans, and pre-translation runs at upload. I found no public information on a published language list, per-segment quality estimation routing weak segments to human review, or a quality evaluation with its method — the only figure is the vendor's own claim that suggestions can be up to 90% accurate. 4 5 6 9 2
The In-House Document Translator
Three named engines (Google Translate, DeepL, ChatGPT), the glossary applied to machine translation automatically, a tone-of-voice setting and layout-preserving export for Word, PowerPoint, Excel and InDesign are exactly my daily bread. We found no published list of supported languages, the fine-tuning option is described only as adjusting translations without detail on what it learns from, and the claim of up to 90% accuracy comes without a method. 4 5 6 9
The Data Protection Officer
The captured pages name several engines — Google Translate, DeepL and ChatGPT — applied together with the customer's glossary, a tone-of-voice setting and AI fine-tuning, and document translation keeps the original layout for InDesign, Word, PowerPoint and Excel. We found no public information on a published language list, engine selection per language pair, or a quality evaluation published with its method. 4 5 9
The E-Commerce Marketer
DeepL, Google Translate and ChatGPT are named engines, my glossary is applied automatically during AI translation, there is an AI tone setting, and finished files keep their layout for InDesign, Word, PowerPoint and Excel. I found no published list of languages, the up to 90% accuracy figure is stated with no described method, and AI fine-tuning is named without an explanation of how it works. 1 4 5 6 9
The Skeptic
Three named engines — Google Translate, DeepL and ChatGPT — with the glossary applied to AI output, an AI Tone of Voice setting, and document translation that keeps the InDesign or Office layout intact. "Up to 90% accurate" arrives with no method attached, no language list is published beyond "10, 20, or more languages", and AI Fine-tuning is one line on a features page with nothing about training on the customer's own translations or any quality estimation. Solid engine choice, unproven quality story. 4 5 6 9
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 perfect and fuzzy matches is reused across projects and document types, the glossary is central, editable in the editor and highlighted during work, and AI suggestions are always presented for human approval. Comments, mentions and a live InDesign page preview give translators context, and one dashboard tracks progress across languages for internal translators, freelancers and agencies. We found no public information on automated QA checks for placeholders or tags, on configurable multi-step workflows, on roles per language, or on cost reporting per vendor — the checks that stop a broken placeholder before it ships are what I would miss most. 1 5 6 7 9
The App Developer
Translation memory with perfect and fuzzy matches is reused across projects, the glossary is central and editable from the editor with automatic term highlighting, and there are comments, mentions, a progress dashboard and live InDesign page previews in the browser editor — solid basics that beat a hand-merged file workflow. I found no public information on automated QA checks for placeholders, tags or lengths, configurable multi-step review stages, roles per language, or ordering translations from vendors inside the product. 1 5 6 7 9 11
The In-House Document Translator
Translation memory is reused across projects with perfect and fuzzy matches, the glossary is central and editable in the editor, comments, mentions and a live page preview give context, and AI suggestions always wait for human approval — a real review loop. But automated quality checks for placeholders and terminology are not described, nor roles limiting a translator to their languages, which is what I would need before letting a freelancer near a contract. 1 6 7 9 11
The Data Protection Officer
Translation memory with perfect and fuzzy matches is reused across projects and document types, the glossary is central and editable in the web editor, AI suggestions are always put forward for human approval, and translators comment, mention colleagues and see the InDesign page layout as they work. We found no public information on automated QA checks for placeholders or terminology, roles that limit translators to their languages, or configurable multi-step workflows. 1 5 6 7 9
The E-Commerce Marketer
Translation memory with fuzzy matches reused across projects, a glossary editable directly in the editor (how I would fix a bad product name), comments and mentions, live InDesign page preview for context, a progress dashboard, and AI suggestions always presented for human approval. I found no public information on automated QA checks, role limits per language, or configurable multi-step workflows. 1 5 6 7 9 11
The Skeptic
Translation memory with 100% and fuzzy matches reused across projects, a central glossary editable from the editor with terms highlighted, comments and mentions, and a live InDesign page preview make a real working environment, and approved segments carry over on document updates. We found no public information on automated QA checks, roles restricting translators to their languages, configurable multi-step approvals, or ordering translators and agencies inside the product — "one process for internal translators, freelancers, and agencies" is a slogan, not a described workflow. 1 5 6 7 9
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 workable format list covers InDesign IDML, Word, PowerPoint, Excel, HTML, XLIFF, JSON and SRT, and an API uploads files, tracks translation progress and downloads finished documents. The CMS and shop connectors — WordPress, Webflow, Storyblok, Shopify — and an MCP server are all marked coming soon rather than shipping, and we found no public information on Git or CI sync, a CLI, SDKs, over-the-air delivery or webhooks. 1 8 9
The App Developer
The documented API does three things — upload files, track translation progress and download finished documents — and I found no public information on a CLI, SDKs, Git repository sync, CI pipelines, webhooks or over-the-air updates. Every CMS and shop connector on the integrations page (WordPress, Webflow, Storyblok, Shopify) plus the MCP server is marked coming soon, and while the format list covers InDesign, Word, PowerPoint, Excel, HTML, XLIFF, JSON and SRT well, we found no public information on Android XML or iOS strings support. 7 8 9
The In-House Document Translator
The API is documented for uploading files, tracking progress and downloading finished documents, and the format list covers InDesign, Word, PowerPoint, Excel, XLIFF, JSON and more. WordPress, Webflow, Storyblok, Shopify and the MCP server are all marked coming soon, and we found no public information on repository sync or CI pipelines, so today it is upload-and-download rather than a connected chain. 8 9
The Data Protection Officer
A documented API uploads files, tracks translation progress and downloads finished documents, the format list covers InDesign, Word, PowerPoint, Excel, HTML, XLIFF, JSON and SRT, and a free optional InDesign plugin adds live page previews. The WordPress, Webflow, Storyblok and Shopify connectors on the integrations page are all marked coming soon, and we found no public information on Git or CI sync, a CLI or SDKs. 8 9
The E-Commerce Marketer
A good range of document formats (InDesign, Word, PowerPoint, Excel, XLIFF, JSON, SRT) and an API to upload files, track progress and download finished documents, but Shopify — the one connector my shop runs on — is marked coming soon, like WordPress, Webflow and Storyblok. I found no public information on a command-line tool, SDKs, Git sync or webhooks. 8 9
The Skeptic
The API uploads files, tracks progress and downloads finished documents, and the format list genuinely covers InDesign, Word, PowerPoint, Excel, HTML, XLIFF, JSON and SRT. Every connector that would make this a pipeline — WordPress, Webflow, Storyblok, Shopify, the MCP server — is marked coming soon, and we found no public information on Git synchronization, a command-line tool, SDKs, webhooks or over-the-air delivery. 8 9
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 pages state plainly that customer documents sent to OpenAI and DeepL for machine translation are processed via API, temporarily, and not used to train their models, and a downloadable subprocessor list names the providers with their processing locations. A data processing agreement and Standard Contractual Clauses for transfers outside the EEA are referenced, and the security page covers firewalls, six-month database backups and incident alerting. We found no public information on encryption in transit and at rest beyond SSL for payments, single sign-on, audit logs, ISO 27001 or SOC 2 certification, or per-project switching of third-party AI processing. 2 3 10 11
The App Developer
The privacy policy states customer documents are sent to OpenAI and DeepL via API, processed only temporarily and not used to train their models, and content is hosted in Ireland and Germany with a downloadable sub-processor list, a self-serve DPA and six-month backup retention. We found no public information on single sign-on, audit logs, granular roles or ISO 27001/SOC 2 certification, and the encryption statements on the captured pages cover payment transactions and CDN shielding rather than translated content in transit and at rest. 2 3 10 11
The In-House Document Translator
The promise my legal department asks for is in writing: customer documents go to OpenAI and DeepL via API, are processed temporarily and are not used to train their models. The engines and sub-processors are named with their locations, a data processing agreement and a sub-processor list are downloadable and database backups are kept six months; we found no public information on single sign-on, certifications such as ISO 27001, or a retention period the customer sets. 2 3 10 11
The Data Protection Officer
The privacy terms state that customer documents sent to OpenAI and DeepL via API are not used to train their models and are only temporarily processed, database backups are retained up to six months, and a data processing agreement and sub-processor list are published. We found no public information on encryption at rest, single sign-on, audit logs, ISO 27001 or SOC 2 certification, or any way to switch third-party AI processing off per project or account. 2 3 10 11
The E-Commerce Marketer
They state that documents sent to OpenAI and DeepL are not used to train models, name the AI providers, describe AI processing as temporary, retain database backups up to 6 months, and offer a self-serve DPA. I found no public information on encryption at rest, single sign-on, certifications, or a per-project switch to turn third-party AI processing off. 2 3 10 11
The Skeptic
The privacy policy names OpenAI and DeepL as the providers that receive customer documents, states the content is sent via API, processed temporarily and not used to train their models, offers a data processing agreement and publishes a sub-processor list, with database backups kept up to 6 months. The captured pages give different figures for the engines — product pages advertise Google Translate suggestions and ChatGPT pre-translation while the provider list names OpenAI and DeepL — and we found no public information on encryption of stored translations, single sign-on, audit logs, certifications, or switching third-party AI off per project. 2 3 10 11
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
Finished documents export in the original format with layout intact and can be pulled through the API, an export-phrases feature is listed, and an FAQ question about importing translation memories exists — though its answer is not shown in the captures. We found no public information on translation memory export as TMX, glossary export as TBX or CSV, a documented migration path from another tool, or the return or deletion of assets when a contract ends. As someone who wants fourteen languages of memory to stay ours, that is the gap I would press before signing. 6 7 8 9
The App Developer
Finished documents download in the original format, including translated InDesign files with layout intact, and can be fetched via the API, with an Export Phrases feature listed. We found no public information on translation memory export as TMX or glossary export as TBX or CSV — the only signal is an FAQ question about importing translation memories — nor on a migration path from named tools, data return or deletion on termination, or a self-hosted edition. 1 7 8 9
The In-House Document Translator
Finished documents download in the original format with layout intact, there is an export-phrases feature and a FAQ about importing translation memories. We found no public information on exporting translation memory as TMX or the glossary in a standard format, on migrating from another tool in practice, or on data return and deletion on termination. 1 7 9
The Data Protection Officer
Finished documents export in their original format with layout intact and can be downloaded through the API, and the pages mention an Export Phrases feature and a FAQ on importing translation memories. We found no public information on translation memory export as TMX, glossary export as TBX or CSV, migration from named competitors, data return on termination, or a self-hosted edition. 1 7 8
The E-Commerce Marketer
Finished files download in exactly the original format and an Export Phrases feature exists, but the captured pages show only the question of whether translation memories can be imported, and I found no public information on TMX or glossary export, termination terms, or a self-hosted edition. 1 7 8
The Skeptic
Translated files come back in the original format with the layout intact, the API can download finished documents, and an Export Phrases feature exists. We found no public information on translation memory export as TMX or glossary export as TBX or CSV, no migration path into the product, and no terms for returning or deleting assets on termination — the FAQ asks whether translation memories can be imported and the captured excerpt never shows the answer, which for a memory built over six years is the whole question. 1 7 8 9
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 Redokun Srls in Montebelluna, Italy, and customer documents and translations are stated to be hosted in Ireland and Germany on named infrastructure. A published subprocessor list places DeepL in Germany but OpenAI, Anthropic, Linode and Postmark in the United States, with Standard Contractual Clauses stated as the safeguard for those transfers. We found no public information on ISO 27001 or SOC 2 certification and no parent company is named, which is what keeps my confidence below full European chain certainty. 2 3 9 10 11
The App Developer
The contracting entity is Redokun Srls of Montebelluna, Italy, customer documents and translations are hosted in Ireland and Germany, and the sub-processor list names each provider with its location: AWS in Ireland and Germany and DeepL in Germany, but also Linode, OpenAI, Anthropic and Postmark in the United States plus Cloudflare and Netlify, with EEA transfers covered by Standard Contractual Clauses. We found no public information on ISO 27001 or SOC 2 certification, and the United States engines and hosts in the translation chain keep this below the top marks. 2 3 9 10 11
The In-House Document Translator
The contracting entity is Redokun Srls in Italy, uploaded documents and translations are hosted in Ireland and Germany, and the sub-processor list names locations including DeepL in Germany. OpenAI in the United States receives customer documents with Standard Contractual Clauses as the stated safeguard, and we found no public information on ISO 27001 or SOC 2 certifications — acceptable for internal manuals, a question I would still put in writing before the first contract. 2 3 9 10
The Data Protection Officer
The contracting entity is Redokun Srls in Montebelluna, Italy, customer documents and translations are hosted in Ireland and Germany, and a sub-processor list gives processing locations for the engines — DeepL in Germany, OpenAI in the United States — with Standard Contractual Clauses stated for transfers outside the EEA. Linode, a United States hosting provider, also appears in the infrastructure list without a stated role for customer content, and we found no public information on security certifications or a parent company. 2 3 10 11
The E-Commerce Marketer
An Italian company with customer documents and translations hosted in Ireland and Germany, a public subprocessor list with locations, and Standard Contractual Clauses under a self-serve DPA for non-EEA transfers. DeepL processes in Germany, but machine translation can also send my catalogue to OpenAI in the United States, a US hosting provider appears in the subprocessor list, and no ISO 27001 or SOC 2 certification is stated. 2 3 9 10 11
The Skeptic
Redokun Srls is an Italian entity with an Italian VAT number, customer documents and translations are hosted in Ireland and Germany, a sub-processor list with each provider's location is published, and Standard Contractual Clauses cover transfers outside the EEA. The chain still runs through US processors for machine translation (OpenAI), hosting (Linode), email (Postmark) and CDN (Cloudflare), and we found no ISO 27001 or SOC 2 on any captured page. The vendor metadata names Runetek S.r.l. while every captured page names Redokun Srls — different names for the contracting party, and I cannot resolve that from the captures. 2 3 9 10 11
Pricing transparency
not rated — the vendor publishes no price
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 14-day free trial is public and the plan names Basic and Premium appear in feature descriptions, but we found no public prices per tier, no scaling rule by words or seats, and nothing on overage, machine translation volume, minimum term or VAT. From the captured pages a buyer cannot compute an annual cost for a fourteen-language release cycle — budgeting per vendor would be guesswork. 1 3 5
The App Developer
The only public pricing facts are a 14-day free trial and that the glossary, AI fine-tuning and ChatGPT pre-translation are limited to the Basic and Premium plans. I found no public price figures, no scaling rule by words, seats or volume, and no overage handling or free-tier limits on any page I read, so an annual cost is not computable from public pages. 1 3 5 9
The In-House Document Translator
A 14-day free trial is public and plan names appear, with Basic and Premium gating the glossary and AI features. We found no public price figures at all, and no public information on per-seat or per-volume pricing, overage handling or cancellation terms — I could not compute an annual cost from these pages. 1 5 9
The Data Protection Officer
A 14-day free trial is offered and the plan names Basic and Premium gate features such as AI fine-tuning, the glossary and ChatGPT pre-translation. We found no public information on tier prices, how cost scales with volume or seats, overage handling or add-on fees, so a real annual cost cannot be computed from the captured pages. 1 5 9
The E-Commerce Marketer
The captured pages show a 14-day free trial and plan names Basic and Premium gating features like AI fine-tuning and ChatGPT pre-translation, but I found no price on any page we read — I cannot budget my spring rollout from these pages, and there is no indication of how cost scales as the catalogue grows. 1 3 5
The Skeptic
A 14-day free trial and a demo booking are public, and the plan names Basic and Premium surface only through feature gating such as glossary and ChatGPT pre-translation. No price appears anywhere we read — no tier price, no scaling by words, documents or seats, no overage, no language or user limits — so a buyer cannot compute a single euro of annual cost from these pages. 1 3 5
European sovereignty — proven facts
3 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 IT
unverified
Why unverified?The address comes from the privacy policy's data-controller section rather than a formal imprint, and no parent company or group seat is mentioned anywhere. |
2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The statement covers uploaded documents and translations only, and the same page and the privacy policy acknowledge that some personal data is processed by service providers outside the EEA under Standard Contractual Clauses. |
2/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?Only the link to the DPA page is shown; the agreement text itself is not included in the excerpts. |
1/1 pts | 3 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Redokun
Is Redokun European?
Not determined: the vendor’s pages as captured do not say where Redokun is based. Its vendor, Runetek S.r.l., is incorporated in Italy, per the vendor’s page captured 17 Nov 2026.
Where does Redokun store data?
Redokun stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 17 Nov 2026.
Does Redokun have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Redokun?
As of 19 Nov 2026, the panel rates LingoHub (3.5/5), Crowdin (3.5/5) and SimpleLocalize (3.5/5) highest among the other 22 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 LingoHub (EU-Made, Austria). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Redokun alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 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. Only the link to the DPA page is shown; the agreement text itself is not included in the excerpts.
- Weak sourcing — Legal entity. The address comes from the privacy policy's data-controller section rather than a formal imprint, and no parent company or group seat is mentioned anywhere.
- Weak sourcing — Hosting location. The statement covers uploaded documents and translations only, and the same page and the privacy policy acknowledge that some personal data is processed by service providers outside the EEA under Standard Contractual Clauses.
- 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.
- 10 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
- 7 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
- 2 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
- 1 data 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 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
- 1 support 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
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.redokun.com Checked 17 Nov 2026 Details →
- 2 Privacy policy — found from the homepage redokun.com Checked 17 Nov 2026 Details →
- 3 Security / trust page — found from the homepage redokun.com Checked 17 Nov 2026 Details →
- 4 Machine translation & AI quality — found from sitemap redokun.com Checked 17 Nov 2026 Details →
- 5 Machine translation & AI quality — found from sitemap redokun.com Checked 17 Nov 2026 Details →
- 6 Translation memory, terminology & review workflow — found from sitemap redokun.com Checked 17 Nov 2026 Details →
- 7 Translation memory, terminology & review workflow — found from sitemap redokun.com Checked 17 Nov 2026 Details →
- 8 Integrations, file formats & developer tools — found from sitemap redokun.com Checked 17 Nov 2026 Details →
- 9 Integrations, file formats & developer tools — found from sitemap redokun.com Checked 17 Nov 2026 Details →
- 10 Confidentiality of translated content — found from sitemap redokun.com Checked 17 Nov 2026 Details →
- 11 Confidentiality of translated content — found from sitemap redokun.com Checked 17 Nov 2026 Details →