One document. Every language your team needs.

You don't need five copies of your onboarding guide. You need one, with shared content translated automatically and local content that lives only where it belongs. That's how Rasepi works.

Onboarding Guide Powered by DeepL
🇬🇧
English Source
🇩🇪
German ✓ Up to date
🇫🇷
French ↻ 1 section updating…
🇯🇵
Japanese ✓ Up to date
🇧🇷
Portuguese ✓ Up to date
Sections changed this edit 1 of 14
Sections retranslated 1 × 4 languages = 4
Full-page approach would send 14 × 4 = 56
Cost reduction 93%

You probably have five versions of the same doc right now

Search your wiki for "onboarding." If you're a global company, you'll find Onboarding (EN), Onboarding - Germany, Onboarding - Japan, and at least one copy helpfully labelled "(DO NOT USE OLD ONE)". Each one maintained by different people on different schedules, slowly drifting apart.

❌ The copy-and-localise trap

  • Copy the whole document per market
  • 80% of the content is identical across all copies
  • One gets updated, the others silently fall behind
  • Nobody knows which version is current anymore
  • 200 docs × 4 markets = 800 things to maintain

✔ Each content lives in its own language

  • One document. Shared content auto-translated
  • Local content (DSGVO, CLT, hanko) exists only in its language
  • Update the English security policy, all translations follow
  • 200 docs stay 200 docs, regardless of how many languages
  • Local teams own their local sections. Nobody else touches them

We wrote about this in detail: Stop Maintaining Five Copies of the Same Document →

How it works under the hood

Every paragraph, heading, and list item gets a unique ID and a content hash. When something changes, Rasepi knows exactly which block changed and which translations need updating. Nothing else gets touched.

1

Write in whatever language is natural for you

Each paragraph is automatically assigned a unique block ID. You don't see this. It just happens.

2

Publish, and every language gets updated

Hit publish. Rasepi sends each block to DeepL individually. Translations are stored alongside the source with their own block mappings. Seconds, not hours.

3

Edit paragraph 3 of a 50-paragraph doc?

Only paragraph 3 gets retranslated. The other 49 stay exactly as they were. A SHA-256 hash on each block tells the system precisely what changed. No guesswork.

4

Local content stays local

Your German team adds a DSGVO section. Your Japanese team adds hanko registration steps. These exist only in their language version and aren't touched when the shared content updates. One document, multiple realities.

The cost savings are not theoretical

A 50-paragraph onboarding guide, 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 full page text, 8 times over. Rasepi sends only the 3 paragraphs that changed.

94% fewer characters sent to translation. Same result.

Translation APIs charge by character volume. When you stop resending content that hasn't changed, the savings compound fast. And it's not just cost. Translating 3 paragraphs takes seconds. Retranslating 50 takes longer and introduces lag your global teams will notice.

What this looks like in practice

Your support team maintains an FAQ in English, German, French, and Spanish.
Monday Support lead updates the answer to question 7. One paragraph changes.
Automatically Rasepi detects the hash change on that block. German, French, and Spanish translations of that paragraph are marked "stale".
Seconds later DeepL retranslates just that one paragraph in each language. Only the changed text gets sent. Everything else stays untouched.
Result All four language versions are consistent. The 40 other questions in the FAQ were never retranslated. Cost: fractions of a cent.

The details

🌐 40+ languages

DeepL supports over 40 target languages. Add new languages to your workspace whenever you need them. No extra config.

🔄 Structure adaptation

Translators can change block types per language. English uses bullet points, German uses numbered steps. Rasepi tracks the difference.

📚 Glossaries and style rules

Set up per-language term glossaries and style rules (tone, formality, date formats). Your translations sound like your team, not a machine. Read more →

One document, every language
your team speaks

Stop maintaining copies. Write once. Translate at the paragraph level. Keep local content where it belongs.

Join the Waitlist → Get in touch

Rasepi is in private beta. We're inviting teams in waves.