Common challenge
Teams consider Weblate because it is free, open source software. Running it in production means operating several services, and app teams still need a way to update text in apps that have already shipped.
ReRune gives teams comparing Weblate a hosted localization workspace with CLI sync, AI assistance, translation variants, an MCP server, and OTA SDKs for React, React Native, Angular, Flutter, Android, and iOS, without running a translation server of your own.





Teams consider Weblate because it is free, open source software. Running it in production means operating several services, and app teams still need a way to update text in apps that have already shipped.
Product and engineering teams shipping web, mobile, and Flutter apps who want translation management and runtime text delivery without operating infrastructure.
Weblate is built around Git repositories and translator communities, with web CDNs and an Android SDK in alpha for runtime delivery. ReRune provides OTA SDKs for React, React Native, Angular, Flutter, Android, and iOS, translation variants, publication rollback, and OTA staging previews.
Where ReRune goes further
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 October 2026.
Publish a typo fix, a legal change, or a new language, and every supported app picks it up on its next update check. No store review, no redeploy. ReRune ships OTA SDKs for React, React Native, Angular, Flutter, Android, and iOS, each with an on-device cache and fallback to bundled strings.
Weblate: web CDNs and an Android Kotlin SDK in alpha. No official SDK for iOS, Flutter, React, or React Native.
Turn on staging in a development or QA build to see saved drafts, unfinished translations, and new keys inside the running app. Production users keep the published text until you publish.
Weblate: no documented draft preview for app builds.
Every publication is kept. Preview an earlier snapshot and restore it to live apps, while the draft you are working on stays untouched.
Weblate: per-string and Git history, but no documented restore of an earlier publication to live apps.
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.
Weblate: its variants group related source strings, such as short and long forms, for translators. They are not messages for different audiences.
Set the preview language to the language you are working on and filter for keys not yet translated in it. Translators see exactly what is left, with no spreadsheets and no developer handoff.
Self-hosting vs ReRune
Weblate is GPL-licensed and free to self-host, but production use means operating several services and keeping them current. Hosted Weblate removes that work, and paid ReRune plans start lower than hosted Weblate plans.
Self-hosted Weblate needs Python, PostgreSQL, Valkey or Redis, Celery workers, and Git, with at least 3 GB of RAM. Each service has to be configured, monitored, and scaled.
Weblate publishes a new release about every month. Someone on your team applies it, runs database migrations, backs up data, patches the host, and handles outages. With ReRune, that work is ours.
Weblate sells self-hosted support from €53 per month, and extended support from €106 per month plus a €480 installation fee, excluding VAT.
Hosted Weblate starts at €47 per month excluding VAT for 10,000 hosted strings, which count each source string once for the source language and once for every target language. Paid ReRune plans start at €19.95 per month including VAT for 2,000 translation keys, with unlimited languages and seats.
Switching
Weblate keeps translations in your repository as standard files such as i18next JSON, Flutter ARB, XLIFF, Android XML, and Apple strings, so ReRune imports them as they are. Point the ReRune CLI at the same paths to push and pull, and add a ReRune SDK when you want OTA updates.
ReRune wraps i18next and react-i18next, so your JSON catalogs and t() calls stay the same. ReRune.setup replaces i18n.init.
ReRune wraps ngx-translate or Transloco, so the translate and transloco pipes stay in your templates. ReRune.provide replaces the provider setup.
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.
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
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.
Manage keys, languages, values, placeholders, dictionaries, metadata, and project context before translation work spreads across files and messages.
Use DeepL or OpenRouter-assisted translation flows with dictionaries and product context close to the text being reviewed.
Use CLI/API workflows to move approved translations into repositories, CI/CD jobs, scripted release tasks, or custom platform integrations.
Export platform formats or publish OTA updates for supported SDKs while keeping bundled app resources as the safe fallback.
Setup WizardAI Coding Agent
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 | shThe script runs locally. ReRune does not receive your source code or list of installed agents.
11 integrations: 4 available now, 7 planned.
Coverage
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
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
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/rerunereruneConnect the project
Create the project config and connect the repository to its ReRune workspace.
rerune pullPull approved updates
Bring current dashboard translations into the app or its build workflow.
rerune pushPush local changes
Send local translation updates back to ReRune for the team to manage and publish.
SDK directory
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.0Questions
Share an idea, report a problem, or ask for help with ReRune.
No. ReRune is a hosted platform. Your app keeps standard i18n libraries and file formats, and you can export your translations at any time, so your codebase is not tied to ReRune. If you need a free plan for a public open source project or must run the platform on your own servers, Weblate is the better fit.
Hosted Weblate prices plans by hosted strings, which count each source string once for the source language and once for every target language, starting at €47 per month excluding VAT for 10,000 hosted strings as listed on weblate.org in October 2026. ReRune prices plans by translation keys and monthly OTA quota, with unlimited languages and seats, and paid plans start at €19.95 per month including VAT.
Weblate offers a JavaScript localization CDN and a translation files CDN for web delivery, and an official Kotlin SDK for Android that is in alpha. ReRune provides OTA SDKs for React, React Native, Angular, Flutter, Android, and iOS, with local caching, fallback to bundled strings, OTA staging previews, and publication rollback.
Weblate keeps translations as standard files in your repository, so ReRune imports them as they are. Point the ReRune CLI at the same paths, then disconnect the Weblate component. Your app already uses standard i18n, so lookup code stays the same. Translation memory, glossaries, comments, and history move separately through exports such as TMX.
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.
Compare ReRune with self-hosted Tolgee and Tolgee Cloud. ReRune is hosted, includes unlimited languages and seats, starts at €19.95 per month, and ships OTA SDKs for web, mobile, and Flutter apps.
Read moreDeliver published app text through ReRune OTA SDKs, preview enabled drafts in staging clients, and keep production caches isolated with fallback and rollback.
Read moreDeveloper localization platform for app teams: translation management, CLI/API sync, AI assistance, and OTA SDK delivery where supported.
Read moreCreate 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.