Skip to content
the transglot oss grantgranted, not purchased

The Team plan, free, for public projects.

A maintained open-source project can apply for the OSS grant and get everything the $49 Team plan has: 1,000,000 words a month, unlimited projects, languages and seats. It costs nothing and it is hard capped, so it can never produce a bill.

Without
With

Community translators send pull requests against a JSON file, and the plurals lose.

Twenty formats read and written natively, and a language missing a plural form is refused rather than shipped.

The translation tool has a free plan that stops at three languages.

The grant carries unlimited languages and unlimited seats, so every contributor can have one.

Nobody wants an invoice arriving because a release got popular.

The grant is hard capped and never metered, so a busy month cannot produce a bill.

Transglot itself is a hosted application whose source is private. Our CLI is MIT licensed and published on npm, and the GitHub Action is MIT with a public repository. The grant is the part of this that is free, and it is genuinely free.

how it works

Your repository goes in. Every language comes back, plurals correct.

five steps: a public repository, the GitHub Action, the translation pass, the plural check, the same pull request with a badge for the README
solutions · route consolesolutions / openSourceOpen source

steps · Open source: A public repository → The GitHub Action → Glossa Flux → The plural gate → The same pull request

what goes inA public repositorythe JSON file your contributors send pull requests against
how it gets thereThe GitHub ActionMIT licensed, public repository, drafts on push
which passGlossa Fluxevery push, and the plural gate does the arguingFluxDeepthe fast pass, on every push
the checkThe plural gatea locale missing a form is refused, so the plurals stop losingplaceholderspluralsglossarylengththe check that catches it here
what comes outThe same pull requestplus a localized-with badge for the README
an illustrative first weekOpen source
grant · applied · read by a person
granted · team-level · hard capped
seats, locales, projects · unlimited
push · plural check · ru-RU few, many · held
pull request · every locale, forms complete
bill · none, ever
the plan that fits
The OSS grant$0a month
  • 1,000,000 words a month, hard capped
  • Unlimited projects, locales and seats
  • The Team feature set, unchanged
Granted, not purchased: a person reads the application, and the cap means it can never meter.
See all eight pages
every one of them starts on the same free plan
A fixture, in your browser. The five steps, the two passes, the four checks and the plan rows are the shipped mechanism and the shipped price list; the first-week tape is illustrative and nothing on this plate is sent anywhere.

What the grant is, and what it is not.

The OSS grant
real, and free
What is free
Everything the $49 Team plan has, on a granted plan: 1,000,000 words a month, unlimited projects, languages and seats.
Is the platform open source
No. Transglot is a hosted application and its source is private. The CLI is MIT on npm, and the GitHub Action is MIT with a public repository.
Can you self-host it
Not today. Packaged and air-gapped self-hosting is on the Enterprise roadmap, and that is the whole of the claim.
How you apply
A public form. A person reads it, and approval moves your organisation onto the granted plan.
What it costs later
Nothing. The grant is hard capped rather than metered, so it cannot produce an overage bill.
The grant is a plan in the shipped configuration, with its own hard cap. The licensing answers above are deliberately the narrow, true ones.
grantednot purchased
the grant

One application, then the Team plan at $0.

The grant exists because a project that adopts us is worth more to us than a subscription. A person reads your application and switches it on. There is no checkout path at all.

One application,
What the grant givesTerms
The OSS grant
public, maintained projects
Free, reviewed by a person
Allowance
never meters, so no overage is possible
1,000,000 words a month, hard capped
Projects, languages and seats
every contributor can have a seat
Unlimited
Features
the Team feature set, unchanged
Quality mode, glossary, API, webhooks and the CDN bundle
Badge
a public endpoint, cached at the edge
A localized-with SVG for your README
Apply for the grant
No card, no checkout, and no automatic upgrade at the end of anything.

FAQs

Including the awkward ones, answered first.

Is Transglot open source?
The hosted product is not. Our CLI is MIT licensed and published on npm, and the GitHub Action is MIT with a public repository. The application itself, including the engine and the format codecs, is private.
Apply for the OSS grant. The form asks for the repository and a short description, a person reads it, and approval moves your organisation onto a granted plan carrying everything the $49 Team plan has: 1,000,000 words a month, unlimited projects, languages and seats. There is no card and no checkout anywhere in that path.
A public, maintained project with real users. A person reads the application rather than a rule, so there is no star count to hit and no batch to be in.
There is no expiry built into it and no card behind it, so nothing renews and nothing lapses on its own. If the project outgrows the allowance, or stops being maintained, that is a conversation rather than an automatic charge.
Nothing arrives on a card, because there is no card. The grant is hard capped, so the run stops rather than metering, and you can talk to us about the cap.
Give them a seat. Seats are unlimited on the grant, and access can be scoped to a single language, so a contributor who speaks Polish gets Polish and nothing else. Their work lands in the same pull request as everything else rather than as a hand-edited JSON diff.
That is the check that exists for this. Every plural category the target language declares has to be present, drawn from the 224 CLDR plural languages, so a Russian or Arabic row missing a form is refused rather than merged. Seven of the 20 formats carry plurals natively, including gettext PO, Android XML and Flutter ARB.
Twenty, as they are: flat and nested JSON, gettext PO, YAML, Android XML, iOS strings, stringsdict and xcstrings, Flutter ARB, XLIFF 1.2 and 2.0, Laravel PHP and JSON, Java properties, .NET RESX, CSV, XLSX, Markdown, Unity Localization CSV and Unreal PO. Your schema comes back the way it went in.
Yes, a localized-with SVG served from a public endpoint and cached at the edge, so GitHub can hammer it without hitting us. It is offered, not required.
No. Your strings go to our AI subprocessors for inference only, under commercial terms, and the trust page names each one. The shared exact-match memory pool is anonymised and can be switched off per project.
Not today. Packaged and air-gapped self-hosting is the single item on the Enterprise roadmap here, and until it ships we do not sell it or describe it as available.
Projects that adopt us, and a badge in a README. That is the whole trade, and it is why the grant is hard capped rather than a trial that turns into a subscription.
works with what you already run

41 connectors, already built.

granted · hard capped · no card

Apply once, then ship in every language your contributors speak.

Everything the $49 Team plan has, at no cost, reviewed by a person, and capped so the grant can never meter.