Free tier
Free
Free tierNo card required
- 300 Translation keys
- 1 GiB / month OTA quota
Start with this plan
Pricing
Straightforward pricing for software localization teams.
Choose a package for your translation keys and monthly OTA quota. Expand either with add-ons on a paid plan as your needs grow. The localization workspace is included.
No workspace traps
Every package keeps the core localization workspace open, without hidden project, language, seat, or sync gates.
Unlimited where cost is flat
Projects, languages, hosted words, collaborators, glossaries, metadata, and sync stay included.
Two plan limits
Plans are based on translation keys and monthly OTA quota. The rest of the workspace is included.
Plans: What you see is what you get. No strings attached.
Compare published plans or discuss a custom setup for your localization workload.
Paid tierTrial eligibleUp to 15% off
Starter
Starter plan meant for freelancers or small teams
19.95 EUR / month239.4 EUR / year
- 2,000 Translation keys
- 5 GiB / month OTA quota
- Expandable with add-ons
Start with this plan
Paid tierTrial eligibleUp to 25% off
Team
Team plan meant for small to medium teams
47.7 EUR / month572.4 EUR / year
- 5,000 Translation keys
- 15 GiB / month OTA quota
- Expandable with add-ons
Start with this plan
Paid tierTrial eligibleUp to 30% off
Plus
Plus plan meant for medium teams
110.5 EUR / month1,326 EUR / year
- 12,500 Translation keys
- 25 GiB / month OTA quota
- Expandable with add-ons
Start with this plan
Paid tierTrial eligibleUp to 35% off
Pro
Pro plan meant for big teams
208 EUR / month2,496 EUR / year
- 25,000 Translation keys
- 50 GiB / month OTA quota
- Expandable with add-ons
Start with this plan
Custom plan Let’s talk
Tell us what your team needs and we’ll discuss a plan that fits.
- Tailored Translation keys
- Tailored OTA quota
Monthly billing selectedVAT included
More keys or OTA quota? Add what you need.
Extend your paid plan with translation-key or OTA-quota add-ons. Increase either independently without switching packages.
Plan limits
Translation keys and monthly OTA quota.
Your package includes translation keys and monthly OTA quota. On paid plans, add more of either independently with add-ons, without changing packages.
Translation keys
Your plan includes capacity for a set number of translation keys that your workspace actively manages. Paid plans can add extra translation-key capacity as an add-on.
Keys are the clearest proxy for localization scope: they represent the actual product copy your team stores, reviews, syncs, and ships.
OTA quota
Your monthly OTA quota covers the text data delivered to your apps by ReRune’s servers. Usage is measured in GiB of successful SDK response-body data. Paid plans can add extra OTA quota as an add-on.
First and full syncs plus delivered updates consume quota. Headers, errors, unchanged 304 responses, and CDN hits that do not reach the origin do not.
Included resources
The workspace should not be the expensive part.
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.
| Resource | Package allowance | Why it stays simple |
|---|---|---|
| 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, localization, and design teammates without counting every reviewer as a pricing event. The ReRune plugin for Figma is coming soon to Figma Community and will work on every plan. |
| Glossaries and metadata | Unlimited | Glossary terms, notes, placeholders, and key metadata stay part of the workflow instead of becoming add-ons. |
| Screenshots and Gallery | Included | Upload, paste or drop screenshots of your app, mark the area of each key, and browse every screen in the project's Gallery. Translators see each text in its place on the screen, on every plan. |
| ReRune plugin for Figma | Coming soon | Coming soon to Figma Community. Link text layers to keys, push copy as drafts, preview every language on the canvas, and upload a screenshot of each frame you change. It will work on every plan, Free included. Nothing is published from Figma. |
| 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 | Work packages with assignees, due days and optional approval, separate edit and publish permissions, review context, and project visibility are core product capabilities, not surprise extras. |
Feature comparison
How ReRune compares with other localization platforms.
Compare what ReRune includes with common pricing and feature differences across localization platforms.
| Category | Other localization platforms | ReRune approach |
|---|---|---|
| Capacity and usage | Hosted words, source strings, projects, languages, managers, or seats can become plan gates. | Projects, locales, hosted words, collaborators, glossaries, import/export, CLI, and API sync are included. Your plan determines how many translation keys you can manage. |
| 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 monthly OTA quota, 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 glossaries, metadata, placeholders, structured values, project context, and app-oriented sync by default. The ReRune plugin for Figma, coming soon to Figma Community, will add design screenshots to keys, with the linked layer highlighted. |
| 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 measured as monthly GiB quota. |
| 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. |
Pricing questions
Clear answers for teams comparing localization plans.
Contact the ReRune team
Share an idea, report a problem, or ask for help with ReRune.
What determines my ReRune plan?
Choose your plan by the number of translation keys you manage and the monthly OTA quota you need, measured in GiB. The localization workspace is included.
How are translation keys counted across languages?
Each translation key counts once, no matter how many languages it is translated into. A project with 250 keys in 9 languages uses 250 translation keys, not 2,250. Adding languages does not increase your key count.
Are there limits on app installs or monthly active users?
No. ReRune does not limit app installs or monthly active users. Plans use only two usage metrics: translation keys and monthly OTA quota. OTA usage is visible in the dashboard, so you can monitor it and, on paid plans, add OTA quota without changing packages.
How is OTA quota measured?
OTA quota is the monthly volume, in GiB, of successful SDK response bodies served by ReRune's origin. Headers, errors, 304 responses, reads from the app's local cache, and CDN hits that do not reach the origin do not count. The first successful sync on an installation downloads the full published text. After that, published updates deliver only changes, and if nothing changed, no translation payload is downloaded.
How does OTA quota work for high-traffic consumer apps?
OTA usage depends mainly on how many installations sync for the first time and how much text you change when you publish. After the first full download, published updates deliver only changes, and checks that find nothing new download no translation payload, so frequent app opens add little OTA usage. You can start on any plan, including the smallest one, watch your OTA usage in the dashboard, and adjust as needed by adding or removing OTA add-ons on paid plans. If you would like to discuss a custom package, we are happy to hear from you.
Can I add translation keys or OTA quota without changing plans?
Yes. On paid plans, you can purchase extra translation-key capacity and OTA quota separately as add-ons to your current package. Manage them in your billing account. Free plans need to move to a paid plan before adding add-ons.
Which ReRune resources are unlimited?
Projects, languages, hosted words, collaborators, glossaries, metadata, import/export, CLI sync, and API sync are included as core workspace capabilities.
Why are plans based on translation keys?
Translation keys are the clearest measure of product copy scope because they represent the strings teams store, review, sync, and ship.
Is the Figma plugin included in every plan?
Yes, once it is released. The ReRune Figma plugin is coming soon to Figma Community and will work on every plan, Free included; designers join as collaborators, which are unlimited. Keys created from Figma count toward your plan's translation-key limit like any other key. Figma bills its own seats: the plugin will work on every Figma plan, including the free Starter plan, for anyone who can edit the file, which on paid Figma plans means a Full seat. Dev Mode features are planned for a later release and will need a paid Figma plan with a Dev or Full seat.
Take control of your product copy.
Start with one project. Bring your existing text, translate it, try an audience variant, and preview an update before publishing.
