Same engine underneath. What changes is what you hand over first.
Same features for everyone. The difference is what you want to stop worrying about.
You sell in five markets and the site speaks one language.
It is never the most urgent thing, so it never gets done, and every quarter it costs you something you cannot quite measure. The reason it keeps slipping is that it looks like a project. It is one tag and an afternoon.
- Nobody has to become a localization expert, including you.
- New pages get picked up and translated without anyone filing a ticket.
- One email a month says what happened. Nothing else asks for you.
Do you even need a developer?
Most hosted site builders have a settings field for exactly this kind of tag. Paste it there and you are done. If your site was custom built, your developer does it once, in an afternoon. Nothing moves, nothing is rebuilt, and nothing has to be undone if you stop.
No cap on markets
No tier limits how many languages you run, and no language has a fee of its own. Plans go by the words you store, and each language stores its own.
Something to point at
The monthly receipt says how many sentences were translated, how many languages stayed live and what the quality score is. You can put it in front of your board.
You are the whole localization team, and you'd like to stop being it.
You already pay an AI provider. What you lack is everything around it: the memory, the rules, the checks and a place for the files to land. That is what the 199 kr buys.
- Paste your endpoint and the price goes flat, however much you translate.
- Your build script fetches the translations. You never have to open a dashboard.
- Everything exports, so you can leave any day with all of it.
Ships in an afternoon
One script tag, or two fetch scripts, and your first languages are translating the same day.
Your model, your bill
Tokens land on your provider's invoice, where you can see them. We show your usage and never bill it.
Quiet by default
One monthly receipt. No weekly digest, no engagement email, nothing to unsubscribe from.
The rules live in one place, so nobody has to be the language police.
Two engineers, a designer and whoever writes the copy all push text. The rulebook is what stops five people deciding five different things about the same word.
- Your glossary and your do-not-translate list apply to every AI run.
- Tone, substitutions and instructions per language, set once.
- The checks hand you a short list to review, not a full re-read.
One memory
Translate a phrase once and it stays consistent across marketing, product and docs.
No seat maths
Add the whole team, including the person who only ever fixes typos. Same price.
Review only what matters
The checks flag the sentences worth a look, usually a handful.
A workspace per client, and a receipt you can forward without editing.
Client sites don't share a glossary, a tone or a repo. They shouldn't share a project either. Keep them separate, bill them separately, and keep the flat price.
- Separate projects, members and rulebooks per client workspace.
- No limit on sites, so a new client costs you nothing extra.
- The translations ship as files inside the client's own site.
Handover-safe
Translation files ship in the client's build. When the retainer ends, nothing has to be untangled.
Your margin, not ours
Flat cost per workspace means the tenth site is free to you.
Something to show
The monthly receipt gives you a quality score you can put in a status meeting.