Common challenge
Web teams manage interface text, settings, onboarding, and release copy across languages that can easily drift from the rest of the product.
Web app localization connected to the same product workflow.
ReRune keeps web app text alongside mobile and cross-platform surfaces, with CLI/API workflows and OTA delivery through native React and Angular SDKs.
Best fit
Web product teams that need translation management, context, AI assistance, and developer sync without isolating browser copy from the rest of the product.
How ReRune helps
ReRune keeps web app localization aligned with app localization, so teams can share dictionaries, metadata, workflow, and sync patterns across surfaces.
Browser scope
Manage web copy across frameworks.
ReRune manages browser-product translation data independently of the frontend framework. Public React and Angular SDKs add runtime OTA delivery through each app’s native translation engine.
Manage browser copy centrally
Keep navigation, settings, onboarding, validation, and other interface text in the same project model as mobile surfaces, with shared dictionaries and product context.
Use build-time sync for any web stack
Imports, exports, CLI sync, and API-backed workflows can feed the application's normal localization build. These paths do not depend on React or browser runtime fetching.
Choose a native web SDK
@rerune/react connects to i18next and react-i18next. @rerune/angular provides native ngx-translate and Transloco adapters. Both restore cached OTA text over bundled resources and keep the app’s existing rendering APIs.
Render crawler-visible copy on the server
React uses ReRune.preload(...) and passes hydration state to browser setup. Angular uses its root provider and TransferState with normal SSR configuration. Translate titles, metadata, JSON-LD, and page copy after initialization in the server rendering path.
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.
Agent-assisted setup
Run one command. Your coding agent integrates ReRune.
Run the onboarding command from the root of your Git repository. The wizard detects the app and compatible coding agents already installed, then launches the agent you choose to move static UI text into localization, connect ReRune when cloud setup is selected, and validate the result.
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.
Run the onboarding command
Start it from the repository root. It stays in the terminal and detects the app, existing localization, and supported coding agents already installed.
Confirm the detected setup
Review the source locale, Git branch, and whether to connect ReRune cloud and add supported OTA delivery. Nothing changes until you confirm.
The agent completes the integration
The selected agent migrates user-facing strings into the app's localization system, connects ReRune when cloud setup is selected, adds supported OTA setup when requested, and runs the relevant validation.
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
reruneConnect 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.
React Web
@rerune/react 1.6.0 creates i18next from your native options and replaces the root provider. Keep translation calls and resources, with browser caching and a separate SSR preload flow.
Explore React localization- Replace i18n.init(...) with awaited ReRune.setup(..., nativeOptions)
- Replace I18nextProvider with ReRuneProvider; keep native options and translation hooks
- Preload OTA translations with ReRune.preload(...) for server-rendered and SEO-visible content
- Use bundled resources whenever OTA translations are unavailable
- Select Main or a named translation variant at setup or runtime
- Preview enabled drafts in an isolated staging mode before publishing
ReactWebi18nextOTA
Quick Start
@rerune/react@1.6.0
Install command
npm install @rerune/react@1.6.0 i18next react-i18nextSetup
import { ReRune, ReRuneProvider } from '@rerune/react'
const client = await ReRune.setup({
otaPublishId: '<READ_ONLY_OTA_PUBLISH_ID>',
}, nativeOptions);
<ReRuneProvider client={client} defaultNS="translation">
<App />
</ReRuneProvider>Use your existing nativeOptions and resources. Keep imports at module scope; await setup once in browser startup, then replace I18nextProvider and mount your app. Keep useTranslation(). For plugins, pass your existing i18n. The full guide covers SSR.
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.
Can ReRune manage web app localization?
Yes. ReRune can manage web app translation keys, languages, values, dictionaries, metadata, import/export, and CLI/API sync from the same workspace.
Does web app localization support OTA updates?
Yes. React apps can use @rerune/react with i18next and react-i18next. Angular apps can use @rerune/angular with ngx-translate or Transloco. Both keep the native rendering path and bundled fallback while applying published OTA translations.
How does AI translation stay controlled?
ReRune keeps AI assistance close to project context, dictionaries, placeholders, structured values, and review steps so generated translations can be checked before sync or publish.
Can I preview draft translations in a running app before publishing?
Yes. Enable OTA staging for the project and opt a development or QA client into staging mode. The client receives saved, enabled draft snapshots on its next sync from a cache kept separate from published content. Production clients stay on the published path by default.
Explore next
Keep exploring the localization workflow.
Go deeper into the developer, platform, and delivery workflows connected to this page.
React localization that stays connected to product delivery.
Adopt React OTA localization with SDK 1.6.0. Replace startup wiring, preserve i18next translation calls, and restore native setup when removing ReRune.
Read moreAngular localization with your existing translation engine.
Adopt @rerune/angular 1.6.0 with ngx-translate or Transloco. Replace the root provider, keep native options and pipes, and support OTA updates and Angular SSR.
Read moreLocalization API for teams that automate product text.
Connect localization to product systems with ReRune API workflows for translation keys, languages, AI-assisted translation, sync, and release automation.
Read moreSoftware localization platform for apps that ship everywhere.
ReRune is a software localization platform for teams shipping web, mobile, and cross-platform apps with AI assistance, CLI/API sync, and OTA updates where supported.
Read moreOne 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.