Product · Babely

Ship product updates in every language—without changing how you work.

Babely keeps translations in sync with your repo: run the CLI locally with npx @babely/cli@latest, wire in CI/CD if you want, and review updates like any other Git change—your locale files stay aligned with every release.

npm package @babely/cli

Start automatingExplore the docs

3-day free trial

CLI on npmGitHub Action3-day free trial
Babely CLI
│◇ 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!│◇ npx @babely/cli@latest 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

Automated translation runs
Generate and refresh translations from your source files so multilingual releases stay on pace with development.
@babely/cli on npm
Install with npx @babely/cli@latest, pull updates, validate keys, and push translations from your terminal—without breaking your existing workflow.
Markdown & docs in sync
Translate Markdown and structured content alongside app strings so documentation matches each locale.
Brand voice & terminology
Tune tone and vocabulary so translations stay consistent with your product narrative across markets.
GitHub-native automation
Use our GitHub Action to translate on commits or PRs and open reviewable changes automatically.
Works with your i18n stack
Keep your current libraries and formats—Babely fits into the tooling you already use.

From strings to shipped locales

Translation quality
  • Context-aware suggestions that respect UI constraints
  • Consistent tone and voice across locales
  • Shared glossary and preferred terms
  • Pluralization, placeholders, and formatting handled safely
  • Refresh translations as source content changes
  • Human-approved overrides when you need precision
Workspace setup
  • Connect your repo and configure languages in minutes
  • Invite teammates with the right permissions
  • Fine-tune tone, rules, and locale behavior
  • Pick source and target languages per project
Built into engineering
  • @babely/cli — local runs and scripting
  • First-class CI/CD hooks
  • GitHub Action for automated PRs
  • Review translations like code before merge
  • Clear guides from install to production
Start automating

3-day free trial

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.

Git push
Babely Engine
EN
English
ES
Spanish
JA
Japanese
Merge pull request
Deployed

Simple pricing

3-day free trial

Starter

$2.39/ month

Save 20% with annual billing

500 keys

5 documents

Start automating

Pro

$7.99/ month

Save 20% with annual billing

5,000 keys

25 documents

Start automating
Most popular

Scale

$23.99/ month

Save 20% with annual billing

50,000 keys

500 documents

Start automating

Enterprise

$159.99/ month

Save 20% with annual billing

100,000 keys

1,000 documents

Start automating
  • Unlimited projects
  • GitHub Action integration
  • Translation overrides
  • Fine-tuning options
  • Advanced analytics
  • Custom brand voice
  • Context memory
  • Priority support

Excl. VAT · 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).

Explore Babely

Solutions by stackDocumentationBabely vs LokaliseBabely vs Crowdin

FAQ

Next step

Ship every locale from the same pipeline.

Sign in with GitHub or Google, connect your workspace, and sync translations with the @babely/cli npm package or CI/CD—so updates roll out in every language without slowing releases.

Start automating

3-day free trial

Solutions

Contact

Babely

© 2026 Babely. All rights reserved.