Join early access
Live on Product Hunt

i18ner is an AI-native localization platform built on simplicity, transparency, and cost control. Bring your own provider keys, skip per-string pricing, and take control of the whole localization workflow from start to finish.

Join early access

A recording of i18ner: a JSON file is dropped into an empty project, parsed into its source strings, and machine-translated into Korean, German and Spanish in the editor grid.

AI driven translations

Powered by your choice of Anthropic, DeepL, Google Translate or OpenAI.

Bring your own key

Use your own keys and set your own limits to keep pricing predictable.

Translation memory

Reduce API cost and improve consistency across multiple projects.

Quality assurance

Run placeholder, glossary and formatting checks on the rules you hand-pick.

A head in profile, chin resting on a fist, with a question mark drawn above it.

Traditional localization platforms act as gatekeepers. Workflows are wrapped in layers of dashboards and dozens of integrations you never use, but pay for all of it through per-seat and per-string taxes with enormous markups.

i18ner flips that model upside-down. You bring your own keys and skip per-string and per-user pricing. Pay for what you actually need, and what you actually use. i18ner offers predictable pricing, whether you are one person, a small team, or an enterprise.

We are confident that localization is a problem that AI can actually solve, given it is incorporated thoughtfully alongside battle-tested solutions, instead of being bolted on over them. We believe retrofitting a product around AI is not enough, so we built i18ner around AI instead.

To pricing*
  • Anthropic
  • DeepL
  • Google Translate
  • OpenAI

A person in profile holding a bucket up under a row of four taps, filling it from the second one while the first hangs dry and the last two wait their turn.

Powered by your choice of the different providers we support. Add one key and you're good to go. Add multiple keys, and you unlock smart routing. For each language, you can custom-define the provider priority, choosing which provider should be tried first, second, and so on.

Everything runs on your own account, where it is billed by the providers directly. You pay us a flat fee, for the infrastructure and features: the editor, translations, review-flow, translation -memory, quality assurance and the integrations your team uses.

A head in profile with a library shelved inside it, and translated cards streaming out of it into the open.

Previous translations are ranked and saved. When the same wording comes up again, the answer comes from memory instead of going to a provider. Your product keeps saying the same thing, the same way, in every language. And the calls you never had to make, translate to money you never spent.

A hand tipping a small box, translation cards falling out of it into an open head in profile.

Years of translations are sitting in the tool you are leaving. Export and upload them to i18ner, and your memory arrives intact: every segment ranked, searchable, and answering before a single provider call goes out. Nothing gets paid for twice just because it changed address.

Your glossary moves with you too. Upload the termbase and the terms it settles are applied while translating, then checked again by QA. The vocabulary your team agreed on months ago survives the move without anyone having to argue it out a second time.

Two hands over a crowded keyring, one of them taking a single key with a small flag tag tied to it.

Role-based Access Control (RBAC) allows admins to bring translators and reviewers in for specific languages and have them work on those specific languages only. The other languages are not theirs to view or edit.

Every save runs the changes past checks that have been configured. A variable that went missing and would have crashed the screen, a brace left open, a term your glossary settled months ago. Each issue lands on the row it came from, and you either fix it or wave it through.

A recording of review in i18ner: translation rows are approved, marked for revision and rejected in turn, with a comment left against one of them.

Once translations are present, reviwers can either approve it, mark it for revision, or reject it. Comments attach to every translation, so the discussions sits next to the text instead of in a thread somewhere.

A hand holding three sheets fanned out like playing cards, each one tagged with a different flag.

Everything is rebuilt into the shape you uploaded, keys and structure intact. Download them manually, or connect a VCS like GitHub and let i18ner open the pull request for you.

Nothing ships before you say so. Untranslated strings hold delivery back, and you can add your own gates on top: no export while QA errors are unresolved, while translations have gone stale, or while anything is still waiting on a review.

Early access

Join the list for launch updates and private betas.