>Rethinking knowledge!

Documentation you and AI can actually trust.

Your team writes great docs. But six months later, nobody knows if they're still correct. Your AI tools don't know either. They just serve whatever they find. Rasepi fixes that. Every document earns a live trust score, gets flagged when it goes stale, and only shows up in search and AI results when it's actually been reviewed.

Oh, and it publishes to 40+ languages automatically. That part's pretty nice too.

app.rasepi.com / engineering / onboarding-guide
Engineering
↳ Onboarding Guide
↳ API Reference
↳ Architecture
Operations
↳ Incident Playbook ⚠
↳ On-call Rotation
HR
↳ Benefits Guide
EN DE FR ↻ JP PT
Expires Jun 30, 2026
Freshness
82 / 100
Getting Started with Rasepi
Welcome to the engineering onboarding guide. This document walks you through our stack, conventions, and deployment pipeline.
Our backend is built with .NET 8 and PostgreSQL.
✓ Updated in 5 languages
Deployments are handled via GitHub Actions. Every merge to main triggers a staging deploy automatically.
0% Content review enforced
0% Lower translation costs
0+ Languages supported
AI Assistant

Actually talk to your docs. Out loud.

Ask a question out loud and hear the answer back — pulled straight from your actual documentation. No digging, no searching, no cross-referencing. Just speak naturally and Rasepi answers using only content that's been reviewed and is still current.

  • Ask with your voice — or type — and get answers from your actual documents
  • Every answer links directly to its source so you can verify it
  • Stale docs are excluded automatically — no outdated answers, ever
  • Ask in any language, get your answer in that same language
  • Works hands-free for onboarding, compliance reviews, and quick lookups
Freshness ties directly into this. A document with a score below a threshold won't be used as a source for AI answers. If you can't trust the doc, the answer it produces can't be trusted either.
Learn more →
V Rasepi AI
Engineering + HR + Operations
What's our process for onboarding a new engineer?

Based on your Onboarding Guide (HR · updated 3 weeks ago, freshness 94/100):

  1. IT setup on day 1 (laptop provisioned via the IT Request form)
  2. Complete the 3-day Engineering Immersion programme
  3. First PR reviewed by a senior within the first week

Full details: HR / Onboarding Guide →

What incident process should I follow at 2am?
⚠️ The Incident Response Playbook has a freshness score of 31/100 and is overdue for review. I've found the content but recommend verifying with your on-call lead before acting on it.
Ask anything about your docs…
Core Features

Docs you and AI can actually rely on

Here's the thing: nobody knows if that onboarding guide from last year is still right. Your team doesn't. Your AI tools definitely don't. They just serve whatever they find and sound confident doing it. Rasepi gives every document a live trust score so everyone, humans and machines, knows what's fresh and what's not.

💚

Live Freshness Score

Every document gets a health score based on real signals: broken links, readership, review status, language version drift, and more. Think of it as a credit score for your docs. High score? People and AI trust it. Low score? It gets flagged and drops in search results until someone fixes it.

Learn more →
📅

Forced Content Expiry

Every document needs a review date, full stop. When the date arrives, the owner gets notified and the doc is flagged until someone signs off on it. No more "I think this is still right" situations.

Learn more →
🔍

Freshness Affects Rankings

When someone searches your knowledge base, or an AI tool queries it, the freshness score matters. Well-maintained documents surface first. Stale ones get pushed down. No config needed, it just works.

Learn more →
🌐

Multilingual Publishing

Write in one language and Rasepi translates it to 40+ others via DeepL. Only the sections you changed get retranslated, so costs stay low even at scale. Your Berlin and Tokyo teams see updates in seconds.

Learn more →
🤖

Talk to Your Docs

Ask a question in plain language, get an answer pulled from your actual documents. The key difference: Rasepi won't use stale docs as sources. If a document hasn't been reviewed, it's excluded from AI answers.

Learn more →

Edit Once, Update Everywhere

