AI translation management that stays accountable to product context.

ReRune brings DeepL and OpenRouter-assisted translation into the localization workspace so AI output can use project context, dictionaries, placeholders, and review before sync or publish.

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 speed only helps when terminology, brand language, placeholders, product context, and review control stay intact.

Best fit

Product teams that need AI assistance inside a governed translation workflow rather than scattered prompts disconnected from app strings.

How ReRune helps

ReRune keeps AI assistance close to keys, metadata, dictionaries, project context, and delivery status so generated translations can be checked before they reach users.

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.

Collect product text

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

Translate with context

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

Sync through developers

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

Deliver safely

Export platform formats or publish OTA updates for supported SDKs while keeping bundled app resources as the safe fallback.

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

The script runs locally. ReRune does not receive your source code or list of installed agents.

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

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

  3. 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
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, React, React Native, and Angular support runtime variant selection with Main and bundled fallback.

Flutter        rerune ^1.3.0
Android        rerune-android-compose:1.2.0
               rerune-android-views:1.2.0
iOS            ReRune 1.2.0
React          @rerune/react@1.6.0
React Native   @rerune/react-native@1.6.0
Angular        @rerune/angular@1.6.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.

Which AI providers does ReRune connect to?

ReRune supports DeepL and OpenRouter-powered translation workflows so teams can use machine translation or LLM-assisted output with project context.

Can teams review AI translations before release?

Yes. ReRune keeps AI-assisted output in the same workspace as translation values, placeholders, dictionaries, metadata, and release-oriented sync steps.

How does AI translation stay controlled?

ReRune keeps AI assistance close to project context, dictionaries, placeholders, structured values, and review steps so generated translations can be checked before sync or publish.

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.