1 · Publish
You choose the subject and the audience
Keep it private to chosen tenants, or list it in the public registry for anyone to subscribe to.
Product · Knowledge Sharing Network
Knowledge you can share without handing over a copy.
The Knowledge Sharing Network lets you publish what you know so other people, teams and AI apps can ask questions of it. They get exact answers from your live knowledge, and never a file to keep.
What it is
Publish once. Others subscribe and ask.
Sharing works like following someone. You publish a subject, such as a product manual, a regulatory update or a research dataset. Other tenants subscribe to it, or you grant specific people access, and from then on they can ask questions of it in chat, in Claude or ChatGPT through MCP, or from their own app. You stay the owner, and they always know whose knowledge they are querying.
2 · Subscribe
They add it to their memory
The shared subject appears next to their own data. Nothing is copied, and access is never automatic.
3 · Ask
Exact answers from your live knowledge
Questions return the stored value, with its source. When you update or revoke, the next question reflects it.
Why it's needed
Sending files is how knowledge goes stale and out of your control.
Teams and companies share knowledge by emailing PDFs, spreadsheets and links. That breaks down as soon as the knowledge changes, or when the people who need it are AI assistants rather than readers.
| Sharing files | Knowledge Sharing Network | |
|---|---|---|
| Staying current | Every recipient holds a copy that goes stale the day you change something | Everyone queries one live subject; update it once |
| Control | Once sent, a file cannot be taken back | Revoke access and the next question no longer sees it |
| Using it | The recipient has to open it and read it | They ask in plain language, or their AI app asks, and get the exact value |
| Ownership | Copies spread and nobody knows who holds which version | You stay the owner, and subscribers see whose knowledge they are querying |
The answers are exact because shared knowledge is filed in M.N.E.M.O.'s memory, an organised structure called an Omni Axis Tree (OAT). Asking for something goes to where it is filed instead of searching for something similar, so a subscriber gets the same exact answer the owner would. See how it works.
How it works
Private, public, or by subscription.
Private sharing
Grant a specific tenant access to a subject. They accept, and it appears in their memory next to their own data. You can revoke it at any time, and the next question they ask no longer sees it. Use it for clients, partners, collaborators or your own team's tenants.
Public sharing
List a subject in the public registry and anyone can browse and subscribe. Public listings are screened for illegal content before they go live. Use it for documentation, reference material and anything you want the world to be able to ask about.
Subscribe like you'd follow a person
Subscribers query shared knowledge through chat or through their own app. Subscribe to several publishers and ask one question across all of them from one ongoing relationship, not a pile of links.
You stay in control
Publishers own their data and choose the audience. M.N.E.M.O. is the access layer, not the source of truth. Subscribe-only use is available on every plan; publishing and private sharing are on Standard and above.
Availability
Private sharing is live today. Public registry publishing is being rolled out.Subscribing to what others share, and sharing privately with chosen tenants, work now. Opening publishing to the public registry is being enabled in stages while the supporting policies are put in place.
In real life
What people use it for
Illustrative scenarios, not customer stories.
A law firm briefs its clients
The firm keeps a subject of regulatory changes and shares it privately with each client. Clients ask, "What changed in the filing rules this quarter that affects us?" and get the firm's own answer, without the firm emailing a PDF every month. When an engagement ends, the firm revokes access.
A software company publishes its product knowledge
Release notes, limits and configuration guides go into one subject that customers subscribe to. Customers ask questions in chat, and their own tools can query it too, so everyone works from the current version, not a stale copy.
A research lab shares a dataset with collaborators
Instead of mailing spreadsheets between institutions, the lab grants partner labs access to the results subject. Partners ask for exact values and aggregates, and everyone sees the same numbers.
A franchise head office keeps every location aligned
Policies, pricing rules and procedures are published once. Each franchisee subscribes, and a manager can ask, "What is the refund window for gift cards?" and get the head office's current rule, with no old binder in sight.
Same memory, other doors
Everything here reads the same memory.
Whatever this feature can see, the other two can see too, so you can add them later without re-uploading anything.
AI chatbot
Ask your own knowledge in plain language.
Learn more →MnemoRAG
One stateless call from your own pipeline.
Learn more →Next step
Choose a plan, or talk with Panaxon AI about your use case.