Your repo was always the source of truth.
We just refused to pretend otherwise.
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 from start to finish.
Motivation
We built it on two convictions. The first is that editing translations could feel genuinely good — by domain, in context, fast — instead of like data entry. The second is 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 never needs your whole codebase; a surgical slice is enough, 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. We want it to be excellent for one community before it is merely fine for all of them.
EU sovereignty
Dialecto runs under EU jurisdiction, holds as little as possible, and self-hosts if you'd rather it hold nothing at all. Thesovereignty page has the details.
Name origin
Dialecto — dialect, with a tip of the hat to domain-driven design. Domain-driven localization: the name is the roadmap.
Team
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.
Write toinfo@dialecto.euand you'll hear back from a person who builds it.