Save a document and Rasepi does the rest: translations update across all languages, freshness scores recalculate, and every team sees the change in seconds. One edit ripples through everything.

Learn more →
Content Health Dashboard All Workspaces
Incident Response Playbook
Operations · Updated 14 months ago
31
4 broken links Overdue by 47d Low readership
API Authentication Guide
Engineering · Updated 6 months ago
58
French version outdated 2 broken links
Onboarding Guide
HR · Updated 3 weeks ago
94
All links valid High readership All 5 languages current
Freshness impact on search & AI ranking
Score 31
Ranked #38
Score 94
Ranked #1
Content Freshness

Every doc earns its trust score. Or loses it.

Every document earns a live trust score based on review dates, link health, readership, and more. Your AI tools can't tell the difference between a doc reviewed last week and one untouched for 18 months — Rasepi can.

🔗 Links inside the document are broken or redirected
👁️ Barely anyone has read it in the last 30 days
🌐 The source was updated but a language version wasn't
💬 Readers have flagged the content as outdated
A low freshness score has real consequences. It drops the document's position in search results, and reduces how much weight AI tools give that content when querying your knowledge base. Fresh docs get found. Stale ones don't.
Explore freshness scoring →
Multilingual Publishing

One edit. Every language updated.

When someone on your team saves a document, Rasepi figures out which sections actually changed and sends only those for translation via DeepL. Everything else stays as it was.

Your French, German, Japanese, and Portuguese teams see the update within seconds of the original being saved. No waiting, no manual handoff, no one working from an old version.

  • Translations update automatically on every save
  • Only changed sections get sent for translation, cutting costs by up to 94%
  • All 40+ DeepL languages supported out of the box
  • Translators can review and adjust for their market
  • Every language version tracks its own freshness independently
On average, only one in fifteen sections changes per document update. Rasepi sends just that section for translation, not the whole thing. That's where the 94% cost reduction comes from.
See translation in action →
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
Translation cost saved 93%
Time to publish all languages ~8 seconds
🤖

Your docs feed AI tools. What those tools read matters.

When your teams or external AI assistants query your knowledge base, a stale document doesn't just give a bad answer. It gives a confidently wrong one. Rasepi makes sure only reviewed, current content is used as a source.

Learn how it works →
How It Works

How it actually works

Rasepi handles translation, review scheduling, and freshness tracking in the background. Your team just writes. Everything else runs automatically.

01

Write in any language

Write and edit in a rich-text editor that works like any tool you already know. Assign it to a workspace, pick an owner, and set when it needs to be reviewed.

02

Freshness tracking starts immediately

The moment a doc is published, Rasepi starts watching: are the links still working? Is anyone reading it? Has something around it changed? Each signal feeds into the document's live trust score.

03

Expiry triggers reviews

When a review date is coming up, the document owner gets notified well in advance. They can review and extend, hand it off to someone else, or archive it. Everything is logged.

04

Publish to all languages instantly

Rasepi sends the changed sections through DeepL and updates every active language version. By the time you've closed your browser tab, your Berlin team can read the update in German.

05

Fresh docs rise. Stale docs wait.

Search results, AI answers, and related document suggestions all weight freshness. High-scoring docs surface to the top. Nobody has to configure this. It just works.

Why Rasepi

How Rasepi compares

r Rasepi Confluence Notion GitBook
Built-in multilingual publishing
Translation cost optimisation
Mandatory content expiry
Live document freshness scoring
Freshness-weighted search & AI
Conversational doc assistant~
Edit triggers translation + freshness update
Self-hosted option

= native built-in feature  ·  = available via third-party plugin or workaround  ·  ~ = partial or limited support  ·  = not available
We believe in honest comparisons. Some competitors offer similar capabilities through marketplace plugins, add-ons, or manual workarounds, but these often come with extra cost, limited integration, and maintenance overhead. Rasepi ships these features natively from day one.

Documentation your whole
organisation can actually rely on

If your teams are working across languages, dealing with stale content, or wondering whether what they're reading is still accurate, Rasepi was built for you.

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