Localazy alternative for teams that want OTA updates on web, mobile, and Flutter apps.

ReRune gives teams comparing Localazy a localization workspace with CLI sync, AI assistance, translation variants, and OTA SDKs for React, React Native, Angular, Flutter, Android, and iOS.

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

Teams compare Localazy alternatives when runtime text updates matter on more platforms than native Android and iOS, or when they want SDKs that plug into the i18n they already use.

Best fit

App teams that ship web, cross-platform, and native apps and want to update approved copy on each of them without a new release.

How ReRune helps

Localazy offers OTA updates for Android and iOS and delivers files for other platforms through its CDN. ReRune provides OTA SDKs for React, React Native, Angular, Flutter, Android, and iOS that keep your existing lookups, plus translation variants and OTA staging previews.

Switching

Switch without rewriting your app.

Localazy keeps translation files in standard formats synced by its CLI, and its Android library overlays native resources, the same way ReRune works. On Android, swap the Localazy Gradle plugin for the ReRune SDK. On iOS, calls to localazyLocalized or Text(localazyKey:) move back to NSLocalizedString.

Web and React Native keep i18next

ReRune wraps i18next and react-i18next, so your JSON catalogs and t() calls stay the same. ReRune.setup replaces i18n.init.

Angular keeps its pipes

ReRune wraps ngx-translate or Transloco, so the translate and transloco pipes stay in your templates. ReRune.provide replaces the provider setup.

Flutter, Android, and iOS keep native lookups

Flutter keeps gen-l10n ARB files and AppLocalizations, Android keeps strings.xml and getString, and iOS keeps NSLocalizedString. You add the ReRune setup call and a small platform hook.

Your files and CLI workflow move with you

Import existing files in standard formats such as ARB, strings.xml, Localizable.strings, XLIFF, and i18next JSON, then push and pull with the ReRune CLI. Your app keeps standard i18n, so your codebase is not tied to ReRune either.

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.

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 script View v1.2.6 Changelog

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.

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

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.

rerune on pub.dev ReRune Android on Maven Central ReRune iOS on Swift Package Index @rerune/react on npm @rerune/react-native on npm @rerune/angular on npm ngx-translate example app Transloco example app

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.

Is ReRune a direct Localazy replacement?

ReRune covers app string management, CLI sync, AI assistance, and OTA delivery. It does not offer Localazy's shared translation memory pool (ShareTM) or its Continuous Localization Team of professional translators.

Which platforms get OTA updates with ReRune compared to Localazy?

Localazy offers OTA updates for Android and iOS. ReRune offers OTA SDKs for React, React Native, Angular, Flutter, Android, and iOS, with local caching and fallback to the strings bundled in your app.

How long does it take to switch from Localazy to ReRune?

Localazy and ReRune both keep translation files in standard formats synced by a CLI, so your catalogs move as they are. On Android, swap the Localazy Gradle plugin for the ReRune SDK. On iOS, calls to localazyLocalized move back to NSLocalizedString. For apps that already use standard i18n the code change often takes minutes. Translation memory, glossaries, comments, and history move separately through exports such as TMX.

Is ReRune a full enterprise suite replacement?

ReRune focuses on software and app localization workflows for product and engineering teams. It does not aim to cover every enterprise content, agency, or language-service workflow.

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