Most documentation platforms hide the edit button and call it a “read-only view.” Rasepi gives readers a completely standalone portal. No hubs, no sidebars, no author clutter. Just topics, search, and answers.
Open Confluence and find a document you need to read. You’ll see a sidebar tree with sections that don’t belong to you, breadcrumb navigation in a hierarchy you didn’t create, and a page full of author metadata. All of this exists because the interface was built for authors. Readers are only allowed in by accident.
We’ve written about the cognitive science background: Readers and authors operate in different modes of thinking →
Creators and readers have different goals, so they get different interfaces. Not different permission levels on the same interface. Actually different applications that share the same content underneath.
Hubs, entries, versions, expiration dates, translation status, block-by-block editing. The full suite of tools for people who create and maintain content. Creators think in terms of where things are located and how they relate to one another.
Topics, search, and popular articles, sorted by recency. Readers don’t know which hub “Getting Started with Rasepi” is in. They simply type what they need and find it. The content is the same. The structure around it is completely different.
AI systems don’t need either of these views. They need structured, machine-readable content with timeliness metadata. Rasepi provides this as a third layer. Outdated content is downweighted or excluded entirely.
Content is grouped by topic: “Getting Started,” “Security,” “Deployments,” regardless of which hub a creator has placed it in. Readers browse by topic, not by file structure.
Search results are weighted by recency. Current, well-maintained documents appear first. Outdated content slides down in the order or is flagged.
Readers can ask questions and receive answers based on your actual, verified documentation. The assistant cites sources and warns of outdated content.
Every reader can switch languages on any page. The German office reads in German. The team in Tokyo reads in Japanese. The same content, their preferred language.
“Popular This Week” highlights content that others are actively reading. Useful during disruptions, product launches, or onboarding waves when everyone needs the same documents.
Readers don’t need to understand your hub permissions or content hierarchy. If they have access to a topic, they see the articles. It’s that simple.
Every author seat includes up to 50 reader seats at no extra cost. A team of 20 authors gets 1,000 readers, each with full access to the portal, the AI assistant, and all languages. We think charging per seat for people who just need to read the Wi-Fi instructions is a strange business model.
Readers get their own portal. Authors get their own tools. Everyone gets better documentation.
Rasepi is in private beta. We’re inviting teams in waves.