No workspace traps
Every package keeps the core localization workspace open, without hidden project, language, seat, or sync gates.
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.
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.
Plans are based on translation keys and monthly OTA quota. The rest of the workspace is included.
Compare published plans or discuss a custom setup for your localization workload.
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.
Free
Free tier
No card required
Translation keys
Translation keys
300
OTA quota
OTA quota
1 GiB / month
Starter
19.95 EUR / month
239.4 EUR / year
Monthly billing selectedVAT included
Starter plan meant for freelancers or small teams
Translation keys
Expandable with add-ons
2,000
OTA quota
Expandable with add-ons
5 GiB / month
Team
47.7 EUR / month
572.4 EUR / year
Monthly billing selectedVAT included
Team plan meant for small to medium teams
Translation keys
Expandable with add-ons
5,000
OTA quota
Expandable with add-ons
15 GiB / month
Plus
110.5 EUR / month
1,326 EUR / year
Monthly billing selectedVAT included
Plus plan meant for medium teams
Translation keys
Expandable with add-ons
12,500
OTA quota
Expandable with add-ons
25 GiB / month
Pro
208 EUR / month
2,496 EUR / year
Monthly billing selectedVAT included
Pro plan meant for big teams
Translation keys
Expandable with add-ons
25,000
OTA quota
Expandable with add-ons
50 GiB / month
Custom plan
Let’s talk
Tell us what your team needs and we’ll discuss a plan that fits.
Translation keys
Translation keys
Tailored
OTA quota
OTA quota
Tailored
Your package includes translation keys and monthly OTA quota. On paid plans, add more of either independently with add-ons, without changing packages.
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.
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.
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.
Compare what ReRune includes with common pricing and feature differences across localization platforms.
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. 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 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 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
Share an idea, report a problem, or ask for help with ReRune.
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.
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.
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 quota is the successful SDK response-body data served by ReRune's origin during a monthly quota cycle. Headers, errors, and 304 responses do not count, and CDN hits that do not reach the origin do not consume quota.