Skip to main content
Hyperlocalise is an all-in-one localization CLI with provider-specific file commands and a shared entry-sync workflow. Keep local AI translation and checks in the same tool you use to move content to and from supported translation platforms.

​
What is a TMS-agnostic localization CLI?

A TMS-agnostic CLI lets you choose among supported translation management systems without tying local translation and checks to one vendor. In Hyperlocalise, you choose your AI provider separately from your TMS. Changing TMS still requires new credentials, project IDs, locale mappings, and a review of provider behavior.

​
Supported TMS commands and adapters

Check each command reference for supported flags and compatibility gaps. Adapter maturity does not imply feature parity with a provider’s official CLI. Pin a tested release in CI and consult the stability matrix.

​
Choose the right workflow

​
Provider file commands

Use hyperlocalise crowdin, lokalise, phrase, or smartling for provider file uploads, downloads, and the operations listed above. These commands use provider APIs and their own configuration. Their file support depends on the provider and operation, not just the local CLI parser. Start with Crowdin approved translations, Lokalise imports, Phrase configuration reuse, or Smartling published downloads.

​
Shared TMS entry sync

Use sync push and sync pull with storage.adapter in i18n.yml for Hyperlocalise-managed translation entries. This experimental path reads flat JSON from the first bucket’s files[].to mapping (bucket names sorted). Use one concrete .json target path template. Nested JSON, contextual entries, other formats, and globs are not supported on this path. Entries use key, context, and locale as identity. Sidecar files keep provenance and draft/review state separate from user-facing translation text.
  1. Generate drafts with run.
  2. Preview and send entries with sync push --dry-run, then sync push.
  3. Curate translations in your TMS.
  4. Preview and retrieve entries with sync pull --dry-run, then sync pull.
Push protects curated remote values by default. Pull can apply curated-over-draft updates when enabled. Read conflict rules before using overwrite options.

​
Platform file sync

Use a top-level hyperlocalise block for Platform file sync. sync push uploads source files; sync pull retrieves project translations. If both hyperlocalise and storage are present, Platform sync takes precedence. Use separate configurations when you need both destinations.

​
Does Hyperlocalise replace my TMS or its official CLI?

Hyperlocalise works with your TMS. Your provider still owns its projects, review workflow, and provider-specific settings. The file commands are alternatives for the documented tasks, not replacements for every official command. Each provider reference includes a comparison and unsupported features.

​
What changes when I switch TMS?

Keep your local translation and checks, then configure the new provider’s account, project, locales, and file mappings. Verify a small upload/download cycle before changing CI. Exporting translation memory or a glossary does not migrate review history, tasks, permissions, or every provider-specific field. For connected workspace review, see Platform TMS integrations.

TMS webhook automatic sync

How Hyperlocalise registers inbound TMS webhooks, reconciles remote changes, and falls back to manual setup.

Crowdin adapter

Configure Crowdin for native sync mode or Crowdin-compatible file mode.

LILT AI adapter

Configure LILT AI for remote translation pull/push synchronization.

Lokalise adapter

Configure Lokalise API v2 for pull/push synchronization.

Phrase adapter

Configure Phrase for native sync mode or Phrase-compatible file mode.

POEditor adapter

Configure POEditor for sync pull and sync push.

Smartling adapter

Configure Smartling for native sync mode or flag-driven file commands.