Skip to main content
Hyperlocalise Platform is infrastructure for multilingual content operations. Use native projects for content you manage in Hyperlocalise, or connect a supported translation management system for provider-backed workflows. Your team can choose its TMS while using Platform for the supported workspace operations.

​
What does TMS-agnostic mean here?

You can work with several supported TMS providers instead of moving every project to a single vendor. It does not mean every provider exposes the same review, automation, or editing features. Provider accounts, permissions, and project settings still apply.

​
Connected providers

This is a workspace overview, not a guarantee of every provider API operation. For example, a file API may be available even when the connector does not expose a Content Editor. POEditor and LILT AI have experimental CLI entry-sync adapters; that does not establish Platform project connections for them.

​
Native vs connected projects

Check Settings → Source connection to identify your project type. Connecting a provider does not automatically migrate projects or start translation.

​
Connect and verify a workflow

  1. Open Integrations, choose the provider, and complete its available connection flow.
  2. Verify that the intended provider account and project are accessible.
  3. Open the connected project and inspect its files and languages.
  4. Review one target locale using the available connector actions.
  5. Verify any saved changes in the provider before expanding the workflow.
If a project or action is missing, check connection troubleshooting and workspace roles. Credentials that can list projects may not have permission to change translations.

​
One CLI for your TMS workflows

The all-in-one Hyperlocalise CLI brings provider file commands, local AI translation, and checks into your repository or CI. Use hyperlocalise crowdin, lokalise, phrase, or smartling for the documented provider workflows. Use Platform file sync for native projects. Provider command credentials are separate from a Platform API key.

​
Can I switch TMS without changing my content workflow?

You can keep local CLI translation and checks, but must remap provider projects, locales, credentials, and delivery behavior. Test a small file before switching production automation. Glossary and translation-memory exchange do not migrate all tasks, permissions, history, or review state. Continue with Platform file formats, connected tools, or CLI compatibility.