Software localization platform

Software localization platform for apps that ship everywhere.

ReRune helps product, engineering, and localization teams manage app text from one workspace, then move approved translations through CLI/API sync, exports, and supported OTA SDK updates.

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

Translation files alone do not give product and engineering teams enough control. They need keys, languages, review context, automation, and release visibility in one place.

Best fit

Teams shipping web, mobile, and cross-platform software where localization touches product, engineering, and release work.

How ReRune helps

ReRune starts with app localization pain: copy changes, developer sync, AI assistance, and runtime delivery. That gives the broader platform a concrete workflow instead of a generic content hub.

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.

1

Collect product text

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

2

Translate with context

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

3

Sync through developers

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

4

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.

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.

Questions

Questions teams ask before choosing a localization platform.

What makes ReRune a software localization platform?

ReRune manages translation keys, languages, values, dictionaries, metadata, placeholders, import/export, CLI/API sync, AI-assisted translation, and OTA publish IDs for supported app SDKs.

Is ReRune only for mobile apps?

No. ReRune is app-first, not mobile-only. It is built for software teams that ship web, mobile, React, React Native, Flutter, Android, and iOS surfaces from a shared localization workflow.

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.

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.