Keys follow the code
The push command sends the whole scan in one request and marks what disappeared, so the catalog does not grow with dead keys.
CLI, Git and QA in one flow
Keys live in your code. BabelHub scans them, checks placeholders, ICU and HTML before a release, and hands the app only the approved catalogs.
Free plan: 2 projects, 2 languages per project, 500 keys. No card required.
Every promise below maps to a feature that is already shipped, not to a roadmap.
The push command sends the whole scan in one request and marks what disappeared, so the catalog does not grow with dead keys.
Missing placeholders, broken ICU, HTML and glossary terms are caught while the text is still being edited — not by a user on production.
Gates block a release with errors, and the app receives exactly the catalogs that passed, with a version and fingerprint.
Four commands and one browser window. The onboarding wizard waits for a real push, not for a click.
Install the CLI, sign in, and describe the project — source language and target languages.
composer global require babelhub/cli
babelhub login
babelhub init
One request sends the keys, their source texts and what disappeared from the code.
babelhub push
Translators work in the panel, reviewers approve. Roles decide who can publish.
A release freezes the approved catalogs. The pull command writes files into your app.
babelhub pull
The steps are described in the documentation. The in-app onboarding walks through the same flow. Docs
Every plan includes the CLI, Git integration and basic QA. Paid plans add memory, webhooks and release management.
79,00 PLN
per month
Create an account, set up the first project, send your keys. The wizard shows the real state of the push.