Most platforms let content rot quietly. Rasepi gives every doc a live score that tells readers and AI tools exactly how much they should trust it.
You've seen it. A Confluence page that was last updated 18 months ago. No way to know if it's still accurate. You read it anyway, because what else are you going to do?
It's not complicated. Every doc has an expiry date. The closer it gets to expiry without being reviewed, the lower its score drops.
When you create or update a doc, you pick an expiry window. Could be 30 days for a fast-moving runbook, 6 months for stable policy docs, or anything in between. This isn't optional.
Based on when the doc was last reviewed, how close it is to expiry, and whether the content has changed, Rasepi assigns a score from 0 to 100. A freshly reviewed doc scores 100. A doc past its expiry date? Probably closer to 20.
As a doc approaches its expiry date, the owner gets a friendly reminder. Review it and confirm it's still accurate, or update it. Either way, the score stays high.
If nobody reviews a doc in time, its score drops and it shows a visible warning. Readers know immediately that this content might be outdated. No guessing required.
Rasepi watches more than just the calendar. These real-time signals all contribute to a document's trust score.
AI tools are great at finding documents. They're terrible at knowing whether those documents are still accurate.
When a Copilot or RAG pipeline indexes your knowledge base, it treats a 2-year-old incident playbook the same as one reviewed yesterday. That's a problem.
Rasepi's trust scores give AI tools a signal they've never had before: how fresh is this content? An AI that surfaces a doc with a score of 95 is giving you something reliable. One that finds a doc scoring 15? It can warn you, or skip it entirely.
This isn't just about humans reading docs. It's about making your entire knowledge base trustworthy for the tools that are starting to depend on it.
Set different expiry periods for different types of content. A fast-changing API doc might need 30 days. Company policy might be fine with 12 months.
Confirming a doc is still accurate is one click. You don't have to rewrite anything. If it's correct, just confirm it and the clock resets.
Admins get a workspace-wide view of freshness scores. Sort by staleness, filter by team, spot the docs that need attention before they cause problems.
Freshness scores are available via API, so you can integrate them into your own tools, dashboards, or AI pipelines. Build trust checks into your workflow.
Rasepi gives every document a trust score. Your team knows what's fresh. AI tools know what's fresh. Nobody wastes time on content that's past its shelf life.
Rasepi is in private beta. We're inviting teams in waves.