Wiki product demo
Your AI already has answers.
Now give it standards.
Wiki gives your chatbots, copilots, docs assistants, and product AI verified knowledge, clear permissions, source-backed answers, and a system for keeping all of it current.
The source of truth behind every AI answer.
Most AI answers are just ungoverned guesses with better typography.
Your chatbot, docs assistant, sales AI, support bot, and internal copilot can all read different things, follow different rules, and confidently say different versions of the truth.
“Refunds any time, no problem.”
Wrong refund wording“New export feature is live.”
Stale feature mention“Refunds within 14 days.”
Missing citation“We can ship that next month.”
Unsupported promise“Comp band is $X, share freely.”
Internal source leakingSame company. Five versions of the answer.
Now the Wiki engine enters and starts organizing the system.
Do not feed your AI a folder.
Give it a source of truth.
A source enters, Wiki captures a snapshot, links it to a document, files it into a collection, and gives it an owner, a review cadence, and a status your AI has to respect.
- 01Raw source enters
- 02Wiki captures a source snapshot
- 03Source links to a document
- 04Document enters a collection
- 05Verification state appears
- 06Ownership and review cadence set
- 07Labeled: public-safe, internal-only, citation-ready
Not every AI should know everything.
Route each collection to the applications that are allowed to use it. Allowed paths run lime. Denied paths stay dark. Sensitive topics require a citation before an answer leaves.
Public Chatbot · access routes
- Product KnowledgeAllowed
- Customer SupportAllowed
- Public DocumentationCitation required
- Sales EnablementDenied
- Restricted NotesDenied
Access matrix · every application, every collection
| AI application | Public docs | Support | Product | Sales | Internal ops | Restricted |
|---|---|---|---|---|---|---|
| Public Chatbot | Allowed | Allowed | Citation required | Unavailable | Unavailable | Unavailable |
| Docs Assistant | Allowed | Citation required | Allowed | Unavailable | Unavailable | Unavailable |
| Support Assistant | Allowed | Allowed | Allowed | Unavailable | Restricted | Unavailable |
| Sales Assistant | Allowed | Citation required | Allowed | Allowed | Restricted | Unavailable |
| Internal Copilot | Allowed | Allowed | Allowed | Allowed | Allowed | Restricted |
Swipe to see all columns
- Allowed
- Citation required
- Restricted
- Unavailable
Wiki does not make every AI smarter. It makes every AI appropriately informed.
An answer is better with receipts.
Watch a question move through policy, retrieval, and contract checks before it becomes an answer. Then change the scenario and watch the system decide when to stop.
How Wiki decides
- 01Question enters Public ChatbotAudience: public
- 02Policy evaluates audience and scopePublic-safe collections only
- 03Approved source retrievedRefund Policy, verified
- 04Contract checkCitation required, public-safe
Can I get a refund for an annual plan?
Yes. Annual plans may be refunded within 30 days of the initial purchase, subject to the current Refund Policy.
Answered with a citation
Wiki AI
Wiki AI traced this answer to a verified policy source.
Your AI should know when to answer. It should also know when to stop.
Turn important claims into rules your AI can keep.
Documents are broad. AI answers are specific. A contract binds a claim to its proof, its scope, the behavior it triggers, and the test that keeps it honest.
Every contract binds five things
- Claim
- Proof
- Scope
- Behavior
- Test
Annual plans may be refunded within 30 days of the initial purchase.
- Proof
- refund-policy.md
- Scope
- Public audience · Public Chatbot, Docs Assistant
- Behavior
- Citation required. Answer allowed when the source is verified.
Do not promise roadmap delivery dates.
- Scope
- All applications
- Behavior
- Blocked. The AI declines and routes forward-looking questions to a human.
Pricing may vary by plan and region. See the current pricing page.
- Proof
- pricing-overview.md
- Scope
- Public audience · Sales AI, Public Chatbot
- Behavior
- Required qualification attached whenever pricing is discussed.
When the source changes, your AI should not wing it.
Wiki captures a new snapshot, highlights what moved, and shows every application, document, contract, and test the change touches before anything ships.
Refund Policy · new snapshot
Refunds are available within 14 days of purchase.
Refunds are available within 30 days of purchase.
Affected by this change
- Public ChatbotAI Application
- Docs AssistantAI Application
- Help Center pageDocs
- Refund Policy contractContract
- 4 answer testsTests
- Support AIAI Application
Wiki AI
Wiki AI found a source change affecting your Public Chatbot.
Most AI products treat a source change like a footnote. Wiki treats it like an event.
Knowledge changes should change your AI on purpose.
Before a knowledge change reaches customers, Wiki shows who it touches and what needs proof. A failed gate holds the release until it is fixed.
Your AI is already telling you what your knowledge is missing.
Wiki clusters the questions your AI cannot answer well, tells you why, and points at the exact source, document, policy, or test that would close the gap.
“Can I cancel after 30 days?”
“Does this support annual refunds?”
“Can I connect this to my docs?”
“Can I use internal sources in the public chatbot?”
Wiki AI
Wiki AI found four recurring questions with no approved source.
Your AI does not need more random content. It needs the right missing knowledge.
One company. One version of the truth.
The same question, asked across every surface. Before Wiki, five answers. After Wiki, one approved answer with the same source behind it.
- Public ChatbotYou can get a refund any time.
- Docs AssistantRefunds are handled within 14 days.
- Support AssistantRefunds depend on your plan.
- Sales AssistantWe can ship that next month.
- Internal CopilotRefund terms are in a doc somewhere.
Your tools can have different jobs without making different promises.
Point Wiki at your AI, whatever it does.
Pick a surface. See the sources it should read, the boundaries it should respect, the claims it should keep, and what Wiki prevents.
Public answers should come from public-safe knowledge.
Recommended sources
Collections
Policy boundaries
Required contracts
Recommended tests
Suggested pack
- Source monitoring
- Watch Refund Policy and Pricing Overview for source changes.
- Release requirement
- Rerun answer tests before a policy change reaches customers.
- What Wiki prevents
- Internal notes reaching a public answer.
This is what a governed AI knowledge base looks like.
A tour of the Nintendo demo workspace. Click through the panels. Every state here is fixture data built to show how the system behaves.
Ten things Wiki does that a folder never will.
Give it standards.
Start with one source, one policy, and one answer worth trusting. Wiki handles the rest of the system around it.
Plans from $29/mo. Cancel anytime.