Common challenge
Copying strings between spreadsheets, repositories, translators, and release branches slows engineers down and makes every handoff harder to verify.
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.
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.
Development workflow
Where ReRune enters the software delivery path.
ReRune keeps the collaborative workspace outside the repository while giving developers explicit ways to move approved localization data through local commands, CI jobs, and supported app runtimes.
Connect a repository
Generate project configuration with rerune, then use the API credentials created in the dashboard to associate local translation resources with the correct ReRune project.
Pull and push deliberately
Use rerune --pull to bring current dashboard translations into the app workflow and rerune --push to send local translation changes back for team management.
Run the same flow in CI/CD
The CLI is designed for scripted use and does not require a specific CI provider. Teams decide which branch, validation, and release gates should run localization sync.
Keep runtime delivery separate
Supported SDKs use a publishable, read-only OTA ID for runtime fetches. API keys used for developer automation do not belong in client applications, and bundled localization remains the fallback.
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.
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 | shThe 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.
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
reruneConnect the project
Create the project config and connect the repository to its ReRune workspace.
rerune pullPull approved updates
Bring current dashboard translations into the app or its build workflow.
rerune pushPush 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.devReRune Android on GitHubReRune iOS on Swift Package Index@rerune/react on npm@rerune/react-native on npm@rerune/angular on npmngx-translate example appTransloco example app
Flutter rerune ^1.2.1
Android rerune-android-compose:1.1.1
rerune-android-views:1.1.1
iOS ReRune 1.1.1
React @rerune/[email protected]
React Native @rerune/[email protected]
Angular @rerune/[email protected]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.
Contact the ReRune team
Share an idea, report a problem, or ask for help with ReRune.
Explore next
Keep exploring the localization workflow.
Go deeper into the developer, platform, and delivery workflows connected to this page.
Localization CLI for releases that cannot wait on spreadsheets.
Use the ReRune localization CLI to initialize project config, pull dashboard translations, and push local translation updates from scripts or CI/CD workflows.
Read moreLocalization API for teams that automate product text.
Connect localization to product systems with ReRune API workflows for translation keys, languages, AI-assisted translation, sync, and release automation.
Read moreLokalise alternative for teams that want developer-first app localization.
Compare ReRune as a Lokalise alternative for software teams that want app-focused localization, CLI/API sync, AI assistance, and OTA updates where supported.
Read moreOne 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.