[For engineering managers]

Ship to a new market on your normal release cycle, not a side project.

Localization usually pulls your best engineers off the roadmap for an open-ended slog. Polyglot turns it into a bounded task you can gate in CI — predictable enough to put on a sprint board.

$curl -fsSL https://getpolyglot.ai/install.sh | bash

Free to start · no account required · no credit card

polyglot — zsh
$ polyglot scan
✓ Found 43 string(s) across 6 file(s)
$ polyglot wrap
✓ Wrapped 43 string(s) in 6 file(s)
$ polyglot translate --languages de,fr,ja
de: 43 translations
fr: 43 translations
ja: 43 translations
Done! 129 strings translated across 3 languages.
$ polyglot preview --lang de
Preview ready at http://localhost:3000
[01]The difference

Why i18n blows estimates.

The work isn't the translating — it's everything around it. Polyglot removes the parts that don't fit in a planning poker round.

i18n as an open-ended project

An engineer hand-audits the codebase for hardcoded strings
Wrapping and wiring up t() calls is days of tedious refactoring
Translation turnaround is an external dependency you can't schedule
Missing-string regressions surface as production support tickets

i18n as a bounded task

One scan command lists candidates with file and line
polyglot wrap does it with a reviewable diff
Translation runs through the API, then waits for review — no vendor round-trip
Differential CI surfaces new findings in pull-request review
[02]No surprise i18n debt

It can't silently rot between launches.

The expensive failure mode isn't the initial translation — it's the slow drift afterward, as new features ship English-only and nobody notices until a market complains. Polyglot can check each pull request, distinguish new debt from the baseline, and enforce policy after the team deliberately enables it.

The open Action reports differential findings; Polyglot Automation adds native Checks
Coverage is a number you can check per language
Translation memory means re-runs are near-instant and free

# CI check on a feature PR

polyglot scan --ci

Coverage: 100% (de, fr, ja)

✓ No untranslated strings introduced

# next PR adds an un-translated string

polyglot scan --ci

✗ 1 untranslated string · build failed

src/billing.tsx:23 "Upgrade plan"

[03]By the numbers

The numbers that show up in your planning

1

Command to scope the work

polyglot scan → audit report

$0

Open GitHub Action

catches new strings in every PR

4.96/5

Translation quality

June 2026 · AI-judged

5

Developer seats on Team

reviewers always free

[04]Workflow

How a localized launch actually goes.

Four steps, all scriptable, none of them blocked on a vendor or a specialist.

01

Scope it

$ polyglot scan

polyglot scan lists the candidate strings the launch touches and where they live — a solid first count to scope against.

02

Wire it

$ polyglot wrap

polyglot wrap extracts strings into message catalogs with a diff your team reviews like any PR.

03

Translate it

$ polyglot translate

polyglot translate fills every target language in one pass, reusing anything already translated.

04

Gate it

$ polyglot scan --ci

Add the differential check to CI and establish the baseline, so every pull request afterward shows what it added rather than what the repository already owed. Policies that block a merge are in early access.

[05] Questions

What engineering managers ask

Run polyglot scan on the target scope — it reports candidate strings and the files they live in. Wrapping and translating are bounded steps, so you get a solid first count to put on a board instead of a multiplier-laden guess. Check it against the screens you’re shipping.

[06]Pricing

Pricing that grows with you.

Start with the CLI and open GitHub Action on any plan. Team adds managed checks, catalog sync, and verified translation PRs.

MonthlyAnnualSave up to 20%

Pro

For individual developers

$39/month
billed annually
Get started today
10,000 strings
5 languages
Unlimited characters
Glossary overrides
Async translation
Email support

Team

Best value

For growing teams

$119/month
billed annually
Get started today

Polyglot Automation is in early access. Setup and availability

25,000 strings
15 languages
3M characters/mo
5 developer/admin seats
Reviewers free — invite as many as you want
Polyglot Automation — native checks, catalog sync & translation PRs
Review workflow & team roles
Shared glossaries
Email support

Scale

For large projects

$449/month
billed annually
Get started today

Polyglot Automation is in early access. Setup and availability

Everything in Team, including Polyglot Automation
Unlimited strings
Unlimited languages
25M characters/mo
15 developer/admin seats
Priority support
Audit log

Free

$0

Try it out — no card, no commitment.

500 strings2 languagesUnlimited charactersUnlimited detectionOr try 50 strings without an accountLocal checks + open GitHub Action

Start in your terminal

Put localization on the board.

Run a scan on the repo you’re planning to localize and get a string count in seconds. The first 50 translations are free. When every pull request needs a native Check and translations need team sign-off, Team adds shared review and translation PRs (Automation is early access) — flat price, five developer seats, reviewers free.

$curl -fsSL https://getpolyglot.ai/install.sh | bash
Polyglot for Engineering Managers — Ship to new markets without slowing down | Polyglot