Other platforms say “verified.” Verified by whom? When? On what basis? Rasepi shows you exactly why a document was downgraded and tells you when something in the real world makes your documentation unreliable.
Most knowledge platforms have someone click a button that says “this is still correct.” This badge tells you nothing about what has happened since the last review. The real world doesn’t wait for your review cycle.
Rasepi does more than just count the days since the last review. It looks for actual changes and links them to the affected documents.
Connect your GitHub repos, CI/CD pipelines, monitoring tools, policy systems, and product configuration. Rasepi watches for changes that could affect your documentation: releases, deprecations, configuration updates, incident postmortems.
When a dependency changes (a new version is released, an API is marked as deprecated, a tool is replaced), Rasepi identifies which documents reference that source and assesses the impact on each one.
Not just “this document is outdated.” The specific reason: “v2.0 released, your installation guide still references v1.x” or “/api/v1/payments marked as deprecated in the last deployment.” The notification is visible to everyone.
Reviewers see what has changed, when it changed, and which sections are affected. Correct the specific parts, confirm the rest, and the trust score recovers immediately.
These are the types of changes that silently destroy documentation every day, and the signals that Rasepi attaches to each one.
/api/v1/payments as deprecated in favor of /api/v2/payments and publishes the change.
Each Trust Score is a composite of internal and external signals. Each is weighted, tracked, and visible in the score breakdown.
If you use AI co-pilots, RAG pipelines, or enterprise search, you need a way to tell these tools which documents are worth citing. Confidence scores give them exactly that signal.
Set a confidence threshold: “AI assistants may only cite documents with a confidence score ≥ 0.8 that were reviewed within the last 30 days and are not marked as modified externally.” Rasepi enforces this. Your AI assistant will never confidently cite a document that references an outdated API.
Trust metadata is available via API, MCP server, and webhooks. Integrate it into your RAG pipeline, your enterprise search ranker, or your internal AI governance layer. Every response your AI provides can carry a trust signal.
Rasepi is API- and AI-first. The web interface is just a client. The REST API, the MCP server, and the webhook system are equally powerful. Your internal tools, CI pipelines, and AI assistants all retrieve the same trust data via the same endpoints. Explore the developer documentation →
This isn’t about adding AI to documentation. It’s about making documentation safe for AI. Without trust metadata, AI tools reinforce outdated information with complete confidence. With it, they know what to cite, what to warn about, and what to skip.
Different content has different lifespans. Rasepi lets you define expiration policies by document type and enforces them automatically.
Rapidly changing operational documents are assigned short expiration windows. If the tooling changes, the runbook is flagged immediately. If not, it is still reviewed monthly.
Stable policy documents do not require monthly reviews. But they must be checked when regulations change. Rasepi handles both: scheduled expiration and external triggers.
Competitive pricing changes rapidly. A weekly cycle ensures that sales teams always have up-to-date figures. Changes to product configuration trigger immediate flags regardless of the schedule.
For compliance SOPs and security procedures, require the reviewer to formally confirm that they have reviewed the content. The attestation is logged, timestamped, and linked to the trust score.
Guru and Tettra let you set a verification interval. Every 90 days, someone clicks “still correct.” If a breaking change was released yesterday, no one knows about it until the next review cycle. The badge says “verified.” The content is already incorrect.
Confluence and Notion don’t track timeliness. A page updated 3 years ago looks exactly the same as one updated today. Their AI features index everything with equal confidence. Atlassian Intelligence can summarize a page, but it can’t tell you if the page is still true.
Rasepi assigns each document an evidence-backed trust score. Your team sees why a document was downgraded. Your AI tools know what can be cited with confidence. No one follows a runbook that references a tool you replaced six months ago.
Rasepi is in private beta. We’re inviting teams in waves.