FAQ

Questions, Answered

What liveknowledge does, what it costs, and what it does not do yet.

Getting Started

What liveknowledge is, what it costs and how to begin.

What is liveknowledge?
A team knowledgebase, for people and for AI. Your team writes its how-tos, decisions and handbooks as pages in a page tree. Each page has an owner and a verified date, and your colleagues and your agents read the same pages under the same rules. It is part of liveworkspace, beside livediagram, liveplanner, livedocuments, livedesign and livehuddle.
Is liveknowledge free?
It is free to start, with no card and no trial clock, and it is open source under the MIT licence: the code is on GitHub. Writing, linking, verifying, searching and connecting an agent cost nothing. Ask runs on built-in AI, included with daily limits. A team may add its own Claude or OpenAI key instead, and that usage is paid to the provider, not to us.
Is there a paid tier?
Not at launch. Everything this site describes is free to use, built-in AI included. The only AI cost a team can carry is its own Claude or OpenAI key, if it adds one.
How do I start a knowledgebase?
Open the editor and a new knowledgebase starts on a screen of choices. Start blank, pick a structure such as Team Handbook or Runbooks and On-Call with its pages already in place, import from Notion, Confluence or a folder of Markdown, or describe what it is for and AI proposes the pages for you to accept. Describe to Set Up runs on built-in AI, or on your team’s own key if it adds one.
Do I need an account?
Not to write. Open the editor and start a knowledgebase, and it is kept Offline in your browser. Verifying pages, Ask, Describe to Set Up, AI Knowledge, sharing and connecting an agent need a free account, because each of them has to know who you are.
What is liveknowledge not?
It is not a slide or page layout tool: for slide decks, infographics and documents laid out on paper pages, use livedocuments. It is not a chat or a project tracker either. A knowledgebase page is writing, with tables, pictures, charts and drawings in the text.
How do I edit a page?
A page opens to read. Press Edit, or double-click the writing, and you are in a draft that everyone editing the page shares live, each with their own caret. Readers, search, Ask and agents keep seeing the saved page until someone presses Save. Cancel leaves the draft to anyone still editing; if you are the last, it asks before throwing your changes away.
Can a page have a cover?
Yes. Add Cover, beside the reading time under a page’s title, sets a picture, one of the theme’s gradients or an animated background across the top of the page. Knowledgebase Style sets the look of every page at once: its theme and its fonts.
How big can a knowledgebase be?
Up to 500 pages, nested up to eight levels deep. Both limits are checked on the server as well as in the editor, and the control that would pass one says why it is disabled.
Are there templates?
Yes, and each is a whole knowledgebase rather than a single page: thirty-two structures such as Team Handbook, Engineering Handbook, Runbooks and On-Call and Sales Playbook, each a tree of pages with a line on what belongs on each and the headings to write under. They are grouped under Company, Engineering, Product, Customers, Operations, Community, Education and Personal. Pick one from the template gallery or from a new knowledgebase’s start.

Trust and Verification

Owners, verified pages and reviews that come due.

How does verification work?
Each page has an owner. An Editor or a Participant presses Verify, and the page shows a green tick with who verified it and when. The knowledgebase has one Review Period (30, 90, 180 or 365 days, or never), and once it has passed a page reads Review Due until someone verifies it again. Nothing is verified automatically, and a large change made after verifying is marked Changed Since Verified.
Who can verify a page?
Editors and Participants. Viewers see every page’s state but cannot change it. Only an Editor sets the Review Period, from Page Health beside any page, and it applies to every page. Verifying needs an account, so a knowledgebase kept Offline has no verified pages.
How do owners know a review is due?
The Knowledgebase Home lists Yours to Review: the pages you own whose review is due, oldest first, each with a Still Right button that verifies it. Each owner also gets one email, Pages Due for Review, at most once a day, while their Knowledgebase Reviews notification is on.
What is AI Context?
A section in every page’s right rail: whether the page is Always in Context (handed to every agent first, with its size in tokens), the questions Ask answered from it, and which agents read it this week, each shown once there is one. Always in Context pages share a budget of 8,000 tokens, and a page that would pass it says so.
What does AI Knowledge show?
Which agents read your knowledgebase and what they read most, the questions nobody could answer, pages that disagree with each other, the edits agents have suggested, and the pages you marked Always in Context. Finding pages that disagree uses a model, built-in AI or your own key; the rest needs none.

Ask and AI

Cited answers, built-in AI, your own key and search.

