One binary, one file
One executable with the web interface built in and the data in a single SQLite file. About 15 MB on disk, no Java, Postgres or Redis, and it starts in milliseconds.
One binary.
Every language.
Your apps' keys and translations in one place, with roles for developers and translators, machine or AI translation, and files handed back in the format your build already reads.
On your server · Linux, Windows, macOS or Docker · Open source / AGPL-3.0
In your daily work
Translation without the infrastructure.
One executable and one SQLite file. Nothing else.
A role for each person
Manager, developer, reviewer, translator or viewer in each project. Translators and reviewers can be limited to some languages, and reviewed texts are locked.
Machine translation and AI
Google, DeepL, Microsoft, LibreTranslate or any OpenAI-compatible API, including Ollama and LM Studio. Placeholders are preserved, and provider keys are stored encrypted.
The formats your build reads
Import and export JSON, CSV, Gettext PO, Android strings.xml, Apple .strings and Java .properties. Per-project API keys bring the texts to your app and your CI.
Your translations stay on your server.
Everything lives in one SQLite file in the data folder you choose, easy to copy for backups. Provider keys are encrypted. If you use machine translation or a remote AI, the texts go to the provider you chose.
Coming from Tolgee
Bring the whole project.
LowLex imports a Tolgee project straight through its API, in the background, resuming where it stopped if interrupted. After the move, code written for Tolgee's REST API keeps working, pointed at LowLex.
Also exploreLowDesk
Less noise in support. More tickets resolved.