Publish
Docs in your customers’ language, on your terms
Publish in English, translate everywhere else — or keep a locale human-only. AI drafts translations governed by your per-locale glossary and tone rules; reviewers approve before they go live.
Translated from EN · glossary: “workspace → Arbeitsbereich”
Translation where it counts
Per-article, per-section, per-release and even per-API-operation translations.
Your glossary travels
Per-locale terminology and tone guidance is injected into every translation prompt — product terms stay product terms.
A clear review boundary
Mark locales as AI-published or review-required. The gate applies to translations the same as everything else.
Readers notice only the result
A locale switcher on every page, localized UI strings, and answers in the reader’s language.
A good fit if…
- Products selling across regions
- Support teams tired of translating tickets, not docs
- Teams burned by machine translations that miss terms
Works well with
Help center
Guides, FAQs, changelogs and reference on one fast site — searchable, indexed by Google, and readable by AI search engines.
Keep currentDoc suggestions
Twelve signal sources — from support themes to code pushes — feed one queue of proposed updates.
Keep currentCode to docs
Link your repos and pick the paths that matter.
Get started
Make space for the questions that matter
Join the teams keeping their help center current without the busywork. Free while in early access.
No credit card · Your docs export any time