Feature
Translation that never leaves your walls.
Deploy TranslateX in the managed cloud, a sovereign cloud, or fully on your own infrastructure with a local translation model and documented air-gapped installs. LDAP and Active Directory sign-in, MFA, five workspace roles, audit logs with SIEM export, white-label branding, and encryption in transit and at rest.
The premise
Sensitive documents should not be
pasted into public websites.
That is how most institutional translation happens today: a confidential contract, copied into a free web page, terms of service unread. TranslateX exists so that never has to happen.
Three deployments
Cloud, sovereign cloud,
or entirely inside your walls.
TranslateX runs where your data policy says it should. The managed cloud is the fastest start. Sovereign cloud keeps documents inside your national or regional infrastructure. And full on-premises deployment puts the whole platform, including a local translation model, on servers you own: translation happens inside your perimeter, and nothing leaves it.
On-premises is not a diminished edition. It is the same product, deployed via Docker, with documented air-gapped installs for environments that never touch the internet. This is a core differentiator, not an afterthought: Lisan built it because more than 24 government entities work with Lisan, and governments ask exactly this question first.
- Managed cloud, sovereign cloud, or full on-premises
- Local translation model for on-prem: no external calls
- Docker deployment, with documented air-gapped installs
Same product in all three. The on-premises install runs a local translation model, so nothing crosses your perimeter.
Access control
Your directory decides who gets in.
Roles decide what they can do.
Enterprise access control means plugging into what you already run, not maintaining another user database.
Identity and roles
LDAP, Active Directory, MFA, and five roles.
Users sign in through LDAP or Active Directory, so joiners and leavers are handled by the directory your IT team already manages. Multi-factor authentication with TOTP adds a second factor on top of the password, whichever deployment you run.
Inside the workspace, five roles keep privileges tight: admins run the platform, managers own projects and language assets, translators produce, reviewers approve, and viewers read. Khalid Mansour reviews legal documents without touching deployment settings; the intern reads finished translations without editing the glossary.
- LDAP and Active Directory sign-in
- MFA with TOTP authenticator apps
- Roles: admin, manager, translator, reviewer, viewer
Five roles, least privilege by default. Sign-in through LDAP or Active Directory, with MFA on top.
Audit and monitoring
Every action leaves a record
your SOC can read.
Audit logs capture what happens in the platform: sign-ins, translation jobs, glossary changes, role updates. SIEM export forwards those events into the monitoring stack your security team already watches, so TranslateX shows up in the same place as everything else, not in a silo someone has to remember to check.
Documents are encrypted in transit and at rest, part of the enterprise-grade security posture that applies across every deployment model.
- Audit logs across sign-ins, jobs, and admin actions
- SIEM export into your existing monitoring
- Encrypted in transit and at rest
Sign-ins, jobs, glossary edits, and role changes, all logged and exportable to your SIEM.
Make it yours
White-label branding,
government-grade heritage.
For institutions that deploy TranslateX as an internal service, the platform can carry your identity rather than ours.
White-label branding
Your logo, your name, your look. An on-premises TranslateX can present itself as your ministry's or company's own translation platform to the people who use it.
Built with governments
More than 24 government entities work with Lisan. On-premises deployment, air-gapped installs, and directory integration exist because those institutions required them. Government use cases →
Same features, everywhere
Glossaries, translation memory, style governance, and the review editor all run identically on-premises, with the local model doing the translating. Glossary and memory →
Frequently asked questions
Can TranslateX run completely offline?
Yes. The on-premises deployment includes a local translation model and supports documented air-gapped installs, so translation runs entirely inside your network with no external calls. Deployment is via Docker.
What sign-in options do enterprises get?
LDAP and Active Directory integration, so access follows your existing directory, plus multi-factor authentication using TOTP authenticator apps.
What roles does the platform support?
Five: admin, manager, translator, reviewer, and viewer. Admins control deployment and security, managers own projects and language assets, translators and reviewers handle production and quality, and viewers get read-only access.
How does TranslateX fit our security monitoring?
Audit logs record sign-ins, translation jobs, glossary changes, and admin actions, and SIEM export forwards those events into the monitoring stack your security team already uses. Data is encrypted in transit and at rest.
Can we brand the platform as our own?
Yes. White-label branding lets an institution present TranslateX under its own name and identity, which is common for on-premises deployments offered as an internal service.
Is TranslateX trusted by governments?
More than 24 government entities work with Lisan, and TranslateX's on-premises, air-gapped, and directory-integration capabilities were built for exactly those environments. See TranslateX for government.
Translate the document. Keep the design.
Right-click a file, work inside Office, or press F6 on anything on screen. TranslateX returns the same document in the other language: fonts, tables, and layout intact, terminology on brand.
Arabic, English & more · Layout preserved · On-premises available