Your repo was always the source of truth.
We just refused to pretend otherwise.
The mission
Localization shouldn't mean handing your codebase — or even your strings — to someone else's "platform." Dialecto keeps the repo as the source of truth: your translations organized by domain, validated before they ship, and delivered back to you as clean pull requests. Yours, start to finish.
Why we built it
Two convictions. First, that editing translations could feel genuinely good — by domain, in context, fast — instead of like data entry. Second, that AI leverage shouldn't cost you control: you should be able to bring whatever model you trust, ground it in curated context, and keep everything — code, strings, review — in your own hands. Dialecto is the only localization tool that never needs your whole codebase. A surgical slice, and not a stroke more. That constraint shaped everything else.
Elixir first
We're starting with the Elixir and Phoenix community — gettext-native, quality-minded, and the ecosystem we know best. Best-in-class for one community before merely-fine for all of them.
EU-sovereign, on principle
Dialecto runs under EU jurisdiction, holds as little as possible, and self-hosts if you'd rather it hold nothing at all. The sovereignty page has the details.
The name
Dialecto — dialect, with a tip of the hat to domain-driven design. Domain-driven localization: the name is the roadmap.
Who's behind it
Dialecto is built by a small team that has shipped and localized production software for years — and got tired of every tool that asked for more than it needed. Contact details land here shortly.