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

Comparison

Dialecto vs Lingo.dev

Lingo.dev translates each push on its servers and commits the result. Dialecto keeps your team in charge of every line, and rewrites your code when you rename a key.

Advantages over Lingo.dev

  • Runs on your own server and drafts with a local model, if you choose.
  • Renames whole families of keys in every language, and rewrites your code to match.
  • Lets you edit a translation by clicking it on your running Phoenix or Astro app.
  • Costs far less than Lingo.dev, with a free tier that does real work.

We make Dialecto, so we're biased. Every claim links to its source, checked 6 October 2026.

Feature comparison

Security

EU hostingLingo.devEU database, global edgeDialectoIn the EU

Lingo.dev's database is in Frankfurt and its app runs on Cloudflare's global network; EU data residency is an Enterprise option. Dialecto runs in the EU, and text leaves it only through a model provider you pick. 12

Drafting with a local modelLingo.devDeprecated CLI onlyDialectoWith self-hosting

Lingo.dev's legacy CLI could call a local Ollama model; its current CLI and GitHub App translate on Lingo.dev's servers. A self-hosted Dialecto drafts with a local model, so translations never leave your machines. 34

Self-hostingLingo.devNone foundDialectoAvailable

Dialecto runs on your own servers if you'd rather keep everything in your hands. We found no self-hosted option in Lingo.dev's docs or plans. 2

SOC 2 Type II reportLingo.devOn EnterpriseDialectoNo report

Lingo.dev shares a SOC 2 Type II report with Enterprise customers. Dialecto has no such audit yet; the code that runs in your repository is public for you to read. 2

AI context

Curated contextLingo.devGlossary, rules, brand voiceDialectoDomain, voice, audience, glossary

Both give the model your glossary and brand voice. Dialecto also tells it which part of your product a translation belongs to, from the domain its key lives in, and the audience you're writing for. 5

ValidationLingo.devScored to custom criteriaDialectoChecked on every change

Lingo.dev scores every translation against criteria you set. Dialecto checks placeholders, plural forms and glossary terms on every change, and its merge gate holds back pull requests with new untranslated strings. 6

Native-speaker proofreadingLingo.devEnterprise add-onDialectoNot offered

Lingo.dev sends translations to native-speaking proofreaders before they go live, priced per word on Enterprise. Dialecto leaves the words to your team and your model. 26

Key renames

Batch key renamesLingo.devNone foundDialectoWhole families at once

Rename every basket.* key to cart.* in every language in one step. We found no rename feature in Lingo.dev's docs, so there you edit each file. 4

Call-site rewritesLingo.devBy handDialectoIn the same pull request

Dialecto rewrites every place your code uses a renamed key, and lists anything it can't rewrite safely. We found no such feature in Lingo.dev.

Changes

Changes as pull requestsLingo.devFrom Lingo.dev's GitHub AppDialectoOne line of diff each

Lingo.dev's GitHub App commits translations to its own branch and opens a pull request, or commits to your pull request's branch. Dialecto opens one for each change you approve. 7

gettext round tripLingo.devPartly, in testingDialectoComments, order, wrapping

Lingo.dev's legacy CLI, 0.138.9, kept comments but dropped obsolete entries, unwrapped long lines and turned the checkout button's “Commander” into “Commande”. Its current CLI parses files on Lingo.dev's servers, so we couldn't test it. 48

Editing

In-context editing in developmentLingo.devReact compiler, in alphaDialectoPhoenix and Astro

Lingo.dev's React compiler, in alpha, includes an in-browser translation editor; we found none for its CLI or GitHub App. Dialecto's runs on your Phoenix or Astro app while you develop. 9

Team review in the appLingo.devOn EnterpriseDialectoIn the web editor

Lingo.dev's review stage for your own team comes with Enterprise; otherwise your team reviews the pull request. Dialecto's editor groups translations by domain and checks them as you save. 2

Try the editor

Reach

Formats beyond gettext and JSONLingo.dev18, Markdown and mobileDialectogettext and JSON

Lingo.dev's CLI reads 18 formats, from Markdown and MDX to Android and Xcode. For docs or a mobile app today, Lingo.dev covers more. 10

CMS and emailLingo.devPayload and MailchimpDialectoRepository files only

Lingo.dev also localizes content in Payload and campaigns in Mailchimp. Dialecto works on the translation files in your repository. 6

Price

Free tier and team planLingo.devFree; from $99 a monthDialectoFree; Team from €XX

Lingo.dev's free Sandbox allows 100,000 tokens a day, and Production costs $99 a month plus usage. Dialecto's free tier does real work, and Team costs far less than Production. 2

Example

Renaming translation keys

Your product says “cart” now, but your keys still say basket, so everyone who works on checkout reads one word in the code and another on the screen.

Rename every basket.* key to cart.* and ship it.

With Lingo.dev

  1. Rename the keys in each language file yourself.

  2. Find every t("basket.…") in your code and fix it by hand.

  3. Push, and review the pull request its GitHub App opens. 7

Effort

65 edits by hand: 14 keys in each of 3 language files, and 23 places in your code.

With Dialecto

  1. Rename basket.* to cart.* in the editor, and every language follows.

  2. Review the pull request Dialecto opens; the checks have already run.

Effort

One rename: Dialecto changes the 14 keys in 3 catalogs and the 23 places in your code, in one pull request.

Done by hand, a rename touches every language and every call site, so teams have always lived with the old names. Dialecto makes it one step, so your keys can change as often as your product does.

Moving from Lingo.dev

  1. Remove Lingo.dev's GitHub App or CI step, and its configuration and lock files. 7
  2. If you used its legacy CLI, check what it changed in your gettext files and restore anything you want from git. 8
  3. Connect Dialecto, confirm the paths of your translation files, and bring your glossary across.
  4. Done. Your translations stay in your repository, and Dialecto opens the next pull request.

Leaving Dialecto

Your translations already live in your repository, exactly as you approved them, so there's nothing to export. Disconnect Dialecto and keep working.

Rename your keys in one step, on your own repository.

Create your account, connect your repository, and your first change arrives as a pull request your team reviews.

Sources, checked 6 October 2026
  1. 1Lingo.dev's privacy policy (where its data is)lingo.dev/en/legal/privacyread 6 October 2026
  2. 2Lingo.dev pricinglingo.dev/en/pricingread 6 October 2026
  3. 3Lingo.dev: the legacy CLI's configuration (deprecated; model providers)lingo.dev/en/docs/cli-legacy/configurationread 6 October 2026
  4. 4Lingo.dev: the CLIlingo.dev/en/cliread 6 October 2026
  5. 5Lingo.dev: localization engineslingo.dev/en/docs/platform/enginesread 6 October 2026
  6. 6Lingo.dev's home pagelingo.dev/enread 6 October 2026
  7. 7Lingo.dev: the GitHub Applingo.dev/en/docs/workflows/github-appread 6 October 2026
  8. 8Our receipts: lingo.dev 0.138.9's PO loader, run on two catalogs, with the runner and hashes/compare/receiptsread 6 October 2026
  9. 9Lingo.dev Compiler (alpha)lingo.dev/en/docs/react/compilerread 6 October 2026
  10. 10Lingo.dev: file formatslingo.dev/en/docs/cli/formatsread 6 October 2026