The license and the status line in the summary
ReviewGate is free: no license key is needed and the whole engine is available. At the foot of every summary the bot shows an informational status line — License: Community with a «Support the project» link (the project lives on donations). The language of the line follows the language key in .reviewgate/config.yml (English by default); with language: ru the same line reads Лицензия: Community. The line restricts nothing: it is an honest marker of how the deployment runs.
Community is the whole engine
Community status cuts nothing down: not the number of developers, not the languages, not the features. Team rules, the judge, the gate, committable suggestions, the CLI, the hook and MCP all work.If you already have a key
Previously issued keys keep working: the status line shows the plan and the organisation from the key (Enterprise · your organisation · perpetual, for example). The key goes into the bot's .env:
REVIEWGATE_LICENSE=eyJhbGciOiJFZERTQS...docker compose up -d app
docker compose logs app | grep -i license
# License active: plan=startup, term=...Community to your plan, the key has been applied.docker compose logs — are always in English, whatever language says: that key governs what the team sees in a pull request, not the operator log. Older images wrote those lines in Russian — if the grep above finds nothing, your deployment predates the change. Everything a developer sees — the summary, the inline comments, the CLI — follows language and is English by default.The offline check
A key is a signed JWT (the plan, the seat count, the term). The bot verifies the signature locally with a built-in public key — with no calls to the internet. That works in an air-gapped deployment too and creates no outbound connections (see Security).
Community with the reason in brackets, and nothing breaks.