Most doc platforms hide the edit button and call it a "reader view." Rasepi gives readers an entirely separate portal. No hubs, no sidebars, no authoring chrome. Just topics, search, and answers.
Open Confluence and find a document you need to read. You'll see a sidebar tree of spaces you don't own, breadcrumbs into a hierarchy you didn't create, and a page covered in authoring metadata. All of that exists because the interface was built for writers. Readers just happen to be allowed in.
We wrote about the cognitive science behind this: Readers and Writers Are in Different Mental Modes →
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, expiry dates, translation status, block-level editing. The full machinery for people who build and maintain content. Creators think in terms of where things live and how they're connected.
Topics, search, and popular articles ranked by freshness. Readers don't know which hub "Getting Started with Rasepi" lives in. They just 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 view. They need structured, machine-readable content with freshness metadata. Rasepi provides that as a third layer. Stale content is weighted down or excluded entirely.
Content is grouped by topic — "Getting Started", "Security", "Deployments" — regardless of which hub a creator stored it in. Readers browse by subject, not file structure.
Search results are weighted by freshness score. Current, well-maintained docs appear first. Stale content drops in ranking or gets flagged.
Readers can ask questions and get answers grounded in your actual, reviewed documentation. The assistant cites sources and warns about stale content.
Every reader can switch languages on any page. The German office reads in German. The Tokyo team reads in Japanese. Same content, their preferred language.
"Popular this week" surfaces content other people are actively reading. Useful during incidents, launches, or onboarding waves when everyone needs the same docs.
Readers don't need to understand your hub permissions or content hierarchy. If they have access to a topic, they see the articles. Simple as that.
Every writer seat includes up to 50 reader seats at no extra cost. A team of 20 writers gets 1,000 readers — each with full access to the portal, AI assistant, and all languages. We think charging per-seat for people who just need to read the WiFi instructions is a weird business model.
Readers get their own portal. Writers get their own tools. Everyone gets better documentation.
Rasepi is in private beta. We're inviting teams in waves.