Context
- Localization infrastructure for product, engineering, and language teams
- Combines project dictionaries, AI-assisted translation, CLI/API workflows, coverage checks, and OTA text delivery
- Built for teams that need product copy to move at software speed without losing review
Localization slows down when the source of truth fractures. Keys live in the repository, terminology in people's heads, progress in spreadsheets, and corrections wait for the next software release.
ReRune joins those parts. Keys, languages, project dictionaries, product context, translation providers, repository sync, coverage, and runtime delivery stay in one system.
What the product delivers
Shared workspaces with projects, languages, ownership, and localization status
Translation key management across languages, namespaces, and product areas
AI-assisted translation with project context, dictionaries, and a choice of supported providers
CLI, API, and CI/CD workflows that keep translations connected to the repository
Published versions, release IDs, and an SDK for updating supported runtime text without a new app binary
Coverage views for missing keys, incomplete languages, and release readiness
Proof in ROE Check-it
ROE previously managed localization in large Excel spreadsheets passed between colleagues. That made ownership, progress, and consistency hard to see. During the pilot, ReRune gave technical and nontechnical contributors one shared workspace, with BasalBit handling setup and onboarding.
The result was a clearer process with less manual coordination. ROE also reports time saved and translations that became more consistent and reliable.
- One source of truth instead of spreadsheets passed between colleagues
- Nontechnical colleagues can contribute without editing source files
- Project dictionaries and context make wording more consistent
- Key and language coverage make readiness visible before release
Delivery model
A key can move from the repository into a shared project, pick up terminology and product context, pass review, and return through CLI or API workflows. For supported apps, an approved version can then reach the runtime through OTA delivery.
We automate the movement and the repetitive suggestions. Ownership, review, and the decision to publish remain visible to the team.