Translation & Localization
LILT
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by LILT, Inc. · lilt.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.
LILT at a glance
- Vendor
- LILT, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention United States source, captured 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates LILT 3.5/5, the mean of 6 judges. LILT is an enterprise AI translation platform built on adaptive machine translation with human review. 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
LILT is an enterprise AI translation platform built on adaptive machine translation with human review. Machine translation leads at 7 to 8: models fine-tune in real time from human corrections, custom models train on historical data, and a model library includes OpenAI, Anthropic and Google. Integrations and formats scores sit at 7 on 100+ native connectors, a documented REST API and MCP support. Content confidentiality scores 7 to 8 on SOC 2 Type II audited by A-LIGN, ISO 9001 and ISO 17100, a published data processing agreement, Standard Contractual Clauses, retention capped at 90 days after completion of services, and private cloud, on-premises, bare metal and air-gapped deployments. Sovereignty is the weak side, with scores spanning 4 to 6: judges who valued the self-managed editions scored higher, while others weighed the US-based controller and servers; we found no public information on EU hosting of the cloud service. Portability and exit scores run 6 to 7 — import is broad, but the documented export covers termbase entries to CSV. Pricing is request-only: every tier says Contact Sales.
Speaks for it
- Adaptive models fine-tune in real time from human corrections, with custom models trained on customers' historical data and third-party LLMs from OpenAI, Anthropic and Google in the model library
- 100+ native connectors reach GitHub, Contentful, Shopify, Zendesk and competing translation systems, alongside a documented REST API and MCP on every plan
- SOC 2 Type II audited by A-LIGN, ISO 9001 and ISO 17100, a published data processing agreement and Standard Contractual Clauses are documented
- The retention obligation ends 90 days after completion of services
- Private cloud, on-premises, bare metal and air-gapped deployments are documented with their own self-managed documentation
Held against it
- Sovereignty scores span 4 to 6: the controller is LILT, Inc. in San Francisco, servers are stated to be in the United States on Google Cloud Platform, and we found no public information on EU hosting of the cloud service
- The documented export endpoint covers termbase entries to CSV; we found no public information on translation-memory export as TMX or complete project export
- We found no public information on whether customer texts train models or on zero-retention terms with the named LLM providers
- We found no published translation-quality evaluation with its method, and the supported-languages list is available through an API endpoint rather than a readable page
- Every tier — Team, Business, Enterprise, Government — says Contact Sales, with a Request Pricing page and no figures
Best for
- You need machine translation that learns from your translators' corrections and can pair with OpenAI, Anthropic or Google models
- Your content lives in GitHub, a CMS such as Contentful or Sitecore, or Shopify, and you want native connectors plus a documented REST API
- You can operate the self-managed edition on your own private cloud, on-premises, bare metal or air-gapped infrastructure
- Your translators rely on central termbase entries that overwrite the memory like dictionary items and are highlighted during translation
Avoid if
- You need the standard cloud service hosted in the EU — the captured pages state the company's servers are located in the United States on Google Cloud Platform, and we found no public information on EU hosting
- You need a documented exit with your translation memory in hand — the documented export covers termbase entries to CSV
- You need published figures to budget before engaging sales — every tier says Contact Sales
- Your team has no system administrators — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3.5 of 5 |
| Translation memory, terminology & review workflow | 3.5 of 5 |
| Integrations, file formats & developer tools | 3.5 of 5 |
| Confidentiality of translated content | 3.5 of 5 |
| Data export, portability & self-hosting | 3 of 5 |
| European sovereignty | 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
LILT's adaptive engine is the real thing: models fine-tuned in real time from human corrections and trained on our own historical data, a choice of third-party LLMs (OpenAI, Anthropic, Google) alongside their own context-aware models, and brand guidelines, glossaries and tone-of-voice applied when output is produced, with a documented API endpoint listing the supported language pairs. AI review agents do an initial error pass and content is routed by risk profile to human experts, which covers steering; we found no public information on a published quality evaluation with its method, and error checking is described as flagging potential errors rather than a calibrated per-segment quality score with a documented routing rule. 1 5 10 11 12 13
The App Developer
Adaptive models that learn in real time from human corrections, custom context-aware models trained on our historical data, an automated fine-tuning cadence to the MT system or LLM of choice, third-party LLMs like OpenAI, Anthropic and Google in a model library, and brand guidelines, glossaries and tone-of-voice applied during translation and verification — this is the strong version of machine translation. The supported-languages list is published through an API endpoint. We found no public information on a published translation-quality evaluation with its method, or on tracing each segment to the engine, model version and glossary that produced it. 2 5 10 11 12 13
The In-House Document Translator
Their own context-aware engine adapts in real time from human corrections, they let you bring OpenAI, Anthropic or Google models or build custom models per language pair, and termbase entries are enforced and highlighted during translation with brand tone checked by AI review agents. For my daily contract and manual work the gaps matter: I found no public information on a published language list (only an API endpoint to query), on whether Word or PDF layout is kept, or on a published quality evaluation with its method. 10 12 13 11 5 2
The Data Protection Officer
Adaptive custom models trained on the customer's historical data and refined in real time from human corrections are well documented, with termbase entries enforced and highlighted during translation, routing of high-risk content to human review based on the asset's risk profile, and supported language pairs retrievable through a documented API endpoint. We found no public information on a published translation quality evaluation with its method, or on per-segment quality estimation that routes weak segments to human review. 10 11 12 13
The E-Commerce Marketer
The adaptive models are the strong part: custom context-aware models train on my own historical data, are fine-tuned in real time from human corrections, and I can use LILT's own models or bring third-party ones from OpenAI, Anthropic or Google. Termbase entries are highlighted during translation and stored tone-of-voice is used to verify output, which is how I would pin down a product name across six languages. We found no public information on a published quality evaluation with its method, and the supported languages are documented as an API response rather than a readable list I could check against my spring deadline. 12 10 5 13 11 1
The Skeptic
Adaptive models that learn in real time from human corrections, custom models trained on the customer's historical data, and a model library that includes third-party LLMs from OpenAI, Anthropic and Google are all documented, with models created per language pair and termbase entries applied during translation. What we did not find is any published quality evaluation with its method, and routing is described by content risk profile rather than a per-segment quality score with a stated cutoff. The supported-language list is reachable through the API rather than published as a page. 10 12 13 2 5 11
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
Memory and termbase are first-class citizens: TMX, Trados and XLIFF import, termbase entries that override the memory like glossary items and are highlighted during translation, a Manage entries screen, and a CAT tool with predictive capabilities for translators and reviewers. Review is covered by AI review agents before humans see the text, a Reviewed by default setting, usage-based human-expert verification through LILT's own network, role-based access with per-domain segmentation, and real-time analytics on delivery, quality and spend — though we found no public information on configurable blocking QA checks per project, fuzzy-match penalties, or comments and screenshots for translator context. 2 5 12 13 14 17 19
The App Developer
Translation memory and a termbase are managed centrally with termbase entries highlighted during translation, AI review agents run an automated error check before a human sees the text, content routes by risk profile to human experts, and roles with domain-level permissions are documented. Real-time analytics cover delivery, quality and budget, and human-expert verification is offered usage-based. We found no public information on an in-context or visual editor, comments and screenshots for translators, or QA checks for placeholders and tags with blocking rules — the in-context part matters most for an app team like mine. 2 5 12 13 17
The In-House Document Translator
Translation memory and termbase are managed centrally, termbase entries overwrite the memory like dictionary items and are highlighted during translation, which is exactly how I would keep our contractual terms consistent across French, Italian, Polish and Chinese. Review is real: AI review agents make a first error pass, content is routed by risk to human experts (ours or theirs, ordered usage-based), with role-based access, domains, and analytics on quality, spend and turnaround. We found no public information on an in-context visual editor, configurable blocking QA rules, or comments and screenshots for reviewers. 13 12 5 17 19
The Data Protection Officer
A translation memory and a central termbase are managed in the product with import from TMX and Trados formats, an AI pre-review pass before human eyes, routing to human experts — the customer's or the vendor's — roles segmented by domain, and real-time reporting on delivery, quality and spend. We found no public information on an in-context visual editor, configurable blocking QA rules, or per-language role assignment. 2 4 12 13
The E-Commerce Marketer
Memory and termbase entries are managed in one place, termbase entries overwrite the model like dictionary items and are highlighted as work happens — exactly the manual fix I need for a mistranslated jersey name. Content routes by risk profile between instant AI and human experts ("yours or ours"), AI review agents do a first error pass before any human sees the text, and roles, domains and analytics on delivery, quality and budget are all documented. We found no public information on an in-context or visual editor or on QA rules configurable per project, which keeps this a notch below the enterprise-grade level. 13 12 2 5
The Skeptic
Memory and termbase are managed centrally, termbase entries are highlighted during translation and override the memory, AI review agents run a first error pass before human verification, and content routes to a verified network of human experts — yours or theirs. Role-based access and domain segmentation restrict what users touch, and real-time analytics cover delivery, quality and budget. We found no public information on fuzzy matching, comments or screenshots for context, or QA rules configurable with blocking severity. 13 19 5 12 17 2 4
Integrations, file formats & developer tools
Show reasoningHide reasoning
How this is scored
How content gets in and out: the file formats supported (XLIFF, PO, JSON, YAML, Android XML, iOS strings and xcstrings, Office documents, InDesign), a REST API and CLI, SDKs and over-the-air updates for apps, Git repository sync (GitHub, GitLab, Bitbucket) and CI pipelines, connectors for CMS, shop and design tools (WordPress, Contentful, Shopify, Figma), browser and office add-ins, webhooks, and a JavaScript snippet or proxy for website translation.
0 — No documented way to get content in or out except typing or pasting by hand.
3 — File upload and download or a basic API; formats, repository sync and connectors are basic or not described.
5 — A documented REST API, a list of supported file formats covering the common software and document formats, sync with at least one Git host or CI, and connectors or plugins for several named CMS, shop or design tools.
8 — A CLI and SDKs for named platforms, over-the-air updates for mobile or web apps, Git sync with branching, webhooks, connectors for the main CMS, shop, design and support tools, office or browser add-ins, a public status page, and API limits documented.
10 — Integration that scales across an organisation: an API covering every function of the product with versioning and SDKs, an app or connector framework third parties build on, continuous localization in CI with pull requests opened automatically, and every connector documented with its limits and the fields it syncs.
The Localization Manager
The connector catalogue is the broadest I have judged: 100+ native integrations spanning GitHub, GitLab, Bitbucket and self-hosted Git, the main CMS platforms (Contentful, Sitecore, Drupal, WordPress via WPML, Adobe Experience Manager), Shopify and Salesforce Commerce Cloud, Figma, Zendesk and Intercom, plus TMS-to-TMS bridges to Trados, Phrase, Crowdin, Lokalise and Smartling — alongside a documented REST API, native MCP support, developer documentation and a public status page. We found no public information on a CLI, SDKs, over-the-air updates, webhooks, office or browser add-ins, or documented API limits. 1 2 9 14 15
The App Developer
For a developer this covers a lot of my wishlist: sync with GitHub, GitLab, Bitbucket and self-hosted Git, 100+ connectors including Figma, Contentful, Shopify and Zendesk, a documented REST API with endpoints for languages, memory import and termbase export, native MCP for AI assistants, and a public status page. We found no public information on a CLI, SDKs, over-the-air updates, webhooks or documented API limits, and the only format list I found covers translation-memory files (TMX, XLIFF, SDLXLIFF, TBX, CSV) rather than software string formats like JSON, iOS strings or Android XML. 1 2 14 15 19
The In-House Document Translator
There is a documented REST API plus more than a hundred named connectors — GitHub, GitLab, Bitbucket and self-hosted Git for code, Contentful, WordPress, Sitecore and other CMS, Shopify and Salesforce Commerce Cloud, Zendesk, Figma, Box and Dropbox — alongside native MCP support and a public status page. For document work the captured pages show TM and termbase formats (TMX, XLIFF, Trados memory files, TBX, CSV) and a claim of translation for image, PDF, audio and video files; we found no public information on a CLI, SDKs, webhooks, or software formats like PO or JSON. 15 1 14 11 19 13 2
The Data Protection Officer
A documented REST API with authentication sits alongside more than a hundred named connectors covering GitHub, GitLab, Bitbucket and self-hosted Git, major CMS platforms, commerce, design and support tools, plus native MCP support and import of TMX, XLIFF and Trados memory formats. We found no public information on a CLI, SDKs, over-the-air updates, webhooks, or a published list of software file formats such as JSON or Android resources. 1 14 15 19
The E-Commerce Marketer
There is a native Shopify connector promising a multilingual shop in a matter of clicks, among more than a hundred others including GitHub, GitLab, Bitbucket, WordPress via WPML, Contentful, Figma, Zendesk, HubSpot and Salesforce Commerce Cloud — enough to reach product pages, emails and support without hiring a developer. A REST API is documented with reference pages for memories, termbase export and supported languages, import covers TMX, XLIFF, CSV, TBX and more, a status page exists, and native MCP support is claimed for all plans. We found no public information on a CLI, SDKs, over-the-air updates or webhooks, so I stop short of the top level. 15 1 14 13 2
The Skeptic
A documented REST API with endpoints for languages, memory import and termbase export sits alongside a connector catalogue naming GitHub, GitLab, Bitbucket, Contentful, WordPress, Shopify, Figma, Zendesk, Salesforce and dozens more, including connections to competing translation systems, with native MCP support on every plan. We found no public information on a CLI, SDKs, webhooks, or over-the-air updates for apps, and no documented API limits. 15 14 11 18 2 5
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
SOC 2 Type II (audited by A-LIGN) plus ISO 9001 and ISO 17100 are stated with their auditors, a data processing agreement and the European Commission's standard contractual clauses are offered, and single sign-on sits on the Enterprise tier with certificate-of-translation audit trails. The privacy policy states encryption and firewalls, the self-managed documentation details database encryption and mutual TLS between services, and private cloud, on-premises and air-gapped deployments go beyond what I usually see. The captured pages are silent, though, on whether customer texts train LILT's own cross-customer models and on zero-retention terms with the named LLM providers, and retention is stated only as no obligation to keep information beyond 90 days after services end. 1 5 6 7 12 16 17
The App Developer
SOC 2 Type II with a named auditor, a published data processing agreement, subprocessor listings, role-based access control, audit trails on the Enterprise tier, and private cloud, on-premises and air-gapped deployment options are all documented, with mutual TLS and storage encryption in the self-managed documentation. The privacy policy states encryption and firewalls and caps any retention obligation at 90 days after completion of services. We found no public information on deletion after a customer-set retention period, on whether customer texts are used to train models, or on zero-retention terms with the named LLM providers. 5 6 7 12 16 17
The In-House Document Translator
Security is well documented: SOC 2 Type II with the auditor named, ISO 9001 and ISO 17100, encryption in transit and at rest, role-based access, translation audit trails, single sign-on on the top tier, a data processing agreement, a subprocessor listing in a security portal, and private cloud, on-premise or air-gapped deployment. But the written promise I need most — that a draft contract is never used to train their models — we could not find; retention is a flat 90-day statement rather than something we set or switch per project, and no zero-retention terms with the named LLM providers are stated. 7 16 8 17 5 6 12
The Data Protection Officer
Strong pieces are documented: SOC 2 Type II with a named auditor, a published data processing agreement, encryption, single sign-on, audit trails, role-based access with tenant separation, and private cloud, on-premises and air-gapped deployment options. However, the privacy policy states only that there is no obligation to keep information beyond 90 days after completion of services — we found no public commitment to delete translated texts after any stated period. We also found no public statement that customer texts are never used for model training (custom models trained on the customer's historical data are a core feature), and no zero-retention terms with the named LLM providers OpenAI, Anthropic and Google. 1 5 6 7 12 16 17
The E-Commerce Marketer
Retention is capped at ninety days after completion of services, a data processing agreement is published, and a security documentation portal carries certifications and sub-processor listings; SOC 2 Type II, ISO 9001 and ISO 17100 are stated with their auditors. Enterprise adds audit trails and single sign-on, and the self-managed edition documents role-based access, tenant isolation, AES-128 database encryption and mutual TLS inside the customer's own infrastructure, with private cloud, on-premise and air-gapped deployment options. We found no public information on zero-retention terms with the named LLM providers, which is the one gap that matters for a shop's trade secrets. 7 6 8 16 5 17 12
The Skeptic
The privacy policy states no obligation to keep information beyond 90 days after completion of services, a data processing agreement is published, SOC 2 Type II was audited by A-LIGN, and single sign-on, audit trails and role-based access arrive on the Enterprise tier, with on-premise and air-gapped deployments for the strictest cases. Two gaps matter: we found no public statement that translated content is excluded from model training — the product's premise is models learning from every correction — and no zero-retention terms with the third-party LLM providers, whose processing is not shown to be switchable below the Enterprise tier. The self-managed deployment documents database encryption as AES-128 in ECB mode, a choice a security reviewer would question. 7 16 6 5 1 17 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 and termbase import in open and Trados formats (TMX, XLIFF, sdltm, tmq, TBX, CSV), the termbase exports to CSV through documented API endpoints, and there is a self-managed edition with its own documentation covering memory management and encryption on infrastructure the customer controls — on-premises, bare metal and air-gapped are all named as deployment options. We found no public information on exporting the translation memory itself back out as TMX, a complete export of files, comments and history, or data return and deletion terms on termination. 9 12 13 17 18 19
The App Developer
A self-managed edition with its own documentation — deployable on private cloud, on-premises, bare metal and air-gapped — is exactly the exit path I want if the vendor changes course, and TMS-to-TMS connectors to Crowdin, Lokalise, Phrase and Trados plus import of TMX, XLIFF, SDLXLIFF, TBX and CSV data document a migration path in. Export is the thin side: the documented export endpoint covers termbase entries to CSV, and we found no public information on translation-memory export as TMX, complete project export, or data return and deletion on termination. 9 13 15 18 19
The In-House Document Translator
Getting data in is well covered — TMX, XLIFF, Trados memory formats, TBX, CSV and more, up to 200MB — and there is a genuinely self-managed edition with its own documentation for on-premise and bare-metal deployment, so our assets could live on our own servers. Export is thinner: the documented export is the termbase to CSV via an API endpoint; we found no public information on exporting the translation memory itself as TMX, on complete export of project files, comments and history, or on data return and deletion at termination. 19 18 13 17 8 9 7
The Data Protection Officer
Import of translation memory from TMX, XLIFF and Trados formats plus termbase files, termbase export to CSV via the API, and a self-managed edition with its own documentation running on private cloud, on-premises or bare metal are all evidenced. We found no public information on translation memory export, export of full projects with history and comments, or stated terms for return or deletion of data on termination. 9 13 17 18 19
The E-Commerce Marketer
I can bring translations in from other tools in TMX, XLIFF, SDL, CSV and TBX formats with a documented file-size limit, the API exports termbase entries to CSV, and a self-managed edition has its own documentation covering deployment on private cloud, on-premise and bare metal. We found no public information on exporting the translation memory itself in TMX or on downloading all project files with their history, so a clean exit with every asset in hand is only partly evidenced. 19 13 18 9 8
The Skeptic
Import is well covered — TMX, Trados memories, XLIFF and TBX or CSV up to 200MB — and a self-managed edition with its own documentation means the assets can live on infrastructure the customer controls. What leaves is the question: the only export endpoint documented is the termbase to CSV, and we found no public information on exporting the translation memory itself as TMX, on project files, comments or history, or on what is returned or deleted at termination. 18 19 13 9 17
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 captured pages name LILT, Inc. of San Francisco as controller, state that the company's servers are located in the United States and that Google Cloud Platform provides the computing infrastructure; a data processing agreement, the European Commission's standard contractual clauses and a subprocessor listing in the security documentation portal are the documented safeguards. On-premises, private cloud and air-gapped editions are documented, which a European customer could run on its own servers, but we found no public information on EU hosting for the cloud service or an EU representative. 2 6 7 8 12 16
The App Developer
The controller and contracting entity is LILT, Inc. of San Francisco, servers are located in the United States and computing infrastructure runs on Google Cloud Platform; a data processing agreement, Standard Contractual Clauses and subprocessor listings are available, which sits above the baseline. On-premises and air-gapped deployments are documented, so a European team could run texts on its own servers, but we found no public information on EU hosting of the cloud service or the locations of every subprocessor in the translation chain. 6 7 9 16
The In-House Document Translator
The contracting entity and controller is LILT, Inc. of San Francisco, the servers are stated to be located in the United States on Google Cloud, and the stated safeguard for transfers is the European Commission's Standard Contractual Clauses alongside a published subprocessor listing; we found no public information on EU hosting or an EU representative. What lifts it for us is the documented private cloud, on-premise and air-gapped edition with self-managed documentation running on the customer's own infrastructure, which would keep our documents on our own European servers — though the locations of every engine and subprocessor in that chain are not spelled out on the captured pages. 7 16 6 8 12 13 17 1
The Data Protection Officer
The controller and contracting entity is LILT, Inc. of San Francisco, whose privacy policy states the company's servers are located in the United States, with Google Cloud Platform named as computing infrastructure; the stated safeguards are a data processing agreement and Standard Contractual Clauses available on request. A subprocessor listing exists behind the security documentation portal, but the captured pages do not show which providers it names or where they sit, and we found no public information on EU hosting or a European contracting entity. A self-managed, including air-gapped, deployment is documented, which a customer could run on its own European servers. 6 7 9 12 16
The E-Commerce Marketer
The controller is LILT, Inc. in San Francisco and the privacy policy states the company's servers are in the United States on Google Cloud Platform, so my product texts would cross the Atlantic under Standard Contractual Clauses; a data processing agreement and a sub-processor listing are at least published. Self-hosted, on-premise and air-gapped editions are documented, but they read as enterprise deployments run by customer sysadmins, not something a Munich shop without a developer could operate. We found no public information on EU hosting or an EU contracting entity for the standard service. 7 16 6 8 12 17
The Skeptic
The controller and contracting entity is LILT, Inc. of San Francisco, the servers are stated to be in the United States on Google Cloud Platform, and site analytics run through Google and Meta — the whole standard chain is American, held together by standard contractual clauses and a published data processing agreement. The escape is real but framed for US missions rather than European ones: on-premise and air-gapped editions with self-managed documentation exist, yet we found no public information on EU hosting, an EU entity or representative, or where the machine translation and LLM providers process text. 7 16 6 5 8 17
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
Every plan on the public pricing page — Team, Business, Enterprise and Government — says Contact Sales, with a Request Pricing call to action and no figures anywhere in the captured pages; even detailed MCP pricing is only referenced, never shown. The published tier feature lists tell me what each tier contains, but from these pages alone I cannot begin to compute an annual cost for a given volume of words or languages. 5 10
The App Developer
Four tiers are published with their inclusions — Team with unlimited users and 3 included domains, Business with 5 domains and forward-deployed engineering hours, Enterprise with SSO and bring-your-own LLM, Government with air-gapped deployment — but every plan says "Contact Sales" and the page routes to "Request Pricing". We found no public information on any per-character, per-word or per-seat figures, a free tier, or the usage-based cost of human-expert verification, so I cannot compute an annual cost from the captured pages. 5 10
The In-House Document Translator
Every plan — Team, Business, Enterprise, Government — says Contact Sales, and the pricing pages show request-pricing with no figures at all, not even a starting price or a free tier. Each tier's inclusions (number of domains, single sign-on, air-gapped deployment, human verification as usage-based) are published so I know what to ask about, but I cannot compute any annual cost from the public pages alone. 5 10 1
The Data Protection Officer
The pricing page names four tiers and lists their feature inclusions, but every plan shows "Contact Sales" and no figures appear anywhere: no per-word or per-seat price, no free tier, no overage or add-on pricing. An annual cost cannot be computed from the captured pages. 5 10
The E-Commerce Marketer
The pricing page names Team, Business, Enterprise and Government tiers and says what each includes — users, domains, verification options, single sign-on — but every plan says Contact Sales and the page shows Request Pricing with no figures; even the usage-based human-expert verification is unpriced. As a shop owner I cannot compute a monthly cost from these pages, let alone see what happens when my catalogue grows before the spring season. 5 10
The Skeptic
Every tier — Team, Business, Enterprise, Government — is "Contact Sales", the page itself says "Request Pricing", and no figure, free tier or volume rule appears anywhere we read; usage-based human verification and MCP pricing are mentioned without a rate. What is public is the feature split per tier, such as included domain counts and single sign-on, which lets a buyer compare scope but not compute a single euro or dollar of annual cost. 5 10
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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | 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 LILT
Is LILT European?
No. whats-best.ai classifies LILT as Rest of world.
Where does LILT store data?
The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention United States as hosting location, per the vendor’s page captured 1 Nov 2026.
Does LILT have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to LILT?
As of 2 Nov 2026, the panel rates SimpleLocalize (3.5/5), Phrase Localization Platform (3.5/5) and Tolgee (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: LILT 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 options. 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.
- 3 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 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (19)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage lilt.com Checked 1 Nov 2026 Details →
- 2 Features page (AI platform) lilt.com Checked 1 Nov 2026 Details →
- 3 Features page (translation assist) lilt.com Checked 1 Nov 2026 Details →
- 4 Integrations page lilt.com Checked 1 Nov 2026 Details →
- 5 Pricing page lilt.com Checked 1 Nov 2026 Details →
- 6 Terms of service lilt.com Checked 1 Nov 2026 Details →
- 7 Privacy policy lilt.com Checked 1 Nov 2026 Details →
- 8 Security / trust page lilt.com Checked 1 Nov 2026 Details →
- 9 Features page (private deployment) lilt.com Checked 1 Nov 2026 Details →
- 10 Machine translation & AI quality — found from sitemap lilt.com Checked 1 Nov 2026 Details →
- 11 Machine translation & AI quality — found from sitemap support.lilt.com Checked 1 Nov 2026 Details →
- 12 Translation memory, terminology & review workflow — found from sitemap lilt.com Checked 1 Nov 2026 Details →
- 13 Translation memory, terminology & review workflow — found from sitemap support.lilt.com Checked 1 Nov 2026 Details →
- 14 Integrations, file formats & developer tools — found from sitemap lilt.com Checked 1 Nov 2026 Details →
- 15 Integrations, file formats & developer tools — found from sitemap lilt.com Checked 1 Nov 2026 Details →
- 16 Confidentiality of translated content — found from sitemap lilt.com Checked 1 Nov 2026 Details →
- 17 Confidentiality of translated content — found from sitemap support.lilt.com Checked 1 Nov 2026 Details →
- 18 Data export, portability & self-hosting — found from sitemap support.lilt.com Checked 1 Nov 2026 Details →
- 19 Data export, portability & self-hosting — found from sitemap support.lilt.com Checked 1 Nov 2026 Details →