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.

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

Web teams manage interface text, settings, onboarding, and release copy across languages that can easily drift from the rest of the product.

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 glossaries, 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 glossaries 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, 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 platform

ReRune for Angular

@rerune/angular 1.9.0 replaces your native root provider and accepts its unchanged options. Keep ngx-translate or Transloco pipes, loaders, and language switching.

Replace the native root provider with ReRune.setup(..., nativeOptions)
Keep native reactive pipes, interpolation, and language switching
Restore cached OTA text over bundled translations with built-in browser storage
Use the same provider for Angular SSR and TransferState hydration
Select Main or a named translation variant at setup or runtime
Preview enabled drafts in an isolated staging mode before publishing

Angularngx-translateTranslocoSSROTA

Quick Start

Translation engine

Install command

npm install @rerune/angular@1.9.0 @ngx-translate/core@18

Setup

import { ApplicationConfig } from '@angular/core'
import { TranslateLoader } from '@ngx-translate/core'
import { ReRune } from '@rerune/angular/ngx-translate'
import { BundledLoader } from './translations'

export const appConfig: ApplicationConfig = {
  providers: [
    ReRune.setup({
      otaPublishId: '<READ_ONLY_OTA_PUBLISH_ID>',
      supportedLocales: ['en', 'de'],
    }, {
      lang: 'en',
      fallbackLang: 'en',
      loader: { provide: TranslateLoader, useClass: BundledLoader },
    }),
  ],
}

Replace the native root provider; keep your existing loader and translation pipes. supportedLocales includes app-owned languages the native engine has not registered yet. The full guide covers loader setup, SSR, and removal.

Full setup guide SDK README

Install command

npm install @rerune/angular@1.9.0 @jsverse/transloco@8

Setup

import { ApplicationConfig } from '@angular/core'
import { ReRune } from '@rerune/angular/transloco'
import { BundledLoader } from './translations'

export const appConfig: ApplicationConfig = {
  providers: [
    ReRune.setup({
      otaPublishId: '<READ_ONLY_OTA_PUBLISH_ID>',
    }, {
      config: {
        availableLangs: ['en', 'de'],
        defaultLang: 'en',
        fallbackLang: 'en',
        reRenderOnLangChange: true,
      },
      loader: BundledLoader,
    }),
  ],
}

Replace the native root provider; keep availableLangs, your loader, translation pipes, and plugin order. The full guide covers loader setup, SSR, and removal.

Full setup guide SDK README

Explore Angular localization View on npm

React Web

@rerune/react 1.9.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.

Replace i18n.init(...) with ReRune.setup(..., nativeOptions), which returns the client synchronously
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.9.0

View on npm

Install command

npm install @rerune/react@1.9.0 i18next react-i18next

Setup

import { ReRune, ReRuneProvider } from '@rerune/react'

const client = ReRune.setup({
  otaPublishId: '<READ_ONLY_OTA_PUBLISH_ID>',
}, nativeOptions);

<ReRuneProvider client={client} defaultNS="translation">
  <App />
</ReRuneProvider>

Use your existing nativeOptions and resources. Call setup once at module scope; it returns the client synchronously. Replace I18nextProvider with ReRuneProvider, which loads cached and OTA text after its first render. Keep useTranslation(). For plugins, pass your existing i18n. The full guide covers SSR and the Next.js App Router.

Full setup guide SDK README

Explore React localization

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, glossaries, 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, glossary terms, 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

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

Web app localization connected to the same product workflow.

Common challenge

Best fit

How ReRune helps

Manage web copy across frameworks.

Manage browser copy centrally

Use build-time sync for any web stack

Choose a native web SDK

Render crawler-visible copy on the server

From app copy to release-ready localization.

Collect product text

Translate with context

Sync through developers

Deliver safely

One command. A wizard sets the stage, your AI agent ships it.

Coding agent integrations

App-first does not mean mobile-only.

Sync through the CLI. Publish through OTA SDKs.

Install the ReRune CLI

ReRune for Angular

React Web

Quick Start

Questions teams ask before choosing a localization platform.

Contact the ReRune team

Can ReRune manage web app localization?

Does web app localization support OTA updates?

How does AI translation stay controlled?

Can I preview draft translations in a running app before publishing?

React localization that stays connected to product delivery.

Angular localization with your existing translation engine.

Localization API for teams that automate product text.

Software localization platform for apps that ship everywhere.

Start with one product workflow and expand from there.

Web app localization connected to the same product workflow.

Common challenge

Best fit

How ReRune helps

Manage web copy across frameworks.

Manage browser copy centrally

Use build-time sync for any web stack

Choose a native web SDK

Render crawler-visible copy on the server

From app copy to release-ready localization.

Collect product text

Translate with context

Sync through developers

Deliver safely

One command. A wizard sets the stage, your AI agent ships it.

Coding agent integrations

App-first does not mean mobile-only.

Sync through the CLI. Publish through OTA SDKs.

Install the ReRune CLI

ReRune for Angular

React Web

Quick Start

Questions teams ask before choosing a localization platform.

Contact the ReRune team

Can ReRune manage web app localization?

Does web app localization support OTA updates?

How does AI translation stay controlled?

Can I preview draft translations in a running app before publishing?

Keep exploring the localization workflow.

React localization that stays connected to product delivery.

Angular localization with your existing translation engine.

Localization API for teams that automate product text.

Software localization platform for apps that ship everywhere.

Start with one product workflow and expand from there.