Ship product updates in every language—from the same workflow.
Babely automates localization in your developer toolchain: run translations locally with the CLI, plug into CI/CD, review changes in Git, and keep locales aligned with every release.
│◇ What would you like to do?█│ Initialize a new Babely configuration│ Let's set up your i18n configuration│◇ What is your source language?│ English│◇ What languages do you want to translate to?│ es, pt, fr│◇ Where should language files be stored?│ src/locales/[locale].json│◇ What format should language files use?│ ● TypeScript (.ts)│ ○ JSON (.json)│ ○ YAML (.yml, .yaml)│ ○ Java Properties (.properties)│ ○ Android (.xml)│ ○ iOS Strings (.strings)│ ○ iOS Stringsdict (.stringsdict)│ ○ iOS XCStrings (.xcstrings)│ ○ Markdown (.md)│ ○ MDX (.mdx)│ ○ HTML (.html)│ ○ JavaScript (.js)│ ○ Gettext PO (.po)│ ○ XLIFF (.xlf, .xliff)│ ○ CSV (.csv)│ ○ XML (.xml)│ ○ Flutter ARB (.arb)│ ○ PHP (.php)│└ Configuration file and language files created successfully!│◇ babely translate│ Translating to Spanish (es)...│ Translating to Portuguese (pt)...│ Translating to French (fr)...│└ Successfully translated to 3 languages!
Everything you need to localize at speed
CI/CD translation workflow
Push code—Babely detects changes, updates translations, and opens pull requests you can review before merge. Locales stay current without blocking releases.
Simple pricing
Choose your usage tier
$67 billed annually · save 20%
500 Translated keys · 5 Translated documents
01234567
Excl. VAT
14-day free trial · no card required
We charge per key regardless of word count, for predictable pricing. For example: If you have 20 source keys (like "Sign Up" or "Welcome!") and translate them into 5 languages, that equals 100 translated keys (20 keys × 5 languages).