You don’t need five copies of your onboarding guide. You need one—with shared content that’s automatically translated and local content that lives only where it belongs. That’s how Rasepi works.
Search your wiki for “Onboarding.” If you’re a global company, you’ll find Onboarding (DE), Onboarding - Deutschland, Onboarding - Japan at least one copy with the helpful note “(DO NOT USE OLD ONE).” Each of these is maintained by different people on different schedules and slowly drifts apart.
We’ve written about this in detail: Stop maintaining five copies of the same document →
Every paragraph, every heading, and every bullet point receives a unique ID and a content hash. If something changes, Rasepi knows exactly which block has changed and which translations need to be updated. Nothing else is touched.
Each paragraph is automatically assigned a unique block ID. You don’t see this. It just happens.
Click Publish. Rasepi sends each block individually to DeepL. Translations are saved along with the source text and their own block assignments. Seconds, not hours.
Only paragraph 3 is retranslated. The other 49 remain exactly as they were. A SHA-256 hash on each block tells the system precisely what has changed. No guesswork.
Your German team adds a GDPR section. Your Japanese team adds steps for hanko registration. These exist only in their respective language versions and are not touched when the shared content is updated. One document, multiple realities.
An onboarding guide with 50 paragraphs, translated into 8 languages. You update 3 paragraphs. Other platforms send all 50 paragraphs back to the translation service, for every language. That’s the entire page text, 8 times over. Rasepi sends only the 3 paragraphs that have changed.
Translation APIs charge by character volume. When you stop resending unchanged content, the savings add up quickly. And it’s not just about cost. Translating 3 paragraphs takes seconds. Retranslating 50 takes longer and causes a delay that your global teams will notice.
DeepL supports over 40 target languages. Add new languages to your workspace whenever you need them. No additional configuration required.
Translators can change block types per language. German uses bullet points, English uses numbered steps. Rasepi tracks the difference.
Set up language-specific glossaries and style guides (tone, formality, date formats). Your translations will sound like your team, not a machine. Learn more →
Stop maintaining duplicate copies. Write once. Translate at the paragraph level. Keep local content where it belongs.
Rasepi is in private beta. We’re inviting teams in waves.