Runbooks
Internal KB
Private articles for the team. Useful. Incomplete when the answer is in a thread, not a page.
[internal knowledge base]
An internal knowledge base stores runbooks. Oppulence stores the promise those runbooks forget.
Internal knowledge bases keep team articles private. Oppulence keeps operational notes and relationship state in a graph you can inspect — not in opaque model memory.
Free first reportApproval before anything leavesNo invented case studies
[definition]
What “internal knowledge base” actually means
An internal knowledge base is the article store your team uses and customers cannot see. Notion, Confluence, and a private GitBook site are the usual answers. Oppulence is a different private store: readable notes, live subjects, and a signed-in register. It is not a wiki replacement.
Three jobs that are not the same.
Opaque
Model memory
Whatever the chat happened to keep. You cannot inspect it. You cannot hand it to the next owner.
Inspectable
Local vault + register
Markdown on disk, and signed-in commitments with sources. That is the Oppulence pair.
[for]
This page is for you if
- You already write promises in mail, Slack, and calls, and they disappear.
- You want a register with sources, not another place to type notes.
- Customer-facing sends should wait for a person.
[not for]
This is the wrong page if
- You need a public help center, article CMS, or ticketing inbox. That is a different product.
- You want a bot that sends as you without approval.
- You want a wall of logos and invented time-saved numbers. We will not publish those.
Questions this URL actually answers
The leftover slug is a search path. The answers stay honest about the product.
A private article store for the team. Sometimes it is the same software as the public help center, gated.
