Translation management for software teams. Every language, and a variant per client.
Every string your product ships, in one editor. Developers push from the build, AI drafts each language from your glossary, and reviewers who speak it approve before it ships — while any client can have their own wording without you forking a file.
Free for one platform and three languages. No card, no sales call.
A translation management system for software teams
Your product's strings live in a repository, not a content calendar. locoloop treats them that way: keys sync from your codebase, translations come back as a pull request, and the whole set stays reviewable like any other change.
One grid, every language
Keys down, languages across. Keyboard-first editing that stays fast at ten thousand rows, with full history on every cell and the actor recorded — human, AI or API.
Variants that inherit
Sell the same app to several customers and each will want its own wording somewhere. Copy the default, override the handful of keys that differ, and let the rest read through.
AI that reads your glossary
Machine translation without context produces confident nonsense. Give the model a project brief and a locked glossary, and every draft arrives in your tone with your product names intact.
Built for your pipeline
A REST API, an MCP server for agents, webhooks, and thirty-odd file formats in both directions. No SDK to install and none to keep up to date.
Set it up once, in about an hour
After that it runs on its own: keys arrive when someone pushes, drafts appear, reviewers approve, and your build pulls the file it needs.
Create your organisation
Sign up with email, GitHub or Google. Name the organisation and pick the language your team writes in.
Add a platform
One per shipping surface — iOS, Android, web app, design files. Each gets its own languages, key namespace and a default project.
Connect the source
Point locoloop at a branch and a path in GitHub, GitLab or Bitbucket — or pull named text layers straight out of Figma.
Translate and pull
AI drafts each language, your reviewers approve, and the build pulls an export — or takes the pull request locoloop opened for it.
Context and glossary, per project
Set a project brief once and every request carries it: what the product is, which words must never change, how long a button label can run — and whether this language addresses the reader formally.
A draft that breaks a glossary rule or a length limit is rejected and retried before it reaches the grid. 100,000 AI words included, or your own key on Business and up.
AI translation →Glossary →Keys sync themselves
New keys appear in the editor seconds after a push. Approved translations come back as a pull request you review like any other change.
Import and export are symmetric — plurals, placeholders, comments and nesting all survive the round trip.
A REST API and an MCP server. Nothing to install.
A two-line curl in your build script has no dependency to update, and six half-maintained client libraries are worse than none. The OpenAPI spec is there if you want to generate your own.
The MCP server lets an agent in Claude or Cursor look up what a key means, propose a translation, or check a term against your glossary — scoped to the permissions of the key you gave it.
Product strings, and only product strings
locoloop is built for the words inside software. Campaigns, landing pages and long-form content need a different tool, and we would rather say so than sell you one.
JSON, YAML, gettext and framework-native formats.
String catalogs, Android XML, Flutter ARB, with correct plural forms.
Product surfaces of a site — navigation, forms, checkout, account.
Figma text layers, so a screen can be reviewed in any language before it ships.
Invite anyone, scope them tightly
Access can be granted at organisation, platform or project level — so a contractor translating for one client sees that client's project and nothing else.
Encrypted keys, scoped tokens, EU hosting
Your strings are product surface. We treat them like code.
Start from the job you arrived with
The same workspace, five quite different weeks.
Pull every locale into the bundle at build time, from the CI you already run.
Mobile appsNative formats, CLDR plurals, and a gate so an untranslated string never reaches a store.
WebsitesMarketing copy where a literal translation costs you the most.
White-label and reseller wordingA variant per customer that overrides what differs and inherits the rest.
Continuous localizationPush on merge, pull the finished files back, gate the release on progress.
Outside translatorsScope an agency to one app and a freelancer to one language.
Import your strings and see it working in ten minutes
Free for one platform and three languages, for as long as you like.