Skip to content
ReRune

Lokalise alternative for teams that want developer-first app localization.

ReRune is for teams evaluating localization platforms and looking for a focused workflow around app strings, developer sync, AI assistance, transparent usage, and supported OTA delivery.
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

Teams comparing localization platforms often want a different fit for app delivery, developer workflows, pricing, or product focus.

Best fit

Teams that want software localization centered on app delivery instead of a broad enterprise localization suite for every content type.

How ReRune helps

ReRune focuses on web, mobile, and cross-platform apps with CLI/API sync and supported OTA SDK paths. Compare it on that workflow rather than feature-for-feature parity with a broad enterprise suite.

Where ReRune goes further

Tailor app copy and grow your team freely

Managing translations is only half the job. ReRune also controls what reaches your users, when, and for whom. Competitor notes reflect each vendor's public documentation in November 2026.

One key, many audiences

Store different messages under the same key for A/B tests, white-label brands, or Free and Pro plans. Your app picks the variant and Main text is the fallback, so there are no duplicated keys and no forked copy.

Lokalise documents custom languages and experimental ICU plural and gender support in ARB. It does not document built-in audience variants with shared Main text as the fallback.

Give your team room to grow

Start on Free or choose Starter at €19.95 per month including VAT, as listed in November 2026. Every plan includes unlimited seats, languages, and projects. Your plan is based on translation keys and monthly OTA quota, with extra capacity available as add-ons on paid plans.

November 2026: Lokalise Explorer starts at $169/month, or $149/month billed annually, and includes five advanced seats, five projects, and ten languages per team (base and target combined). Translator and reviewer seats are unlimited.

Lokalise pricingLokalise plan detailsLokalise language settingsLokalise ARB format supportReRune pricing

Switching

Switch without rewriting your app.

Lokalise OTA SDKs for iOS and Android overlay native strings, and ReRune SDKs follow the same pattern. Lookups in your code stay as they are: swap the SDK package, its setup call, and the SDK token for one read-only OTA Publish ID. On Flutter, the Lokalise SDK uses a generated Lt class, so those calls move back to the standard AppLocalizations getters.

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

  2. Angular keeps its pipes

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

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

  4. 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, glossaries, metadata, and project context before translation work spreads across files and messages.

Translate with context

Use DeepL or OpenRouter-assisted translation flows with glossary terms 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 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 direct Lokalise clone?

No. ReRune overlaps in software localization needs, but it focuses on developer-first app localization, CLI/API sync, AI assistance, and supported OTA updates.

When should teams consider ReRune instead of Lokalise?

Consider ReRune when your main localization problem is app text, developer sync, release coordination, and runtime updates rather than a broad enterprise content localization program.

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

The code change is usually small, because the Lokalise iOS and Android SDKs and the ReRune SDKs overlay native strings. Swap the SDK package, its setup call, and the SDK token for one read-only OTA Publish ID, import your files, and point the ReRune CLI at the project. On Flutter, calls to the generated Lt class move back to AppLocalizations. Translation memory and comments move separately, through the exports and API your Lokalise plan provides. Bring glossary terms in as a CSV file, or add them by hand or through the API.

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.

Phrase alternative for app teams that want localization close to the code.

Compare ReRune with Phrase Strings on audience variants, pricing, team seats, and OTA SDKs. ReRune includes unlimited seats, languages, and projects.

Crowdin alternative for software teams that localize app releases.

Audience variants, CLI/API sync, OTA, and unlimited seats, languages, and projects. Compare ReRune with Crowdin on variants, manager seats, and pricing.

Tolgee alternative for teams that would rather ship apps than run a localization server.

Tolgee alternative with no server or license key to manage. ReRune is hosted, with unlimited seats and languages, OTA SDKs, and plans from €19.95 per month.

POEditor alternative for teams that update app text after release.

POEditor alternative with OTA SDKs, draft previews in test builds, audience variants, and publication restore. ReRune counts each key once in every language.

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.

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.

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