What is Ask?
Ask answers a question in plain words from your knowledgebase’s own pages. Each claim carries a numbered citation, and a Sources rail shows every cited passage with its page and who verified it. A trust line says how many of the pages it used are verified.
Who pays for Ask?
liveknowledge does: Ask runs on built-in AI, included, with daily limits. An Editor may add the team’s own Claude or OpenAI key in AI Settings, paid to that provider. Search, verification, import, export and the agent connection need no AI.
What are the built-in AI limits?
Built-in AI is Cloudflare Workers AI, paid for by liveknowledge: 30 questions a person a day, 100 a knowledgebase a day and 20 conflict checks a knowledgebase a day, with a drafted page counted as a question, and 10 Describe to Set Up suggestions a person a day. Once your team adds its own key, everything uses that instead. A server you run yourself has built-in AI only if it is set up with it.
Is my API key safe?
The key is sent once over TLS, encrypted before it is stored, and kept with that knowledgebase. It is never sent back to a browser: AI Settings shows only its last four characters, with Replace and Remove. It is never written to logs or telemetry.
What happens when the pages do not cover my question?
Ask says so instead of guessing. The part it could not answer is shown as a Knowledge Gap, recorded in AI Knowledge with how often it was asked, and an Editor can start a page from it.
Does search need AI?
No. Search is keyword search over your pages, split into passages, and it works for every role and in an Offline knowledgebase. Semantic search is not built.
Can someone with a share link use Ask?
Not anonymously. Ask is off for anonymous share links, because strangers would spend your team’s AI. People you share the knowledgebase with by name can ask, at any role.

Agents

The MCP server, the command line and what an agent may do.

Can I connect my own AI tool?
Yes. liveknowledge has an MCP server and a command line. Connect Claude, ChatGPT, Cursor, VS Code or any MCP client from Build with AI: one address, one approval, then your agent can read the knowledgebase.
What can an agent see?
Only what the person or token it acts for can open. Share roles apply to agents exactly as to people: a Viewer’s agent reads, and a Participant’s or an Editor’s agent can also suggest edits. A read-only connection never suggests.
Can an agent change a page?
By default an agent’s edit arrives as a suggestion with its reason, and a person accepts or dismisses it. Accepting applies it as one undo step and does not verify the page. An Editor can allow one connection to write, but a page that is Verified or Review Due is only ever changed by suggestion.
What does an agent get with a passage?
How far to trust it: whether the page is verified, when, whether its review is due, and any page it is known to disagree with. Reading a whole page also gives who verified it, its backlinks and its subpages.
Does liveknowledge train a model on my pages?
No. Ask sends your question and the passages it found to built-in AI (Cloudflare Workers AI, run by liveknowledge), or to Claude or OpenAI under your team’s own key if it added one. Describe to Set Up sends only what you describe, and the titles of pages already there. An agent you connect reads only what you let it.

Import and Export

Bringing pages in from elsewhere, and taking them out.

Can I import from Notion and Confluence?
Yes. In the editor’s Import dialog choose Notion (its Markdown and CSV export, a .zip), Confluence (a space’s HTML export, a .zip) or a folder of Markdown. You see the pages and pictures it found before anything is imported. Google Docs import is not built yet.
What comes across in an import?
The pages and their hierarchy, the links between them and their pictures. A Notion database’s CSV becomes a table on its page, Confluence’s info, note and warning boxes become quotes, and code blocks stay code. Other attachments are listed by name, because liveknowledge stores pictures only. Imported pages start unverified, with no owner.
How large an import can I make?
An archive up to 200 MB and 500 pages (the size of a knowledgebase), with pictures up to 10 MB each. The archive is read in your browser, and pages are written in batches, so a failed page is reported by name and the rest are kept.
How do I get my pages out?
A page exports to Markdown, PDF and Word, and also to PNG, SVG and JSON. The command line exports a whole knowledgebase as a folder of Markdown with relative links, so it can be kept beside a repository.

Sharing and Privacy

Roles, Offline, and what liveknowledge does not do yet.

How is a knowledgebase shared?
Like every liveworkspace item: by link or with named people, as Editor, Participant or Viewer. A Participant does everything an Editor does except the Review Period, Knowledgebase Style, AI Settings and who has access: it edits pages, changes the page tree, sets covers, verifies and imports. A Viewer reads, searches, asks and exports.
Can I restrict a single page?
No. Sharing is per knowledgebase, as it is for every liveworkspace app, and page-level permissions are not built. To keep some pages to fewer people, put them in a knowledgebase of their own.
Does liveknowledge work offline?
Yes. A knowledgebase kept Offline lives only in your browser, where it is written, searched and exported without an account. Verification, Ask, Describe to Set Up, AI Knowledge and sharing need the server, so they are not available for an Offline knowledgebase.
Can I publish a knowledgebase as a public website?
Not yet. You can share a view-only link, but a public site with its own domain is not built.
Is there a mobile app?
There is no native app. The editor runs in a phone’s browser and can be installed to the home screen.
What is tracked?
Anonymous, first-party counts of which features are used, sent to liveworkspace’s own telemetry service and listed publicly on /telemetry. No third-party analytics, no advertising pixels, and never the words you write.

Still Have a Question?