Skip to content
ReRune

Localization API for teams that automate product text.

The ReRune CLI, the MCP server, and your own server-side scripts manage translation data with an API key in the X-API-Key header, under the same permissions as the dashboard. Apps read published text with a separate, read-only OTA Publish ID.
Start localizingSee workflow
ReRune projects list showing real localization projects in a workspace
ReRune dashboard showing localization workspace activity and project statusReRune dashboard showing localization workspace activity and project statusReRune dashboard showing localization workspace activity and project status
ReRune OTA demo mobile app landing screen with live localization status

Common challenge

Manual exports stop scaling when localization must reach multiple product surfaces, release branches, and internal systems.

Best fit

Localization workflows that must connect with internal tools, dashboards, build steps, release automation, or custom product systems.

How ReRune helps

ReRune keeps API automation tied to the same workspace where translation context, glossaries, AI assistance, and review state live.

Documented surfaces

One API key for the CLI, the MCP server, and your scripts.

Each surface below has setup steps in the ReRune docs. Every request runs with the permissions of the account that owns the key.

  1. MCP server for coding agents

    Connect Claude Code, Codex, Cursor, or another MCP client to https://rerune.io/api/mcp over Streamable HTTP. Its tools read and edit drafts, import files, manage glossary terms, and publish with a tag.

  2. CLI in CI

    Install a pinned CLI release, supply RERUNE_API_KEY from the CI secret store, pull published translations, and fail the job when the pull changes tracked locale files.

  3. API keys for management

    An API key acts as your account and allows only what your permissions allow. Keep it in a server environment, an untracked .env file, or a CI secret store, and run custom integrations on a trusted server.

  4. OTA Publish IDs for apps

    SDKs read published translations with a read-only OTA Publish ID in the request path. It cannot change a project, and read-only does not make the published text confidential.

Workflow

From app copy to release-ready localization.

ReRune connects translation management to the delivery path developers already use: dashboard work, AI assistance, CLI/API sync, and OTA updates where a supported SDK is installed.

Authenticate once

Generate API keys in the dashboard and use them in local scripts, CI/CD jobs, release tasks, or integration services.

Automate sync

Run ReRune once to create project config, then use rerune --pull and rerune --push as part of the engineering workflow instead of waiting on manual file handoffs.

Validate before release

Keep placeholders, structured values, missing languages, and review status visible before translated copy reaches production.

Release with options

Ship translations as files, API-driven sync, or OTA updates depending on the platform and how the product is deployed.

Setup WizardAI Coding Agent

One command. A wizard sets the stage, your AI agent ships it.

Run the onboarding command from the root of your Git repository. The wizard inspects the app and confirms the plan with you, with no AI involved and nothing changed yet. Then it opens the coding agent you already use with a complete migration workflow.

Run inside your Git repository

curl -fsSL https://rerune.io/onboard.sh | sh

View current scriptView v1.2.11Changelog

The script runs locally. ReRune does not receive your source code or list of installed agents.

Coding agent integrations

11 integrations: 4 available now, 7 planned.

  • Claude CodeReady
  • CodexReady
  • OpenCodeReady
  • PiReady
  • GitHub Copilot CLIPlanned
  • GoosePlanned
  • Qwen CodePlanned
  • Cursor AgentPlanned
  • Kiro CLIPlanned
  • Cline CLIPlanned
  • Factory DroidPlanned

Coverage

App-first does not mean mobile-only.

Start where localization creates release friction, then keep web, mobile, and cross-platform products in one shared workspace as your surface area grows.

Developer delivery

Sync through the CLI. Publish through OTA SDKs.

Use the ReRune CLI locally or in CI/CD to manage project translations, then deliver approved runtime updates through the SDK built for your app.

Companion CLI

Install the ReRune CLI

Use the ReRune CLI to sync, validate, and manage translations right from your terminal. Run syncs in CI/CD or locally whenever you need to push a new language.

Homebrew (macOS/Linux):

brew install BasalBit/tap/rerune
  • Downloadable builds for macOS, Linux, and Windows
  • Uses the API keys you generate in the dashboard
  • Fits scripted CI/CD workflows through CLI and API access
rerune

Connect the project

Create the project config and connect the repository to its ReRune workspace.

rerune pull

Pull approved updates

Bring current dashboard translations into the app or its build workflow.

rerune push

Push local changes

Send local translation updates back to ReRune for the team to manage and publish.

CI check

Check translation drift in CI.

The CLI reads RERUNE_API_KEY from your CI secret store. This check fails when pull changes the tracked locale files. Replace path/to/translations with your configured folder.

Open rerune-ci-demo
rerune version
rerune pull
git diff --exit-code -- path/to/translations

Questions

Questions teams ask before choosing a localization platform.

Contact the ReRune team

Share an idea, report a problem, or ask for help with ReRune.

What can teams automate with ReRune API workflows?

With the CLI, teams pull published translations and push source changes in CI, and create projects, languages, and OTA Publish IDs from the terminal. With the MCP server at https://rerune.io/api/mcp, coding agents edit drafts, import files, and publish with a tag when the account has the publishing permission. Both use an API key.

Is the API separate from the dashboard?

No. API workflows use the same project data that teams manage in the dashboard, including keys, languages, glossaries, metadata, and translation values.

Which credential belongs where?

Automation such as the CLI, the MCP server, and server-side scripts uses an API key, kept in a server environment, an untracked .env file, or a CI secret store. Apps use a read-only OTA Publish ID in the SDK configuration. The two are not interchangeable, and an API key never belongs in frontend code.

API keys and OTA Publish IDs

Explore next

Keep exploring the localization workflow.

Go deeper into the developer, platform, and delivery workflows connected to this page.

A localization MCP server for AI coding agents.

Connect Claude Code, Codex, Cursor, VS Code, OpenCode, or Pi to ReRune's hosted MCP server. Agents edit translation drafts and publish only with permission.

Localization CLI for releases that cannot wait on spreadsheets.

Use the ReRune localization CLI to initialize project config, pull dashboard translations, and push local translation updates from scripts or CI/CD workflows.

Developer localization platform for product teams that ship fast.

Keep localization in your engineering workflow with ReRune: CLI sync for releases, API keys for automation, and SDKs for runtime text updates in your apps.

One workspace

Start with one product workflow and expand from there.

Create projects, manage keys, use AI assistance with context, sync through CLI/API, and publish approved runtime updates when your app uses a supported ReRune SDK.
Start localizingPricing