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

Comparison

Dialecto vs Tolgee

Tolgee keeps your translations in its database. Dialecto keeps them in your repository and sends every change as a pull request.

Advantages over Tolgee

  • Renames whole families of keys in every language, and rewrites your code to match.
  • Sends every change as a pull request, with one line of diff per change.
  • Edits your gettext files in place, keeping comments, order and wrapping.
  • Costs far less than Tolgee, 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 and source of truth

Translation storageTolgeeIn Tolgee's databaseDialectoIn the repository

Tolgee's tolgee pull writes your files from its database, so your repository holds an export of what lives on its servers. With Dialecto, your repository stays the source, and every change goes through your review. 1

EU hostingTolgeeEU and US serversDialectoIn the EU

Dialecto runs in the EU, and text leaves it only through a model provider you pick. Tolgee's privacy policy lists servers in Germany, the Czech Republic and the United States. 2

Self-hostingTolgeeLicensedDialectoAvailable

Both run on your own servers. 3

AI context

Curated contextTolgeeDescriptions, screenshots, memoryDialectoDomain, voice, audience, glossary

Both give the model more than the bare string: Tolgee sends key descriptions, screenshots, project and language notes and translation memory. Dialecto adds the domain each key belongs to, your brand voice and the audience you're writing for. 4

Model choiceTolgeeProvider of choiceDialectoLocal or hosted

Both take your provider. A self-hosted Dialecto can draft with a local model, so translations never leave your machines. 4

Key renames

Batch key renamesTolgeeOne key at a timeDialectoWhole families at once

Rename every basket.* key to cart.* in every language in one step. Renaming isn't among Tolgee's batch operations. 56

Call-site rewritesTolgeeBy 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 Tolgee.

Changes

Changes as pull requestsTolgeeOn Tolgee's roadmapDialectoOne line of diff each

With Tolgee, someone runs tolgee pull, commits and opens the pull request by hand. Git integration has been requested since 2023. 178

gettext round tripTolgeeRewritten on exportDialectoComments, order, wrapping

Tolgee's export drops comments and flags and sorts by key, so the first pull rewrites your catalog. It does keep contexts and every plural form. 91011

Editing

In-context editing in developmentTolgeeDevTools pluginDialectoPhoenix and Astro

Both let you click a translation on your running app and change it there. Dialecto's web editor groups translations by domain and checks them as you save. 12

Try the editor
In-context editing in productionTolgeeBrowser extensionDialectoDevelopment only

Tolgee's browser extension unlocks editing on production for anyone holding an API key. Dialecto's editor runs only while you develop. 12

Reach

Mobile and other formatsTolgeeMany, mobile includedDialectogettext and JSON

For a mobile app today, Tolgee is the better pick. 13

Runtime deliveryTolgeeSDKs and a CDNDialectoIn the build

Tolgee can serve translations at runtime, so text changes without a deploy. With Dialecto, translations ship in your build, and your site never calls us. 1314

Screenshots and FigmaTolgeeBothDialectoNeither

Tolgee attaches screenshots to keys, so translators see where text appears, and it has a Figma plugin. 13

Price

Free tier and team planTolgeeFree; from €69 a monthDialectoFree; Team from €XX

Tolgee's free tier covers 30,000 words and 3 seats, and paid plans start at €69 a month, or €58 billed yearly. Dialecto's free tier does real work, and Team costs far less than Tolgee's. 15

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 Tolgee

  1. Rename each key in Tolgee's editor, one at a time. 56

  2. Run tolgee pull to write your files from its database. 19

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

  4. Commit, and open the pull request yourself. 7

Effort

37 edits by hand: 14 key renames in Tolgee and 23 in your code, then a pull request you open yourself.

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 Tolgee

  1. Run tolgee pull once and commit, so your files hold every edit. 1
  2. Check your placeholders: Tolgee converts them on import, so confirm the files say %{count} where your code expects it. 16
  3. Connect Dialecto and confirm the paths of your translation files.
  4. Done. Your translations live 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. 1Tolgee CLI: push and pull stringsdocs.tolgee.io/tolgee-cli/push-pull-stringsread 6 October 2026
  2. 2Tolgee's privacy policy (where its servers are)tolgee.io/privacy-policyread 6 October 2026
  3. 3Tolgee: self-hosting with Dockerdocs.tolgee.io/platform/self_hosting/running_with_dockerread 6 October 2026
  4. 4Tolgee: AI translatordocs.tolgee.io/platform/translation_process/ai_translatorread 6 October 2026
  5. 5Tolgee: translation keysdocs.tolgee.io/platform/translation_keys/keysread 6 October 2026
  6. 6Tolgee: batch operationsdocs.tolgee.io/platform/translation_keys/batch_operationsread 6 October 2026
  7. 7Tolgee's roadmaptolgee.io/roadmapread 6 October 2026
  8. 8tolgee-platform issue #1542, git syncgithub.com/tolgee/tolgee-platform/issues/1542read 6 October 2026
  9. 9Tolgee's PO exporter, v3.226.0github.com/tolgee/tolgee-platform/blob/v3.226.0/backend/data/src/main/kotlin/io/tolgee/formats/po/out/PoFileExporter.ktread 6 October 2026
  10. 10Tolgee's PO importer, v3.226.0github.com/tolgee/tolgee-platform/blob/v3.226.0/backend/data/src/main/kotlin/io/tolgee/formats/po/in/PoFileProcessor.ktread 6 October 2026
  11. 11Tolgee's export query, v3.226.0 (sorted by key name)github.com/tolgee/tolgee-platform/blob/v3.226.0/backend/data/src/main/kotlin/io/tolgee/service/export/dataProvider/ExportDataProvider.kt#L104read 6 October 2026
  12. 12Tolgee JS SDK: in-context translatingdocs.tolgee.io/js-sdk/in-contextread 6 October 2026
  13. 13Tolgee's home pagetolgee.ioread 6 October 2026
  14. 14Tolgee: Content Deliverydocs.tolgee.io/platform/projects_and_organizations/content_deliveryread 6 October 2026
  15. 15Tolgee pricingtolgee.io/pricingread 6 October 2026
  16. 16Tolgee: the PO formatdocs.tolgee.io/platform/formats/poread 6 October 2026