The knowledge
maintaining machine
Add your files. Corpus sorts them out, writes simple pages for your team and keeps them up to date.
No card needed
Built with NVIDIA NemotronPowered by
Token Factory
Free and open source
Use cases
For knowledge that keeps changing
Self-maintaining docs
Handbooks, policies and project pages that update when a new file changes the rules.
Your life's wiki
Notes, chats, lectures, plans, workouts and friends, sorted into one wiki about you.
Client tracking
Every client's details, deal stage and last talk, kept current from emails and calls.
Learning a big subject
Long books become linked, sourced pages in minutes.
Memory for AI agents
One sourced memory your AI tools read and write over MCP.
Maintaining knowledge is HARD.
So, we do it for you.
How it works
From long PDFs to clear facts.
Every page is read, pictures included. Each fact comes out short, with its source.
Self-maintaining
We turn knowledge into pages that rewrite themselves.
A new file arrives. Only the sentences it changes are rewritten, each with its source.
Multi-modal
Transform your knowledge into any type of resource.
The same sourced facts become wiki pages, videos, quizzes, slides, podcasts and agent context.
You stay in charge
Knowledge you can trust and check
Every line has a source
Every sentence links to the file and the page it came from.
Risky changes wait for you
Safe updates apply on their own. Conflicts and deletions wait for a person.
Undo anything
Every change is recorded with its cause and can be reversed.
One answer, not ten versions
Matching facts merge into one, and every source stays attached.
For AI agents
One memory for every agent.
Connect your AI tools through MCP. They read sourced, current facts and remember what you teach them, across every session.
For builders
Just build. Docs write themselves.
While you work with your coding agent, every feature, endpoint and decision is documented in the background.
Glossary
Your team's glossary, written by your files.
Every term your documents use, defined in plain words, with real examples from your sources.
Stakeholders
Know who matters, and why.
Every person and organization in your files, how they connect and how much say they have. Kept current.
Questions
What files can I upload?
PDF, Word and Markdown files. Each one is kept as evidence, so you can always open the original.
What is a claim?
One fact, rule or decision taken from a document, small enough to stand on its own. Every claim keeps a link to the page it came from.
What happens when I upload a newer version?
Corpus Wiki compares it with what it already knows and drafts changes to the claims it affects. Safe changes apply in one step. Others wait for a person. Only the lines that changed are rewritten.
Can the AI change my wiki without me knowing?
No. Every change is recorded with its cause, and old versions are never overwritten. You can see what changed, why, and which document triggered it.
What if two documents disagree?
The conflict stays visible. Both claims stay linked to their sources until someone decides which one holds.
Can I share the wiki outside my team?
Yes. You can publish a read only version of a space and share the link or embed it on your site.
How much does it cost?
Free costs nothing and needs no card: 300 credits a week. Paid plans are Plus $9, Pro $24, Max $79 a month, and Team is $15 per seat (3 seats minimum). Plus and Pro cost two months less when paid yearly. Every plan has a weekly limit and a 5-hour limit, measured in credits.
Where is my data stored?
Your account, the claims and pages built from your files, and the original files themselves are stored with Supabase. Originals sit in private storage and are kept as evidence for the claims that cite them. To read your files and write claims, text is sent to Nebius Token Factory, or to Anthropic when you pick a Claude model. You can ask us to delete your account and everything in it at any time.