Localization for solo devs and small teams, without the enterprise tax.
The translation tool Skiwo built for ourselves — now yours too. Push English keys, translate with Claude or by hand, fetch into your build. No approval workflows. No environments. No RBAC mazes.
We're piloting with a small group right now. Email support@skiwo.com if you'd like to be considered.
Three things, done right.
Most translation tools are bloated for the people we're not. So we picked three problems and made them feel obvious.
Built for ourselves, first.
We use it in production every day. Every regression hits us before it hits you.
Simple on purpose.
No approval workflows, no branches, no role hierarchies. One owner, members, projects, languages. The complexity that makes Crowdin hard to onboard isn't here, deliberately.
Your rules, then AI.
Glossary, DNTs, substitution rules — set them once. Translate yourself, or let Claude help. Either way it stays inside your rules and learns from translation memory. One editor for everything.
How it works.
Three commands, then your build pulls translations like any other static asset.
Push English keys
Run a script on every deploy. Keys get created on BeMyWords; removed keys get hidden — never deleted, so translations survive.
npm run push-english
Translate
Claude drafts each translation with your glossary, tone, and DNTs respected. Edit in-line. Translation memory pre-fills repeats across projects.
Claude · in-editor review
Fetch at build
Your CI calls one endpoint per language. Translations land as JSON / YAML / .strings / .xml / .arb — whatever your stack expects.
npm run fetch-translations
Two things you won't find elsewhere.
Built because translating without context, or shipping a one-character fix that needs a full redeploy, is the part that hurts.
Translate from a screenshot — without storing it.
Upload or paste any screen. Claude reads the image, surfaces which of your strings appear on it, and we drop the bytes. Your screenshot lives in your browser for up to 8 hours — never on our servers, never in our logs, never in our backups.
Useful when
landing.cta.primary
could be three different buttons — and when the screen has things you'd rather we didn't keep.
Konami-code into the editor on your live site.
Drop our
<script>
tag in your layout. On any page, type:
Click any string, edit, save — the page swaps to your new translation without a rebuild. End users see nothing; translators see their edits live.
Two scans that catch what slips past.
Translation memory keeps repeats consistent. The glossary keeps terminology in line. These two catch the rest — English text living in your Norwegian tab, a teammate's hand-edit from before the rules were loaded.
Audit a language for impostor strings.
Pick a target language; Claude detects the actual language of every value and flags the ones that don't match — at confidence ≥ 70%. Open the report and the editor opens with the suspects already filtered in, so you fix or dismiss in the same view.
Useful after migrating from another tool, importing legacy YAML, or any time AI Translate Blanks took a guess no-one reviewed.
Checkup: review every language for one key, in one shot.
Click Checkup on any string and get back a verdict for every language at once — with a suggested fix for the ones that drifted from English. Run it on a single key in the editor, or scan the whole project as a background job and walk the report.
Catches the keys translated before you set up the glossary — or the ones a teammate hand-edited when DNTs and substitution rules weren't loaded.
Pulls into the stack you already use.
Two are production-verified by Skiwo's own sites. The rest are best-effort drafts — open them up and tell us where we got it wrong.
Where we sit.
We're not the all-in-one. We're the one you finish setting up before lunch.
vs Lokalise / Crowdin
Same core: keys in, translations out. Smaller surface area. Skip the four-stage approval workflow your team will never use.
vs Tolgee / Locize
Closer comparison. AI built in , the same simple shape. Bring your existing project; the migration is a config swap.
vs POEditor
One editor handles glossary, do-not-translates, substitution rules, and translation memory in one pane — not three.
Ship multilingual, today.
We're piloting with a small group of approved customers. If your project sounds like a fit, we'd like to hear about it.
Request access