Assign keys to one teammate
Select keys in the Keys tab, name the package and choose a teammate with the Edit keys permission. You can add keys later from a key's menu, and adding keys to a done package reopens it.
A translation workflow with assignments, approval and a separate publish step.
Group keys into a work package, assign it to one teammate with an optional due day, and add an approver when the text needs a second look. Publishing stays a separate permission, so the people who translate, approve and release can all be different.
Common challenge
When translation work is handed out in chat threads and spreadsheets, nobody can see who owns which strings, what is late, or whether anyone checked the text before it went out.
Best fit
Product, localization and engineering teams where different people write, translate, review and release app text.
How ReRune helps
Work packages live next to the keys in ReRune: the assignee filters the key list by package, the approver reviews from the same project, and publishing stays with the people who have the Publishing permission.
Team workflow
Every handoff has an owner
Each package names who does the work, who approves it and when it is due. Its creator, assignee and approver see it in the project's Work Packages tab.
Due days
Give a package an optional due day. The Work Packages tab shows when each package is due and marks it as overdue once the day has passed.
Optional approval, with reasons
Pick an approver other than the assignee, also someone with read-only access. They approve the package or reject it with a reason, and a rejected package goes back to the assignee. Without an approver, a package is approved when it is marked as done.
Notifications at every handoff
Assignees, approvers and creators get an email and a notification in the dashboard when a package is assigned, done, approved or rejected. Nobody is told about their own action.
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.
Assign
Someone with the Project settings permission selects keys, names the package and assigns it to a teammate with the Edit keys permission, with a due day if it has one.
Translate
The assignee filters the key list by the package, translates its keys and marks the package as done.
Approve
The approver, who may have read-only access, approves the package or rejects it with a reason, which sends it back to the assignee. Without an approver, done means approved.
Publish
A teammate with the Publishing permission publishes the changes. Translating and releasing are separate permissions, so they can stay with different people.
Setup WizardAI Coding Agent
One command. A wizard sets the stage, your AI agent ships it.
Run the onboarding command from the root of your Git repository. The wizard inspects the app and confirms the plan with you, with no AI involved and nothing changed yet. Then it opens the coding agent you already use with a complete migration workflow.
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.
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
- Compose Multiplatform 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
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, Kotlin Multiplatform, React, React Native, and Angular support runtime variant selection with Main and bundled fallback.
rerune on pub.devReRune Android on Maven CentralReRune iOS on Swift Package IndexReRune Kotlin Multiplatform on Maven Central@rerune/react on npm@rerune/react-native on npm@rerune/angular on npmngx-translate example appTransloco example app
Flutter rerune ^1.9.1
Android rerune-android-compose:1.8.0
rerune-android-views:1.8.0
iOS ReRune 1.7.0
KMP rerune-kmp-compose:1.0.0
React @rerune/react@1.9.0
React Native @rerune/react-native@1.9.0
Angular @rerune/angular@1.9.0Questions
Questions teams ask before choosing a localization platform.
Contact the ReRune team
Share an idea, report a problem, or ask for help with ReRune.
Does approval block publishing?
No. Approval records that someone checked the package, but it does not lock publishing. Teammates with the Publishing permission decide when to publish, so agree that they wait for approved packages. While someone filters by a done package, its keys are read-only in the dashboard as a reminder.
Who can create, work on and approve a work package?
Members with the Project settings permission create packages and assign them to a teammate with the Edit keys permission. The approver can be anyone in the team except the assignee, also someone with read-only access. Only the creator, the assignee and the approver see the package.
What happens when an approver rejects a package?
The package opens again for the assignee, with the reason shown. When the assignee marks it as done again, it goes back to the approver. Reopening a package, adding keys to it or assigning it to someone else clears an earlier approval.
Is the due day enforced?
The due day is shown on the package, and the Work Packages tab marks the package as overdue once the day has passed. It is a target for the team, not a lock: the assignee can still finish the work and mark the package as done afterwards.
Explore next
Keep exploring the localization workflow.
Go deeper into the developer, platform, and delivery workflows connected to this page.
A translation management system for copy you control.
A translation management system for app copy you control. Keep source text, translations, and variants with team permissions, and publish as a separate step.
Continuous localization for teams that ship every week.
Use ReRune for continuous localization with CLI/API sync, AI-assisted translation, review context, and release-ready updates for web and app teams.
Localization screenshots that show where every key appears.
Upload screenshots of your app to ReRune, mark where each translation key appears, and give translators and reviewers the screen behind every string.
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.
