Skip to content
ReRune

App localization platform that starts with releases, not files.

ReRune gives teams one place to manage app strings, coordinate translation work, sync developer formats, and deliver approved updates across supported web, mobile, and cross-platform workflows.
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

Shipping product text safely across multiple frameworks, languages, and release cycles requires one workflow that keeps every surface aligned.

Best fit

Product teams with interface copy across several surfaces that need localization connected directly to the release path.

How ReRune helps

ReRune starts where localization hurts most: app strings, release sync, and runtime updates. From there, it supports broader product localization from the same workspace.

Multi-surface workflow

Share localization work without forcing every app into one runtime model.

A shared ReRune project can coordinate product language across surfaces, but the delivery layer stays specific to the framework and release channel used by each application.

  1. Centralize the product vocabulary

    Keys, language progress, glossaries, metadata, and review context can stay aligned even when web, Android, iOS, Flutter, and React Native applications use different resource formats.

  2. Treat browser delivery separately

    Web projects can use imports, exports, CLI/API sync, and the public React SDK where i18next-based OTA delivery is appropriate. A generic web page should not imply that every JavaScript framework uses the React package.

  3. Keep native conventions

    Android continues through resource IDs and native string lookups, while iOS continues through Foundation lookups. Flutter keeps generated AppLocalizations, and React Native keeps i18next rendering.

  4. Choose delivery per change

    Existing approved text and supported runtime languages may move through OTA. New code paths, compiled resource identifiers, and platform store metadata still belong to normal application releases.

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.

Collect product text

Manage keys, languages, values, placeholders, glossaries, metadata, and project context before translation work spreads across files and messages.

Translate with context

Use DeepL or OpenRouter-assisted translation flows with glossary terms and product context close to the text being reviewed.

Sync through developers

Use CLI/API workflows to move approved translations into repositories, CI/CD jobs, scripted release tasks, or custom platform integrations.

Deliver safely

Export platform formats or publish OTA updates for supported SDKs while keeping bundled app resources as the safe fallback.

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 is app localization in ReRune?

It means managing user-facing software text as product data: keys, languages, values, metadata, placeholders, glossaries, AI assistance, developer sync, and supported runtime delivery.

Can ReRune support both web and mobile app localization?

Yes. ReRune centralizes the localization workspace while delivery can vary by surface: exports, CLI/API sync, and OTA SDK updates where supported.

Can one workspace cover web, mobile, and cross-platform apps?

Yes. ReRune is structured around projects, languages, keys, glossaries, metadata, CLI/API sync, and SDK delivery paths so teams can manage several product surfaces from one localization workspace.

Explore next

Keep exploring the localization workflow.

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

Web app localization connected to the same product workflow.

Manage web app localization with translation keys, AI assistance, CLI/API sync, and OTA delivery through ReRune SDKs for React and Angular.

React localization that stays connected to product delivery.

Adopt React OTA localization with SDK 1.9.0. Replace startup wiring, preserve i18next translation calls, and restore native setup when removing ReRune.

Flutter localization with OTA updates on top of your existing flow.

Use ReRune Flutter SDK 1.9.1 for OTA localization and runtime variants while keeping generated delegates, bundled resources, CLI sync, and AI assistance.

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