Repo-native localization on sovereign EU infrastructure.
Sovereignty isn't a compliance checkbox we added later. Dialecto was built to hold as little of your data as possible, and to hold that little under EU jurisdiction — with a way out of even that, if you want your strings to never leave your own machines.
Data received
Your codebase stays in your repo. Dialecto receives your translation files, and the few source lines around each string only if your pipeline sends them. Nothing else about your application reaches us, and what does is processed and stored in the EU.
Data destinations
| Destination | Location | Condition |
|---|---|---|
| GitHub repository | Where it already lives | Already the case |
| Dialecto (hosted) | EU infrastructure | When you use the hosted app |
| DeepL | EU (Cologne, Germany) | Only if an owner chooses it |
| Gemini | Google, US | Only if an owner chooses it |
| A local model (self-hosted) | Your own machine | When you self-host Dialecto with a local model |
Machine translation
Machine translation can run on a local model beside a self-hosted Dialecto, and that is the default adapter, so your strings don't leave your machine. Dialecto's hosted app does not run a local model today. During the soft launch, an owner or admin can choose hosted translation for the organization. It is off until they choose, and the choice is theirs to make with the facts in front of them.
DeepL keeps your strings in the EU. The source text goes to DeepL SE in Cologne, Germany, on a paid plan whose terms say texts are not stored or used for training.Gemini sends your strings to Google, a US company. The source text, and your brand voice and personas, go to Google through its paid Gemini API, which does not use them for training. If you need everything to stay in the EU, choose DeepL. Either way it is a choice you make, never a default we quietly flipped.
EU-sovereign infrastructure
The app runs under EU jurisdiction on EU infrastructure. The ways your strings can leave it are ones you choose: GitHub, where your repository already lives, and Gemini, if an owner picks it. Its home will be app.dialecto.eu, on an EU country-code domain, the same one this marketing site lives on. The site is a set of static pages with no cookies, no trackers and no third-party requests, so no customer data is ever served from it. One small script of our own remembers light or dark in your browser if you choose one, and that choice never leaves your device.
Vendor independence
Dialecto's own stack is an Elixir release and PostgreSQL, with EU providers for hosting and email, so no single vendor, and no single US point of failure, sits underneath the app. That's the practical answer to CLOUD Act and FISA §702 exposure for the app itself: a stack without a US lever in it. GitHub and Gemini are the exceptions, and each is yours to choose.
Self-hosting
Want it fully in your hands? Dialecto self-hosts on EU metal: an Elixir release and PostgreSQL, with an optional local Ollama for machine translation. Same product, your keys, your jurisdiction.
Audience
EU and regulated teams with GDPR or data-residency obligations — and anyone who has read enough subprocessor lists to prefer a tool that keeps the list short.
The security modelSee it on your strings.
Create your account and connect a repository: Dialecto reads only the translation files you confirm.