A Lingo.dev alternative that needs no account to start
Both translate your app with AI, ship a CLI, a GitHub Action and an MCP server. The difference is shape: Lingo.dev pushes your content to a configured server-side engine; KAERIS translates the files already in your repo — free to start, with an offline CI check and a repo-native MCP.
Engine you configure vs. files you translate
Lingo.dev
A configurable localization engine. Its CLI (lingo push / lingo pull) ships your source content to a server-side engine that holds glossary, brand voice and model configuration, then writes results back. Requires lingo login or an API key. Strong fit if your team wants persistent, configured localization infrastructure.
KAERIS
Translate-and-ship. The kaeris CLI, REST API, MCP server and GitHub Action translate the files in your repo directly — placeholder-safe, incremental via kaeris.lock. No account to start, and a free offline check that makes no API call. Strong fit if you just want your strings translated fast.
KAERIS vs Lingo.dev
Both are developer-first and translate well. Here's where they genuinely differ.
Facts about Lingo.dev are taken from its own CLI documentation (lingo push/pull, login/API-key requirement). If you want a persistent, configured localization engine, Lingo.dev is a legitimate choice for that job. If you want to translate your repo's files fast without an account, that's what KAERIS is built for.
kaeris check fails a build on missing keys or broken placeholders with no API call and no key.FAQ
How is KAERIS different from Lingo.dev?
Lingo.dev is a configurable localization engine: its CLI pushes your source content to a server-side engine that holds glossary, brand voice and model config, then you pull results back — it requires a login or API key. KAERIS translates your files directly: no account to start, a free offline check that makes no API call, 11 formats, and a repo-native MCP server. Different shapes — Lingo is engine-and-config; KAERIS is translate-and-ship.
Do I need an account or API key to try KAERIS?
No. The free anonymous tier works with no account, no credit card, up to 10,000 characters per file. A free API key raises that to 50,000; paid plans from $19/mo raise it further, or BYOK on the $79 one-time Lifetime plan removes the monthly cap using your own AI key.
Can KAERIS run in CI like Lingo?
Yes — a GitHub Action with two modes. translate updates locale files and opens a PR; check is a static i18n firewall that runs entirely offline (no API call, no key) and fails the build if a locale is missing keys or a translation broke a placeholder.
Which one should I choose?
If you want a persistent, configured localization engine — server-side glossary, brand voice and model chains your team maintains — Lingo.dev is built for that. If you want to translate the files already in your repo quickly, without an account, with a free offline CI check and a repo-native MCP server, that's what KAERIS is for.
Translate your repo without an account
46 languages, 11 formats, placeholder-safe, with a free offline CI check. Start in seconds.
$ pip install kaeris $ kaeris translate en.json --langs de,fr,es,ja