Developer-first localization

Developer localization platform for product teams that ship fast.

ReRune keeps localization close to the engineering workflow: dashboard context for teams, API keys for automation, CLI sync for releases, and SDK paths for runtime text updates.

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

Copying strings between spreadsheets, repositories, translators, and release branches slows engineers down and makes every handoff harder to verify.

Best fit

Engineering teams that need repeatable sync alongside a clear workspace for review, terminology, context, and language progress.

How ReRune helps

ReRune treats localization as product infrastructure. The translation workspace and developer workflow are designed to stay connected from the first key to the release.

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.

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.

How does ReRune fit developer workflows?

Teams can use API keys, CLI commands, import/export, and supported SDKs so localization can move through scripts, CI/CD, repositories, and runtime update flows.

Do non-developers still get a usable workspace?

Yes. Product, localization, and operations users can manage projects, languages, dictionaries, translation status, AI assistance, billing context, and team collaboration from the dashboard.

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