Continuous delivery

Continuous localization for teams that ship every week.

ReRune helps teams turn localization into a repeatable product workflow: manage keys, review translations, automate sync, and ship approved text without rebuilding the process every release.

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

When releases move faster than translation handoffs, localization becomes a recurring blocker instead of part of the normal delivery cycle.

Best fit

Teams whose strings change often, whose releases run through CI/CD, and whose localization status must stay visible before delivery.

How ReRune helps

ReRune connects the workspace to developer sync and SDK delivery paths, so localization can become part of normal release operations instead of a separate manual project.

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.

What does continuous localization mean for ReRune?

It means translation work can move alongside product development through shared project context, CLI/API sync, import/export, status visibility, and supported OTA delivery paths.

Does ReRune require a specific CI/CD provider?

No. ReRune provides developer-facing sync paths that can be used from scripts or CI/CD jobs. Teams decide how those commands fit their existing release process.

Does ReRune only work for OTA updates?

No. ReRune also supports dashboard management, platform exports, import workflows, CLI sync, and API-driven workflows. OTA updates are an added delivery path for supported SDKs.

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