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 localizing See workflow

ReRune dashboard showing localization workspace activity and project status

ReRune projects list showing real localization projects in a workspace

ReRune project keys view for managing software translation keys

ReRune OTA demo mobile app landing screen with live localization status

ReRune OTA demo mobile app story screen showing runtime translation content

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.

Centralize the product vocabulary

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

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.

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.

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, dictionaries, metadata, and project context before translation work spreads across files and messages.

Translate with context

Use DeepL or OpenRouter-assisted translation flows with dictionaries 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.

Agent-assisted setup

Run one command. Your coding agent integrates ReRune.

Run the onboarding command from the root of your Git repository. The wizard detects the app and compatible coding agents already installed, then launches the agent you choose to move static UI text into localization, connect ReRune when cloud setup is selected, and validate the result.

Run inside your Git repository

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

View current script View v1.2.6 Changelog

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

Run the onboarding command
Start it from the repository root. It stays in the terminal and detects the app, existing localization, and supported coding agents already installed.
Confirm the detected setup
Review the source locale, Git branch, and whether to connect ReRune cloud and add supported OTA delivery. Nothing changes until you confirm.
The agent completes the integration
The selected agent migrates user-facing strings into the app's localization system, connects ReRune when cloud setup is selected, adds supported OTA setup when requested, and runs the relevant validation.

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.

Web apps and browser-based products React web apps with the public OTA SDK Angular apps with ngx-translate or Transloco React Native apps with the public OTA SDK Flutter apps with the public OTA SDK Native Android apps with the public OTA SDK Native iOS apps with the public OTA SDK

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, React, React Native, and Angular support runtime variant selection with Main and bundled fallback.

rerune on pub.dev ReRune Android on Maven Central ReRune iOS on Swift Package Index @rerune/react on npm @rerune/react-native on npm @rerune/angular on npm ngx-translate example app Transloco example app

Flutter        rerune ^1.3.0
Android        rerune-android-compose:1.2.0
               rerune-android-views:1.2.0
iOS            ReRune 1.2.0
React          @rerune/react@1.6.0
React Native   @rerune/react-native@1.6.0
Angular        @rerune/angular@1.6.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, dictionaries, 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, dictionaries, 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.

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 localizing Pricing