Pricing
Priced on keys and languages, nothing else
No per-word charge and no meter running while your content grows. A plan is a number of translation keys and a number of languages, and it is already included if you run any other MultiPrimeX product.
One product surface, a handful of markets
Enough for a client area or a single application in the languages your first markets actually need.
Several surfaces, a real regional footprint
Client area, mobile and email templates together, across the language set a multi-region broker typically ends up carrying.
Everything you ship, everywhere you ship it
The full catalogue of surfaces and the complete language list, including right-to-left scripts and regional variants.
Beyond the published tiers
For deployments whose key count or language list does not fit a plan, or that need terms the standard plans do not carry.
What sets the plan
Two numbers, and neither of them is how much you write
A key is a string, not a word
One key is one piece of text you reference — a button label, a notification, an error. Translating it into twenty languages is still one key, which is why the language count is priced separately.
Languages are counted, not characters
There is no per-word or per-character charge. Adding a market means moving up a language band, not watching a meter while your content grows.
Revisions are not re-billed
Changing the text behind a key, or retranslating it, does not consume anything new. Keys are a count of what exists, not of how often you touch it.
Free alongside any other product
If you already run another MultiPrimeX product, localisation is included at no additional charge. It exists as a paid plan for firms who want it on its own.
FAQ
Localisation pricing: common questions
6 short answers to what teams ask before a demo.
One referenced string — a label, a button, a notification, an error message. It counts once regardless of how many languages it is translated into, and regardless of how often you revise the underlying text.
Yes. Running any other MultiPrimeX product includes localisation at no additional charge. The paid plans exist for firms that want localisation without taking the rest of the stack.
No. The plan is set by the number of keys and the number of languages. Content length does not affect the price, which is what makes the monthly figure predictable as your product grows.
You move to the next plan. There is no per-key overage rate, because a string count that drifts past a threshold is a sign the deployment has grown rather than an event to bill for.
No. Arabic, Persian and other right-to-left scripts count as languages like any other, and the layout handling for them is part of the product rather than an add-on.
They are the published plan prices for a standard deployment. Contract length and multi-product arrangements can change what you actually pay, and those are settled in writing rather than implied here.
Still have a question?
A specialist will answer it directly, with your set-up in mind.
Ask a specialistNot sure how many keys you have?
Most teams underestimate it by a wide margin. Send us the surfaces you want localised and we will count them before you pick a plan.