Software localization platform

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.

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.

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 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.

ReRune publishes OTA integrations for Flutter, Android, iOS, React, and React Native while each app keeps bundled localization as its fallback.

rerune on pub.dev ReRune Android on GitHub ReRune iOS on Swift Package Index @rerune/react on npm @rerune/react-native on npm

Flutter        rerune ^1.0.0
Android        rerune-android-compose:1.0.1
               rerune-android-views:1.0.1
iOS            ReRune 1.0.0
React          @rerune/react@1.0.0
React Native   @rerune/react-native@1.0.0

Questions

Questions teams ask before choosing a localization platform.

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