Enterprise DNA

Instead of Lokalise

Stop renting Lokalise. Own your localisation system.

We build your version around the languages you ship, bring your Lokalise exports across and run the review workflow with you. Your wording, your rules and your database.

Lokalise lists Advanced at US$1,049 a month, equivalent to US$12,588 over twelve months before extras. Confirm the billing option and final terms with the vendor.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The subscription comparison

Separate the language work from the platform bill

Lokalise sells a hosted localisation platform. Its pricing compares word capacity, seats, integrations and delivery allowances. Decide which parts your team needs before replacing it.

paid

Advanced subscription

The displayed US$1,049 monthly base price is US$12,588 annualised. Your selected billing terms and extras determine the actual invoice.

translate

Word capacity

Hosted and processed words are separate capacity measures on the pricing comparison.

group

Seats

Standard and advanced seats are separate allowances. Check how your translators and managers use each.

account_tree

Workflow features

The comparison includes tasks, custom translation statuses and branching. Map the steps your team actually follows.

extension

Connections and delivery

Integrations, automations and delivery calls have their own capacity lines. Scope the connections your owned version needs.

fact_check

Reporting and review

Quality reports and review records help manage language work. Your version starts with missing text, review decisions and release blockers.

The owned version

Keep the language desk under your control

Release planning

See which languages are ready

A single readiness summary shows the work left before the next release.

  • check Missing translations by language
  • check Approvals invalidated when the original wording changes
  • check Character limits checked against your own labels
  • check A combined view of review status and your chosen evidence deadlines

Quality checks

Find specific problems before handoff

Give the reviewer a clear list of problems instead of a completion percentage alone.

  • check Missing named placeholders
  • check Preferred wording checked against your terms
  • check Claim wording waiting for supporting evidence
  • check A separate reviewer records the decision after an edit

Weekly work

Give every follow-up an owner

Bring unfinished language work and overdue decisions into the same weekly review.

  • check Follow-ups with owners and due dates
  • check Translator briefs prepared from current wording
  • check Draft release checklists with reviewer evidence
  • check A history of recorded edits and review decisions

Your records

Keep a usable copy of your work

Your translations stay in an owned database, with the original imported text available for reconciliation.

  • check Import the supported Lokalise language exports together
  • check Preserve source descriptions and comments
  • check Export records and review history when needed
  • check Add your own evidence rules and reports as the process changes

Make it yours

Design your own Lokalise replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Lokalise. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Lokalise replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Lokalise data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Localisation for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Localisation for Claude Code

Connected to your own database

Which languages still have release blockers?

Harbour booking

Cale to
de
Tal re
3
Ady bl
0
Ocked
3

Harbour booking

Cale to
fr
Tal re
3
Ady bl
1
Ocked
2

Harbour trade portal

Cale to
de
Tal re
1
Ady bl
0
Ocked
1

Harbour trade portal

Cale to
fr
Tal re
1
Ady bl
0
Ocked
1

Ask it anything

Questions Lokalise cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which languages are blocked for the next release?
chat_bubble Which translations are missing?
chat_bubble Which reviewed words became stale after a source edit?
chat_bubble Which placeholders no longer match the source?
chat_bubble Which labels exceed our character limits?
chat_bubble Which terms break our chosen wording?
chat_bubble Which claims have overdue supporting evidence?
chat_bubble Who owns the overdue translator follow-ups?
chat_bubble What changed and who recorded it?
chat_bubble What decisions belong in the Monday review?

Switching

How to switch from Lokalise

A move involves exporting your language records, mapping your fields and rules, checking the import, and running both systems side by side briefly.

  1. 1

    Export your language records

    Export the plain-text language data you want to bring across from each supported Lokalise Expert Web or mobile project. The documented import accepts CSV exports, with one file per language, and retains source text, translations, descriptions and comments. Check the export options in your Lokalise account with Lokalise. Vantage exports do not use this CSV format, so they need separate mapping.

  2. 2

    Load a test import

    Create the project and identify its source language, then load the Lokalise exports using the import preview first. Review the preview before applying the import. This gives you a chance to catch problems before records are added. The import is for plain text, so confirm that richer formats or other requirements have been scoped separately.

  3. 3

    Check the import preview

    Compare source and target key counts for each language. Check any issues the preview flags, missing or unexpected values, and whether descriptions and comments landed as expected. Imported approvals do not carry over as current approvals, so plan a fresh review. Other history needs separate mapping if you want it brought across.

  4. 4

    Run both systems briefly

    Keep Lokalise and the new database in use side by side for a short period. Use real translation and review work to check that your strings, descriptions and comments are present, and have reviewers repeat the approvals you need. Confirm your release checks fit the process you plan to use. Track anything that still depends on a Lokalise feature or connection.

  5. 5

    Switch off Lokalise

    Switch the team to the new process only after the checks pass and the people responsible for reviews know where to work. Keep the Lokalise account available during the overlap, then turn it off when you are satisfied the required records and workflow are covered. Retain any export or history you still need outside the new system.

construction

Where the real effort goes

The import itself is usually not the main effort. Most work is mapping your own fields and review or release rules, then deciding which history to bring. The supported import carries plain-text content, descriptions and comments, but past approvals need fresh review and other history may need separate mapping. If Enterprise DNA runs the move, they handle this mapping and import work with you.

Not ready for a call?

Get your Lokalise switch plan by email

We will send you the step-by-step plan for moving your business off Lokalise, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose who builds and runs your version

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and install with npm install
  2. 2 Run npm run demo and inspect the fictional language records
  3. 3 Use Claude Code, Codex, OpenCode or Cursor to run the workflows
  4. 4 Preview your Lokalise Expert CSV exports and reconcile the imported wording
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your languages, fields and approval rules
  • check Your Lokalise exports mapped and checked
  • check A web front end for visual review where your team needs it
  • check A different technical foundation when it suits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Language work connected to your agreed business systems
  • check Backups, operational support and ongoing changes
  • check Your review process maintained as products and languages change
Talk about your language workflow

Questions

Instead of Lokalise, answered

Does this replace every part of Lokalise? expand_more

The free version covers plain text translations, review decisions and release checks. Enterprise DNA scopes the visual review screens, richer language formats, translation services and delivery connections your version needs. We check those requirements before recommending a switch.

Will our existing translations come across? expand_more

The free version reads the documented language exports from Lokalise Expert Web and mobile projects. Original text, translated text, descriptions and comments are retained. Previous approvals need a fresh review. Other history and Vantage exports need separate mapping, which we scope with you.

Who decides whether a translation is correct? expand_more

A competent person checks meaning, grammar and context. The system flags specific record problems and requires a reviewer different from the last editor. Recorded names are attribution, so your operated version also needs the agreed access controls.

Can we change the rules to fit our release process? expand_more

Yes. The free version already supports character limits, preferred terms and evidence review dates. We build your version around your own approval stages, reporting and release process, including screens when required.

What do we pay Enterprise DNA? expand_more

The software is free under an MIT licence. Running it yourself has hosting and assistant costs. We customise and operate your version for one setup fee, then a retainer. Sam scopes the migration, connections and ongoing work with you before you commit.

Own the wording and the workflow around it

Spend 30 minutes with Sam reviewing your Lokalise bill, the languages you ship and the work your team actually does. We will map the version Enterprise DNA can build and run for you.

Book a 30-minute call Get the free version

Localisation for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Lokalise?

Get your version built