Knowledge that tells you when it's going stale.
As many knowledge bases as you need, each with a purpose, required sections and a review queue. Documents are stored as a graph with hybrid search, an AI assistant answers across tickets, issues and docs, and a health score tells you what is stale, orphaned or missing.
Example data
From a blank page to a knowledge base that stays healthy.
Set it up
Give each knowledge base a purpose and the sections every page must answer. Grant read, write or full access per team.
Write
New pages are checked against the profile. Pages that fail are held in the review queue, out of search, until someone approves them.
Connect
Documents and the links between them are stored as a graph with embeddings, so search works by relationship and by meaning at once.
Ask
The assistant answers across knowledge bases, tickets and issues, in the app or from Claude, ChatGPT, Copilot and Gemini CLI over MCP.
Keep it healthy
Knowledge Health flags stale pages people still open, orphans and searches that found nothing. Recompute it whenever you like.
Everything in Knowledge Base.
Graph storage
Documents and the links between them are stored as a graph, with embeddings for meaning.
Hybrid search
Search by relationships and by meaning in the same query.
Graph view
Pan, zoom and click to highlight connections, with a reading panel on the side.
AI assistant
Ask about your tickets, issues and knowledge bases. Every chat is saved, so you can pick it up again later.
Profiles and required sections
Each knowledge base has a purpose and the headings every page must answer. A section that cannot be answered honestly is one a page cannot fake.
Review queue
New pages that fail an automated check are held for review and kept out of search until someone approves them. Hold every page if you prefer.
Access by team
Read, write or full access per team and per knowledge base. Owners see everything.
MCP connectors
One connector per member for Claude, ChatGPT, GitHub Copilot or Gemini CLI. It signs in as that member and reaches their knowledge bases, tickets and work log.
Knowledge Health
Flags stale documents people still open, orphans and unmet demand in search. Recompute it whenever you like.
Activity log
Create, update, rename and delete per member, plus an audit of every assistant action, in the app and over MCP.
Soft delete
Owners and admins can bring a deleted knowledge base back.
A closer look.
Pages that answer the questions you decided matter.
Each knowledge base has a purpose and the headings every page must answer. A runbook without a rollback section, or an owner left blank, fails the check and is held in the review queue, out of search, until someone approves it. A section that cannot be answered honestly is one a page cannot fake.
- Required sections per knowledge base
- An automated check on every new page
- The review queue keeps unapproved pages out of search
- Hold every new page if you prefer
Example data
Your knowledge inside the assistant your developers already use.
One connector per member for Claude, ChatGPT, GitHub Copilot or Gemini CLI. It signs in as that member, so it sees exactly the knowledge bases, tickets and work log entries they can see in the app, and every action it takes is in the activity log.
- Claude, ChatGPT, GitHub Copilot and Gemini CLI
- The same access checks as the web app
- Reaches knowledge bases, tickets and the work log
- Every assistant action logged
Example data
The assistants your team already uses.
Docs for the people who have to trust them.
Knowledge Base FAQ.
How many knowledge bases can we have?
As many as you need. Each has its own purpose, required sections, review settings and team access, and owners see all of them.
What does the review queue hold back?
New pages that fail the automated check against the knowledge base's profile, such as a required section left empty. They stay out of search until someone approves them. You can also hold every new page if you prefer.
What does Knowledge Health measure?
Three things: stale documents people still open, orphaned documents nothing links to, and searches that found nothing. Together they make a score you can recompute whenever you like.
Which AI assistants can connect?
Claude, ChatGPT, GitHub Copilot and Gemini CLI, through one MCP connector per member. The connector signs in as that member and reaches their knowledge bases, tickets and work log with the same access checks as the web app.
Is the assistant's activity logged?
Yes. Every assistant action, in the app and over MCP, is in the activity log next to who created, updated, renamed or deleted a page.
What if someone deletes a knowledge base?
It is soft deleted. Owners and admins can bring it back.
How is Knowledge Base priced?
Per seat for each person who can reach Knowledge Base, plus storage per gigabyte. The pricing page has the numbers.