Own your product copy.

ReRune is a translation management system for software teams. Product, localization, and engineering teams can manage source copy and translations, use machine translation and AI assistance, create audience variants, and control when text is published to supported apps through OTA updates.

Teams manage source wording and translations together, create variants for brands or audiences selected by their app, and control when edits become published text. DeepL machine translation and OpenRouter AI are optional. Supported OTA SDKs deliver published text updates with cached or bundled fallback, within each platform's limits.

Yes. ReRune is structured around projects, languages, keys, dictionaries, metadata, CLI/API sync, and SDK delivery paths so teams can manage several product surfaces from one localization workspace.

Create a ReRune project, choose its languages, then import existing translation resources or connect the repository through agent-assisted onboarding, the CLI, or the API. Your app can keep its current localization model.

ReRune includes the localization workspace. Plans are based on translation keys and monthly OTA quota. On paid plans, you can add more of either as separate add-ons without switching packages. Compare monthly and annual plans below, or open the pricing page for a full breakdown.

ReRune is built for product, engineering, and localization teams that ship web or mobile products and want localization connected to their normal release workflow.

No. Your app keeps its native or framework localization model and bundled resources. ReRune manages translation content and adds CLI/API sync plus runtime delivery through supported SDKs.

No. ReRune also supports dashboard management, platform exports, import workflows, CLI sync, and API-driven workflows. OTA updates are an added delivery path for supported SDKs.

Teams can use ReRune API keys, the ReRune CLI, and platform exports to sync translation files through local scripts or CI/CD pipelines.

Supported ReRune SDKs can deliver approved text at runtime. If an update is unavailable, the app keeps its bundled localization resources as fallback. New code paths and unsupported resource changes still ship through the normal release process.

The public Flutter, Android, iOS, React, React Native, and Angular SDKs can expose dashboard-published languages at runtime after their locale payloads are fetched. Platform language listings, store metadata, and SDK-specific application configuration can still require a release.

New code paths and localization structures the installed app does not know about still require a release. Examples include new Android resource IDs, new Flutter keys or placeholder signatures, native system text, and app-store language metadata.

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.

Yes. Product, localization, and operations users can manage projects, languages, dictionaries, translation status, AI assistance, billing context, and team collaboration from the dashboard.

ReRune works with JSON-based i18next resources for React and React Native, root JSON catalogs for Angular ngx-translate and Transloco, generated Flutter localizations, Android string resources, and Apple localization assets. Each integration keeps its platform resource model while ReRune adds sync and supported OTA delivery.

No. DeepL and OpenRouter assistance is optional. Teams can create, edit, import, export, and sync translations through the core workspace without using AI generation.

ReRune keeps project context, dictionaries, metadata, placeholders, and structured values beside the translation work. Teams can inspect and edit values in the dashboard before they sync or publish them.

Yes. Store different messages under the same translation key. Your app chooses the variant from the user’s test group, brand, or plan, and ReRune delivers the matching text. Main content is used when a variant has no override.

Yes. Open a translation key’s publication history, preview an earlier snapshot, and restore it as the live version. The editor draft remains untouched. Apps receive the restored text on their next successful update check, so cached or offline clients may continue showing the previous text until they refresh.