Introducing Polyglot Automation

We built Polyglot around a deliberately narrow idea: i18n should feel like developer tooling. Scan, wrap, translate, and preview — in your repo, from your terminal, before you commit.

That workflow has a boundary, though. The moment a second person needs to sign off on a translation, or a team wants "no new untranslated strings" to actually mean something, you're past what a local CLI should do. Those are coordination problems, and they live where your team already coordinates: pull requests.

Today we're opening early access to Polyglot Automation for Team and Scale plans.

What it does

Checks on every PR. A native GitHub Check compares each pull request against its base and reports what's new, what's existing debt, and what got resolved. Your backlog stays visible; only new strings can block a merge — and only when you decide they should. Checks start informational.

Review in one place. Generated translations wait for a human yes. Reviewers see the source string, the context, and the exact diff — nothing ships without an approval.

Translation PRs, opened for you. Once translations are approved, Polyglot verifies the catalog-only change against a pristine base — your own checks have to pass on both — then opens a pull request. Your branch protections and review rules still decide what merges.

Built like something you'd let into your repo

We assumed you'd read the permissions screen carefully, because we would:

• Two separate GitHub Apps. The Checks App can't write repository contents. The Publisher App — a separate, optional install — can only push verified catalog branches and open pull requests.
• No long-lived secret in your repo. The managed workflow authenticates with GitHub OIDC; credentials are scoped to a single run and expire in minutes.
• Never a direct write to your default branch. Everything lands as a PR.
• Your repo keeps ownership — source files, catalogs, polyglot.toml, and the workflow itself, pinned to a commit SHA.

The free path stays open

The CLI and the open GitHub Action are available on every plan, including free — the Action even runs without an API key. Two lines in a workflow file and every PR gets checked:

- uses: polyglot-i18n/polyglot-action@v1
  with:
    check-mode: differential

Polyglot Automation is for the point where shared review and sign-off become the bottleneck, not before.

Polyglot Automation is in early access for Team and Scale — you can join from your dashboard. We'd love to hear how it fits your workflow: try it, and tell us what your team needs next.