Continuous localization in the build you already have

There is no agent to install and no bot that needs write access to your repository. Three HTTP endpoints, one API key, and the CI system you are already running.

Three endpoints, and that is the API

Everything else in locoloop is built on these.

`POST /push`

Your English strings, upserted by value. Unchanged keys are a no-op; changed ones queue for translation.

`GET /pull`

One locale, resolved, in that platform's native file format. ETag-aware, so an unchanged pull is a 304.

`GET /status`

Per-locale progress, review counts, and the plural forms still missing — the thing you gate a release on.

Pick your pipeline

GitHub ActionsAvailable

A workflow that pushes on merge and opens a pull request with the translations.

GitLab CIAvailable

Two jobs and a masked variable. Artifacts carry the translated files to the next stage.

Bitbucket PipelinesAvailable

One shared step definition, one secured repository variable.

Or talk to it directly

Two surfaces for everything the CI recipes do not cover.

REST API

The same endpoints your build uses, with scoped keys you can pin to a single platform and revoke on their own.

MCP server New

Give a coding agent read and write access to the workspace, so it can add the strings it invents while it writes the feature.

On the roadmap

Listed because the navigation mentions them and you deserve a straight answer: these are not built yet. Tell us which one you need and it moves up the list.

FigmaPlanned

Pull the strings out of a design file before the screen is built, and push the approved wording back.

SlackPlanned

A message when a locale finishes, and when a string you own is flagged for review.

WebhooksPlanned

An HTTP callback on the same events, for whatever you run that is not Slack.

Connect it to your build

A workspace, an API key and one CI job. Free while you are evaluating.

Start free Log in Book a demo