Knowledgefor AI
Your company's verified knowledge, inside your AI.
Datashard gives your AI the facts your people have checked, and only the ones each person may see. Engineers never see project costs. The CEO sees everything.
How it works
Short, verified facts. Not a pile of documents.
Each fact is a few paragraphs about one thing, with an owner and the name of the person who vouched for it. Claude loads a brief once per chat and searches for the rest.
Verified by a person
Every fact records who checked it and when. A fact nobody verified says so, and Claude is told to treat it that way.
Access by role
Facts live in sections, and sections are granted to roles, from your identity provider's groups or by email. Admins change who sees what on the admin pages, and see who gains and who loses each section before they confirm.
Your own account
Each company gets its own install, in its own Cloudflare account, with its own sign-in. Facts are stored only there; there is no shared database.
companyPolicy
Expense claims
Claims go in within 30 days of the spend, with a receipt, through the finance tool.
Features
Everything your AI needs to answer from what your company knows.
Built for AI first: your assistant reads, searches and saves facts through MCP, the open standard for connecting AI assistants to tools. Claude and Grok Bot work with Datashard today. Every answer comes with the fact's owner and who verified it.
A brief per chat
Claude loads the key facts for the signed-in person once per chat, or when you pick "Brief me", and answers from them without searching again.
Search by meaning
Keyword and meaning search together, so a question in other words still finds the fact. Claude is told when a match was by meaning only.
Save from the chat
Ask Claude to save something. It shows you the exact text and section first, and saves only after your yes, with you as the verifier.
Never stale in a chat
Every answer carries the knowledge version, so Claude learns what changed since its brief and loads it again when it must.
Linked facts
Facts link to each other. A long topic becomes a short overview with linked parts, and search returns the family once.
See it as a graph
A search's results and the facts they link to, drawn on a page of their own. Each dot opens its fact and says who verified it, and when.
Full history
A fact is never edited in place: every version is kept with who saved it. A retired fact keeps its text and says it is retired.
Tags for everything
Facts are tagged with the systems, projects and topics they are about, so Claude can pull everything about one of them, page by page. A section can keep tags of its own, seen only by its readers.
A page for every fact
Each fact has its own web page, behind the same sign-in, with its verification, section, version and linked facts.
Whose knowledge it is
Sections are labelled by company, client and project, and every answer says whose knowledge a fact is. A save into one client's section is refused when it is about another client.
Your access on one page
Everyone has a page with their roles and where each one comes from, their sections, which they can save to, and where their reads are logged. It shows nothing about anyone else.
Admin pages
Admins change sections, roles, people and tags in the browser. Every change shows who gains and who loses each section before it is made, and can be changed back.
Reads logged
For sections you mark as sensitive, every read is recorded with who and when.
No secrets saved
Text that looks like a key, token or password is refused at save and at import, naming the problem, never the value.
Nightly backups
Your knowledge is backed up every night in your own account. A copy is kept only once it restores, and the month's copy only once it also answers the golden questions.
Short by design
A fact stays within 4,000 characters, so answers stay quick to read and cheap to send to Claude.
Import what you have
Load an existing set of Markdown notes in one step, with a dry run first that lists every change it would make. Each set loads only into its own section, and a wrong load can be hidden from every answer at once.
A Claude Code plugin
One install brings Datashard's tools and its save skill into Claude Code. A check before every save refuses one aimed at the wrong install.
Golden score
Search quality, measured on every deploy.
Most knowledge tools don't publish how often search finds the right answer. Datashard checks it every time it ships.
The golden rule
Each install keeps a set of real questions, each with the fact that answers it, asked two ways: in other words, and by keyword.
Every deploy asks them all. If too few answers land in the top 3, the deploy goes red. Ours fails below 80%.
Every change to search is measured on a copy of the install before it ships.
Answer in the top 3. Xibit Digital's own install, deploy of Oct 21, 2026.
Security
Sign in with what you already use.
Your AI signs in through Cloudflare Access, and every read goes through one tested layer that decides, fact by fact, what the person may see. Reads of sensitive sections are logged with who and when.
Contact
Talk to us about Datashard for your company.
Tell us about your company and the AI assistant your people use, and we'll answer from there.