No workspace traps
Every package keeps the core localization workspace open, without hidden project, language, seat, or sync gates.
ReRune includes the localization workspace and meters only two things: translation keys and OTA credits.
Every package keeps the core localization workspace open, without hidden project, language, seat, or sync gates.
Projects, languages, hosted words, collaborators, dictionaries, metadata, and sync stay included.
ReRune meters translation keys and OTA credits. Everything else is priced as part of the package.
Choose the plan that matches your localization workflow.
No published plans available
Please try again in a moment.
The plan should not punish your team for being organized. ReRune pricing centers on the two dimensions that actually define paid usage: translation keys and OTA credits.
Metered by the number of translation keys your workspace actively manages.
Keys are the clearest proxy for localization scope: they represent the actual product copy your team stores, reviews, syncs, and ships.
Metered when SDK-backed apps consume runtime localization delivery.
OTA credits map to runtime delivery work, so teams that publish more app text updates pay for the delivery they actually use.
Translation management tools often turn normal workspace shape into pricing pressure: more projects, more languages, more seats, more hosted words. ReRune treats those as the baseline you need to work.
Projects
Unlimited
Create product, platform, staging, or customer-specific projects without reshaping your account around plan limits.
Languages and locales
Unlimited
Add the markets you need. ReRune should not make small language experiments expensive before they prove value.
Hosted words
Unlimited
Word count is workspace context, not a separate billable dimension. Your content volume is represented by the keys you actively manage.
Collaborators and seats
Unlimited
Invite product, engineering, and localization teammates without counting every reviewer as a pricing event.
Dictionaries and metadata
Unlimited
Terminology, notes, placeholders, and key metadata stay part of the workflow instead of becoming add-ons.
Import, export, CLI, and API sync
Included
Developer sync belongs in the package because it is how software teams keep localization connected to delivery.
Team localization workflow
Included
Collaboration, review context, and project visibility are treated as core product capabilities, not surprise extras.
ReRune is intentionally narrower than enterprise translation suites: software localization, developer sync, governed AI assistance, and runtime app text updates.
Capacity and usage
Hosted words, source strings, projects, languages, managers, or seats can become plan gates.
Projects, locales, hosted words, collaborators, dictionaries, import/export, CLI, and API sync are included. Translation keys are the metered scope dimension.
AI features
AI / MT words, advanced AI routing, scoring, or custom profiles are often separated into allowances or higher tiers.
AI-assisted translation is part of the workflow. The pricing model is still anchored on keys and OTA credits, not a separate AI feature wall.
Translation management
Glossaries, translation memory, history, QA checks, screenshots, and in-context tooling are common comparison-table rows.
ReRune focuses on dictionaries, metadata, placeholders, structured values, project context, and app-oriented sync by default.
Delivery and automation
Integrations, workflows, automations, and OTA calls are commonly split across plans or add-ons.
CLI/API sync and platform import/export are included. OTA delivery is represented by OTA credits.
Security and procurement
Access controls, auditability, privacy pages, support levels, and enterprise terms appear as decision rows.
ReRune keeps privacy, legal, subprocessor, team access, and billing-account context visible from the start.
ReRune meters only two usage dimensions: translation keys and OTA credits. The rest of the localization workspace is included in the package.
Projects, languages, hosted words, collaborators, dictionaries, metadata, import/export, CLI sync, and API sync are included as core workspace capabilities.
Translation keys are the clearest measure of product copy scope because they represent the strings teams store, review, sync, and ship.
OTA credits represent runtime localization delivery for SDK-backed apps, so teams pay for the app text delivery they actually use.