Soft launchDialecto is still in testing, and details on this site may change as we finish it.

Edit your translations at AI speed.

Dialecto is domain-driven localization.

AI drafts and edits the text in your app, and your team reviews every change before it ships.

gettext · JSON · Phoenix first · built in the EU

  • lib/
  • config/
  • .env
checkout.po · french
# Shown when the charge fails.#: lib/shop_web/live/checkout_live.ex:88msgid "We couldn't process your payment."msgstr "Paiement refusé."msgstr "Nous n'avons pas pu traiter votre paiement."

the only line touched

Domain-driven

Come through to the workshop. Your translations arrive grouped by domain, each beside the line of code that shows it, and the keys are yours to reshape like no other service lets you, in your files and at their call sites. Rename one key or a whole family, every basket.* key to cart.*, in every language at once, and a public action in your repository carries each rename into the code that uses it.

Call-site rewrite

lib/shop_web/live/checkout_live.ex:88

put_flash(socket, :error, gettext("We couldn't process your payment."))

# Shown when the charge fails.

We couldn't process your payment.

Nous n'avons pas pu traiter votre paiement.french · staged
  • Placeholders
  • Plural forms
  • Glossary

Editing at AI speed

The whole workflow is built to stay out of your way. Machine translation drafts new text in your other languages, and your team reviews it before it ships. Edit fast in the web editor, on your running Phoenix or Astro app through the optional add-ons, or from your coding agent over MCP, with placeholders, plural forms and glossary terms checked on every change.

All features

Over MCP your coding agent does the same: list · stage · preview · open a pull request.

Surgical edits

Dialecto patches the lines an edit or a key rename touches and leaves the rest of each file as it found it. Setup needs no changes to your app's code, and every pull request is as small as the change it carries, so your reviewer reads the change and nothing else.

The minimal diff

Localize checkout (fr)acme/storefront · pull request #284

Open
Dialecto/translationsNothing left untranslated
Dialecto/qualityAdvisory · nothing flagged
Reviewed by InésApproved
PlaceholdersPlural formsCompletenessGlossary
#: lib/shop_web/live/checkout_live.ex:88 msgid "We couldn't process your payment."− msgstr "Paiement refusé."+ msgstr "Nous n'avons pas pu traiter votre paiement."

One line changed. Comments, order and wrapping stay exactly where they were; the rest of the file does not move.

Curated context

Your voice goes with every draft. Describe your brand voice and the audiences you write for once, and Dialecto hands them to the model doing the drafting, your own coding agent over MCP or ours, along with your domain, glossary and translation memory. Nothing a model drafts merges on its own.

Context and personas
Suggestion · Frenchlocal model · Ollama

Grounded in

  • Domain checkout
  • Glossary 2 terms
  • Translation memory 1 match
  • Voice Acme storefront · formal
  • Source code
Nous n'avons pas pu traiter votre paiement."paiement" per glossary · vous, never tu
Needs review

A person approves it before it ships.

Security

Dialecto can run with no access to your code at all. In Security mode your CI workflow sends only the translation files, and code snippets only when you choose to send them.

You don't have to take our word for it.

Security mode

Add a workflow file and a secret to your repository. Dialecto gets no access to it; your pipeline sends the files and opens the pull requests. The workflow file lists every path it sends, so your repository holds the limit, and you can read each line of it.

Convenience mode

Install the Dialecto GitHub App and you are done. Dialecto reads your translation files and opens pull requests for you. GitHub's permission covers the whole repository, so Dialecto's own code holds it to the paths you confirmed.

Built in the EU, and self-hostable on your own metal.

The security model

Reaches Dialecto selected files

  • priv/gettext/**/*.po and nothing else

If your pipeline also sends the few source lines around each string, a rename can follow its call sites. That, too, is your workflow's choice.

Never

  • Source code lib/ · app/ · src/
  • Secrets and environment .env · config/runtime.exs
  • Tests and assets
  • Git history
  • Every other file

File formats

We set the Phoenix table first. Dialecto patches gettext and JSON catalogs in place, and Rails YAML is in a private beta. Wrapping, comments, plurals and order all survive, because the file is never regenerated.

priv/gettext/fr/LC_MESSAGES/checkout.po gettext
# Shown on the confirmation page.msgid "Your order is on its way."msgstr "Votre commande est en route."

Phoenix firstand any .po or .pot

src/locales/fr.json JSON
"checkout": {  "shipped": "Votre commande est en route."}

Flat, nested, and browser extensionsflat catalogs also edit in context for Astro

config/locales/fr.yml YAML
fr:  checkout:    shipped: Votre commande est en route.

Railsprivate betaconfig/locales, existing values

For Elixir teams

Questions

What reaches Dialecto from my repository?

Dialecto reads only the translation files you choose. Code snippets come only from your own pipeline, when you choose to send them. With the GitHub App, Dialecto reads those files and opens the pull requests itself. In Security mode, Dialecto holds no access to your repository at all. Your own workflow sends the files and opens Dialecto's pull requests.

Do I have to migrate anything?

No. Your files stay in your repository, exactly as they are. Dialecto works on them in place and sends each change back as a pull request. Turn it off tomorrow and you've lost nothing.

Which formats and frameworks?

gettext (.po and .pot), JSON in its flat, nested and browser-extension shapes, and Rails YAML, which is in a private beta for the teams we invite, for editing existing values. Phoenix is the experience we polished first, and the in-context editor works for Phoenix and for Astro sites with flat JSON catalogs.

Can I bring my own model?

Yes, in three ways. Self-hosted, you can point Dialecto at your own Ollama server; we recommend translategemma:12b. Hosted, an owner can choose DeepL, which keeps your strings in the EU, or Gemini, which sends them to Google, and hosted translation is off until they do. Or your coding agent can translate over MCP with whichever model you use. We never claim the best translation model; we ground whichever one you choose in your domain, your glossary and your voice, and every suggestion still goes through review.

How is this different from a translation platform, or from the AI-native command-line tools?

The platforms keep your strings in their database and regenerate your files on the way back. The command-line tools regenerate them too, only faster: we ran two of their published loaders over a valid 104-line gettext file and got back 23 broken lines from one and a silently changed translation from the other. We keep the receipts. Dialecto never regenerates a file; it patches the line you changed and leaves the rest as it found it.

When can I use it, and what does it cost?

You can start now: sign up free and connect a repository. The free tier does real work, and Team is priced to be an easy yes when your team grows.

Start with one project.

Sit; the table's set. Install the app or wire up your pipeline, see your strings by domain, and ship the first clean pull request. Decide from there.

Freeone project, the domain editor, clean pull requests
Teamorganizations, review, the merge gate, curated context
Enterpriseself-hosted on your own metal, priority support

Nothing to migrate · no trackers on this site · no cookies