Skip to content
ReRune

A translation management system for copy you control.

Give product, localization, and engineering one place to own app text. Manage source copy and translations, use machine translation and AI, choose audience variants, and decide what goes live through publishing and supported OTA SDKs.
Start localizingSee workflow
ReRune projects list showing real localization projects in a workspace
ReRune dashboard showing localization workspace activity and project statusReRune dashboard showing localization workspace activity and project statusReRune dashboard showing localization workspace activity and project status
ReRune OTA demo mobile app landing screen with live localization status

Common challenge

A small wording change can cross documents, translation files, and a release queue. Teams need a clear owner for the text, its translations, and the version customers see.

Best fit

Product, localization, and engineering teams managing software UI copy across languages, brands, or customer groups, with file, CLI/API, or supported SDK delivery.

How ReRune helps

Keep source copy, translations, and variants together. Separate editing from publishing, preview drafts through OTA staging, and publish supported text updates independently of an app release.

Own the copy lifecycle

From the first word to the version customers see.

Copy ownership means your team can change the wording, choose its audience, and control its release. ReRune connects those decisions to the translation work behind them.

  1. Keep source copy and translations together

    Manage each key's main-language text, translations, metadata, and typed placeholders in one project. Keep terms in a glossary and see which language values still need work.

  2. Translate with DeepL and AI

    Connect DeepL for machine translation or OpenRouter for AI-assisted translation. OpenRouter receives your glossary terms as instructions; DeepL receives them as a hint it may not follow. Review meaning, terms, placeholders, and plurals before publishing.

  3. Choose wording for each audience

    Keep shared text in Main and override only the wording that changes for a brand, customer, plan, or experiment. Your app selects the variant; ReRune uses Main when no override exists.

  4. Decide when the copy goes live

    Save drafts, preview through OTA staging, and publish selected keys with a release tag. Supported SDKs deliver compatible text updates without a new app release. Use publication history to roll back a key when needed.

Before you choose a TMS

Test the workflow your team will use.

Use a real part of your app to check compatibility, responsibilities, and cost. These are the decisions that matter when adopting or replacing a translation management system.

Will our existing translations work?

Check your platform's import and export formats with a representative file. Verify key names, locale codes, placeholders, and plurals. Imports update Main; exports can select Main or one variant with Main fallback.

Check import and export

Who can edit and who can publish?

Assign editing and publishing permissions separately. Agree who owns source copy, who checks translated values, and who releases them to customers.

Review team permissions

How will text reach our app?

Choose files or CLI/API sync for your build workflow, or integrate a supported OTA SDK for runtime updates. Test staging, published content, rollback, and offline fallback on your actual platform.

Read the publishing guide

What will it cost as we grow?

Review translation-key capacity and OTA delivery usage on the pricing page. Paid plans can expand either with add-ons. DeepL and OpenRouter use your connected provider account; check that provider's pricing and language coverage alongside your ReRune plan.

See plans and usage

Moving from another TMS

Prove the move with one real file.

If you are leaving Phrase or another provider, start with the files you can export today. A small end-to-end check gives your team a concrete basis for the switch.

  1. Import a representative sample

    Keep the original export. Choose a supported format and include your source language, target languages, placeholders, and plural messages.

  2. Check the round trip

    Review the imported values, export them again, and run your app's localization generator or build. Check the UI with realistic content.

  3. Try the release path

    Use your file or CLI workflow, or connect the SDK and test staging, publication, and fallback. Set editing and publishing permissions before switching the wider team.

Plan separately for translation memories, vendor assignments, approval history, and other provider-specific data. A translation-file import does not establish that those records transfer.

Talk through your TMS requirements.

Tell us your current platform, app frameworks, file formats, and required workflow. We can help you assess the fit before you move.

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

View current scriptView v1.2.11Changelog

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

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.

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

Questions

Questions teams ask before choosing a localization platform.

Contact the ReRune team

Share an idea, report a problem, or ask for help with ReRune.

Is ReRune a TMS?

Yes. ReRune is a translation management system for software teams. It keeps source text, translations, glossaries, placeholders, language progress, and team permissions in one workspace, with import/export, CLI/API sync, and publishing for supported OTA SDKs.

How does ReRune help teams own their product copy?

Teams manage source wording and translations together, create variants for brands or audiences selected by their app, and control when edits become published text. DeepL machine translation and OpenRouter AI are optional. Supported OTA SDKs deliver published text updates with cached or bundled fallback, within each platform's limits.

Can I move from Phrase or another TMS?

If you can export your app's translation files, start by checking them against ReRune's supported import formats. Validate a representative file, languages, placeholders, and plurals, then export and build your app before switching delivery. File import is not an automatic transfer of translation memory, approval workflows, or publication history; assess those requirements separately.

Can different customers see different wording in the same language?

Yes. Named variants can override selected keys for a brand, customer, plan, or experiment. Your app selects the active variant; ReRune supplies its text and falls back to Main where no override exists. Your app remains responsible for audience assignment and experiment measurement.

Does editing a translation change the live app immediately?

No. Draft edits are separate from published content. Teams can preview drafts using OTA staging, then publish selected keys with a release tag. Publication history supports rollback to an earlier key version. Runtime updates arrive according to the SDK and app refresh behavior; new code and unsupported localization structures still require an app release.

Explore next

Keep exploring the localization workflow.

Go deeper into the developer, platform, and delivery workflows connected to this page.

Software localization platform for apps that ship everywhere.

Localize web, mobile, and Kotlin Multiplatform apps in one ReRune workspace, then ship approved text through CLI/API sync, exports, and supported OTA SDKs.

AI translation management that stays accountable to product context.

Use ReRune for AI translation management with project context, glossaries, DeepL and OpenRouter assistance, review controls, and developer sync.

Developer localization platform for product teams that ship fast.

Keep localization in your engineering workflow with ReRune: CLI sync for releases, API keys for automation, and SDKs for runtime text updates in your apps.

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.

A translation workflow with assignments, approval and a separate publish step.

Assign translation keys to teammates with work packages, set due days, add an optional approver, and keep publishing a separate permission in ReRune.

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