Keep localization in your release plan: see what needs translating, review translations in the dashboard, and ship them in their own pull request. Your team decides when the localized feature is ready.
Polyglot Automation (early access on Team and Scale) keeps catalogs in sync with your main branch. Every generated translation waits for human review. Once approved, Polyglot opens a separate pull request with just the translations, and your team merges it. Plan the localized release around those steps and your usual app checks.
Plan for generation, human review, verification, and a catalog PR merge.
Localization stops being a black box you can only ask about.
Track translated entries and pending review by language, so you can scope the work before it hits the release.
Spin up a new language to test demand in a market without committing a localization budget or a multi-week project up front.
Checks flag new untranslated strings in each pull request. Pair them with language review and your usual app testing before you call a release ready.
Languages benchmarked
Translation quality
Reviewer seats
Languages on Team
Generation is one step. Allow time to review the language, merge the translation PR, and test the localized app. How long that takes depends on your content, your reviewers, and your release process.
Start with the CLI and open GitHub Action on any plan. Team adds managed checks, catalog sync, and verified translation PRs.
For individual developers
For growing teams
Polyglot Automation is in early access. Setup and availability
For large projects
Polyglot Automation is in early access. Setup and availability
Try it out — no card, no commitment.
Start in your terminal
See how few steps a localized launch actually takes. The first 50 translations are free, no account required.