Skip to content
ReRune

Continuous localization for teams that ship every week.

ReRune helps teams turn localization into a repeatable product workflow: manage keys, review translations, automate sync, and ship approved text without rebuilding the process every release.
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

When releases move faster than translation handoffs, localization becomes a recurring blocker instead of part of the normal delivery cycle.

Best fit

Teams whose strings change often, whose releases run through CI/CD, and whose localization status must stay visible before delivery.

How ReRune helps

ReRune connects the workspace to developer sync and SDK delivery paths, so localization can become part of normal release operations instead of a separate manual project.

Release sequence

Continuous localization is a sequence of controlled handoffs.

The goal is not constant publishing. It is a repeatable path in which new product text, translation review, repository sync, and delivery happen alongside the existing release process.

  1. Author with implementation context

    Create or update keys with metadata and placeholders while the product change is still understandable to the people building it.

  2. Review before automation

    Use language status, glossaries, project context, and human review to decide what is ready. AI assistance can accelerate translation, but it does not remove this release gate.

  3. Sync at a defined build stage

    Run CLI or API-backed sync from the branch or CI stage your team owns. ReRune does not prescribe a CI vendor or replace repository and test controls.

  4. Deliver through files or a supported SDK

    Bundle translations in the next build when code or resource structure changes. Use supported OTA delivery for approved runtime text that fits the installed SDK's documented scope.

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.

SDK directory

Use the current public SDK for each product surface.

Public ReRune SDKs for Flutter, Android, iOS, Kotlin Multiplatform, React, React Native, and Angular support runtime variant selection with Main and bundled fallback.

rerune on pub.devReRune Android on Maven CentralReRune iOS on Swift Package IndexReRune Kotlin Multiplatform on Maven Central@rerune/react on npm@rerune/react-native on npm@rerune/angular on npmngx-translate example appTransloco example app
Flutter        rerune ^1.9.1
Android        rerune-android-compose:1.8.0
               rerune-android-views:1.8.0
iOS            ReRune 1.7.0
KMP            rerune-kmp-compose:1.0.0
React          @rerune/react@1.9.0
React Native   @rerune/react-native@1.9.0
Angular        @rerune/angular@1.9.0

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 does continuous localization mean for ReRune?

It means translation work can move alongside product development through shared project context, CLI/API sync, import/export, status visibility, and supported OTA delivery paths.

Does ReRune require a specific CI/CD provider?

No. ReRune provides developer-facing sync paths that can be used from scripts or CI/CD jobs. Teams decide how those commands fit their existing release process.

Does ReRune only work for OTA updates?

No. ReRune also supports dashboard management, platform exports, import workflows, CLI sync, and API-driven workflows. OTA updates are an added delivery path for supported SDKs.

Explore next

Keep exploring the localization workflow.

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

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.

Localization API for teams that automate product text.

Automate ReRune with an API key: the CLI in CI, the hosted MCP server for coding agents, and server-side scripts. Apps use a read-only OTA Publish ID.

A translation workflow with assignments, approval and a separate publish step.

Assign translation keys to teammates with work packages, set due days, add an optional approver, and keep publishing a separate permission in ReRune.

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