Crowdin alternative for software teams that localize app releases.

ReRune gives teams evaluating Crowdin alternatives a focused app localization workflow with translation management, developer sync, AI assistance, and supported OTA delivery paths.

Start localizing See workflow

ReRune projects list showing real localization projects in a workspace

ReRune dashboard showing localization workspace activity and project status

ReRune OTA demo mobile app landing screen with live localization status

Common challenge

Software teams may need localization infrastructure centered on their own app release workflow rather than a very broad integration ecosystem.

Best fit

Teams that want a software localization workspace centered on app keys, language coverage, CLI/API sync, and supported SDK delivery.

How ReRune helps

ReRune focuses on the workflow from app copy to release: manage text, translate with context, sync through developers, and publish supported OTA updates.

Where ReRune goes further

Bring the whole team into audience-specific copy

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.

Crowdin offers conditional messages through ICU select syntax with an other fallback. 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: Crowdin Pro starts at $75/month billed annually, with unlimited translators, unlimited private projects, and 80,000 hosted words counted across target languages. Pro includes no manager seats, and Crowdin sells additional managers as a paid add-on. Team includes five managers and starts at $450/month, billed annually. These are Crowdin's USD list prices, excluding VAT, and its pricing page converts them to local currency.

Crowdin pricing Crowdin ICU select syntax ReRune pricing

Switching

Switch without rewriting your app.

Crowdin SDKs for Android, iOS, and Flutter overlay native strings, and ReRune SDKs follow the same pattern. Swap the SDK package, its setup call, and the distribution hash for one read-only OTA Publish ID. Web apps that call the Crowdin JavaScript client's own lookup methods move to standard i18next t() calls, and apps that already load Crowdin translations into i18next keep their t() calls.

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.setup 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, 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 script View v1.2.11 Changelog

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

Wizard→AI agent

$ curl -fsSL https://rerune.io/onboard.sh | sh

Detected Next.js app with react-i18next

Source locale: en · 3 catalogs found

Installed agents: Claude Code, Codex

? Connect ReRune cloud? › Yes

? Select agent › Claude Code

Handing off to Claude Code

Scanning components for static UI text…

Migrating 214 strings into en/translation.json

Running type check and first ReRune sync

Localization ready · 214 keys synced

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.dev ReRune Android on Maven Central ReRune iOS on Swift Package Index ReRune Kotlin Multiplatform on Maven Central @rerune/react on npm @rerune/react-native on npm @rerune/angular on npm ngx-translate example app Transloco 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 Crowdin replacement?

ReRune can cover many software localization needs, but it does not aim to replace every Crowdin workflow. It focuses on developer-first app localization and supported runtime delivery.

When should teams compare ReRune with Crowdin?

Compare them when your team needs translation management for app strings, developer automation, AI-assisted translation, and release-oriented localization workflows.

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

The code change is usually small, because Crowdin and ReRune mobile SDKs both overlay native strings. Swap the SDK package, its setup call, and the distribution hash for one read-only OTA Publish ID, import your files, and point the ReRune CLI at the project. Web code that calls the Crowdin JavaScript client's own lookup methods moves to i18next t() calls. Translation memory and glossaries move separately through exports. Comments, screenshots, and history are not part of the translation files. 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

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

Crowdin alternative for software teams that localize app releases.

Common challenge

Best fit

How ReRune helps