What is a translation management system?

It stores every piece of text in your product as a key with one value per language. Developers push new text from the codebase, translators work in one place instead of in spreadsheets, and finished translations are pulled back into the build.

How do I give one customer different wording?

Create a custom project. It starts as a copy of your default, you override only the strings that customer needs, and every other string keeps following the default -- so a later fix to shared wording reaches them automatically.

Can I use my own AI provider key?

Yes, on the Business plan. Connect Anthropic, OpenAI or DeepL and your text is processed under your own agreement with that provider. Free and Team plans translate on LocoLoop's own capacity.

Where is my data stored?

In the European Union. The database runs in Frankfurt and backups stay in the EU.

locoloop Sign in Start free

Ten file formats · REST API · MCP server · Hosted in the EU

Translation management
for everything you ship.
Plus a variant per client.

Every string your product ships, in one editor. Developers push from the build, designers pull text straight out of Figma, and translators and reviewers work with the context they need — while any client can have their own wording without you forking a file.

Start free — no card See how it works

✓ Free tier forever✓ Set up in an afternoon✓ Ten import and export formats

kestrel / ios / default 86% done

Key

🇩🇪 de-DE

🇫🇷 fr-FR

pay.confirm.title

Zahlung bestätigen

Confirmer le paiement

pay.confirm.body

Wir belasten Ihr Konto…

Nous débiterons…

wallet.empty.cta

Geld hinzufügen

Ajouter de l'argent

wallet.limit.warn

Tageslimit erreicht

inherited

support.email

help@kestrel.app

AI draft inherited from default 4,182 keys · 9 locales

Reads and writes the formats your stack already uses

React & i18next

iOS & SwiftUI

Android

Flutter

Rails

Django

Why teams switch

Spreadsheets don't survive a second customer

The moment one client wants different wording, most teams fork the whole string file. Then they maintain two. Then five.

One grid, all locales

Keys down, languages across. Keyboard-first editing that stays fast at 10,000 rows, with history on every cell.

Variants that inherit

A custom project copies your default. Override the three keys that differ; the other four thousand stay in one place.

AI that reads your glossary

Project context plus a locked glossary on every request. Or plug in your own model key and bill it yourself.

How it works

Import, translate, review, pull

Create your org

Email and password, or GitHub or Google. Invite whoever needs in.

Add platforms

iOS, Android, web, design files. Each gets its own locales and a default project.

Connect the source

GitHub, GitLab or Figma. Keys sync on push; translations return as a pull request.

Translate and pull

AI drafts each locale, reviewers approve, your build pulls the file.

Client variants

Sell the same app to ten customers. Keep one string set.

White-label clients always want their own words in a handful of places. A custom project gives them exactly that, and inherits everything else from your default — live.

→ Override any key, in any locale → Inherited cells stay marked, never hidden → Each variant gets its own endpoint and export

How variants work

Default projectsource of truth

wallet.name → “Wallet”
support.email → “help@kestrel.app”

iOS & SwiftUIcustom

wallet.name → “Konto”
support.email → inherited

Androidcustom

wallet.name → “Carteira”
support.email → “ola@caixa.pt”

AI translation

Context and glossary, per project

Give the model the brief you'd give a translator: tone, formality, do-not-translate terms, character limits.

Project context “Retail banking app for Germany. Address the user formally. Never translate Kestrel, IBAN or SEPA. Keep buttons under 20 characters.”

WalletKonto

React & i18nextdo not translate

AI & glossary →

Integrations

Keys sync themselves

Point locoloop at a branch and a path. New keys appear seconds after a push; approved translations come back as a PR.

GitHub

Push sync · PR back

GitLab

Push sync · MR back

Figma

Text layers as keys

Webhooks

Everything else

.xcstrings Android XML XLIFF JSON ARB +25 more

All integrations →

Developers

A REST API and an MCP server. Nothing to install.

We don't ship client libraries that go stale in six languages. Two endpoints get you translations, and the MCP server lets an agent read and write them directly.

Read the docs MCP server

Pull a locale Push keys MCP

curl -H "Authorization: Bearer $LOCOLOOP_KEY" \
  https://api.locoloop.dev/v1/projects/kestrel-ios-nordbank/export \
  ?locale=de-DE&format=xcstrings

→ 200 OK · 4,182 keys · 41 KB · etag W/"c8f1"

Security

Encrypted keys, scoped tokens, EU hosting

Your strings are product surface. We treat them like code.

Encrypted throughout

At rest and in transit. Your AI provider keys are encrypted and never returned by the API.

Scoped API keys

Read or write, pinned to a platform or one project. Revocable, with last-used timestamps.

Full history

Every cell records who changed it and from what — including AI and API actors. Revert anything.

Enterprise on request

SSO, white labelling and custom domains, built when an enterprise customer needs them.

Import your strings today. Ship nine languages this week.

Free for one platform and three locales. No card, no sales call.

Start free See pricing

Translation management for everything you ship. Plus a variant per client.