You
Your data. Your keys. Your rules.
- Your data
- Your keys
- Your rules
Mycelium
Mycelium connects independent organizations in one network. The sender decides what may leave, the receiver decides what it accepts, the stricter policy wins, and every transaction is decided before the key is released.
Existing users:Sign in to the console
No account yet?Request Early AccessJoin the Developer Beta
On supported paths and deployments, the connection works without exposing the protected information, without taking control of the keys, and with cryptographic proof of every protected release.Holds on the paths and deployments where the architecture guarantees it.
The Capsule is the technology: it travels with the information and decides every opening. Mycelium is how you reach it.
On a Mycelium connection only sealed messages pass through the middle. NoData sees who sent to whom, when, and the size, not the content.
The key that opens what a side receives is made and kept on its own device. NoData does not hold it.
Every opening leaves a signed receipt on each side’s own record.
An API decides how systems talk. NoData decides what may pass between them.
| An API | NoData | |
|---|---|---|
| The owner controls | What the service allows, set in the endpoint’s code | What the information’s owner allows, per partner and per command |
| The policy travels | The receiver gets what the endpoint returns | The receiver gets only what the owner allowed, and refuses what it did not agree to receive |
| No content seen, no key held | An integration layer in the middle sees the content | Only locked information passes in the middle. We see who sent to whom, when and the size |
| Proof on both sides | Each side keeps its own internal logs | A signed receipt for both sides, which a third party can check |
| Connect and disconnect | A technical connection; revoking stops future calls | A connection is an agreement: invitation, consent, expiry, receipts. Disconnecting also stops what is still waiting |
Nothing runs card to card. Every request passes the hub, and both sides’ rules decide it: the stricter one wins.
Your data. Your keys. Your rules.
Their data. Their keys. Their rules.
Its data. Its keys. Its rules.
Pick one. The console opens on it.
Invite a partner with one link. Their agent asks, yours answers, only within what both boards allow.
Say to Claude: Invite our partner to connectRun a client’s work with their keys, without receiving them. They see each use and can switch you off.
Say to Claude:I need my client’s API keys for this projectConnect by the other agent’s address. Closed by default, with an expiry.
Say to Claude:Connect to the agent at address <their 16-character address>nodata_partner accept <link>Scan this folder before the agent gets itAdd "Project Orion" as a confidential termMake a clean copy of this folder for the agentClean this proposal.docx and keep it a Word fileBlack out the word "children" in this scanned letterLock the originals in this folderSend the clean brief to 4f2a9c1e7b30d815Send this file as a link, 24 hours, view onlyExpose this folder to my partner, clean view, for a weekInvite my vendor to connectDeliver the final film to the client, burn after viewingRun the build with my project secretsI need my client’s API keys for this projectGive the reporting agent read access to orders, no customer columnsShow my proofs from todayWhich of my files did the vendor’s last job use?Invite, accept, send and open with nd.fabric. Sealed on your side.
Available today
nd.fabric in @nodatachat/sdk 2.1.0: open, invite, accept, partners, send, reply, inbox, disconnect.
Planned
npm i @nodatachat/sdk@2.1.0npx -y @nodatachat/mcp@latest setupnodata_get_startedChecks this computer and says the next stepreads onlynodata_connectConnects this computer to your organisation, one approval in the browseraddsnodata_termsShows or accepts NoData’s termsaddsnodata_nodeRegisters this computer as a node of the organisationaddsnodata_scan_folderScans a folder for sensitive data, counts onlyreads onlynodata_scan_termsSets your own words that make a file sensitiveasks you firstnodata_scan_feedbackReports a wrong scan resultaddsnodata_clean_folderBuilds a verified clean folder next to yoursaddsnodata_redactMakes a clean copy of one file, in the same formataddsnodata_protectSeals files on this computerasks you firstnodata_openOpens a sealed file, next to itaddsnodata_wrapSeals files to the organisation’s keyasks you firstnodata_planRecommends and applies a policy for a folderasks you firstnodata_rulesSets what agents may do with filesasks you firstnodata_chooseChooses, per kind of detail, what crosses from a folder; the owner approves it as policyaddsnodata_policyShows the agent policy boardreads onlynodata_seal_revokeRevokes a sealed file for everyoneasks you firstnodata_sendSends a file as a governed link, or straight to a partner’s computeraddsnodata_deliverCreates a burn-after-read linkaddsnodata_inboxManages this computer’s inbox and who may reach itasks you firstnodata_exposeLets a partner’s computer ask for files, clean copies onlyaddsnodata_partnerInvites and works with a connected organisation: commands, not filesaddsnodata_prepareFrom Claude: prepares an invitation or a vendor policy as a link you approve in the browserreads onlynodata_connect_sourceConnects a data sourceaddsnodata_runRuns a command with vault secrets in memory onlyasks you firstnodata_register_tableRegisters a table for agent accessaddsnodata_grantGrants an agent access to the allowed columns onlyaddsnodata_revokeRevokes an agent’s accessasks you firstnodata_decideAsks whether an agent may reach a resourcereads onlynodata_retrieveRetrieves the context an agent may seereads onlynodata_readReads governed data within a grantreads onlynodata_api_listLists the organisation’s governed APIsreads onlynodata_api_readReads from a governed API, with an hourly and daily capreads onlynodata_api_writeWrites to a governed APIasks you firstnodata_useInvokes a registered capabilityasks you firstnodata_proofsLists the organisation’s proofsreads onlynodata_evidenceLists field access eventsreads onlynodata_link_statusChecks the links you sent: opens so far, expiry, burned or notreads onlynodata_burnBurns a sent link, at onceasks you firstnodata_code_adviseAdvice on a code capsulereads onlynodata_code_patchSubmits a signed patch to a code capsuleasks you firstnodata_encryptEncrypts a value (legacy)reads onlynodata_decryptDecrypts a value (legacy)reads onlyimport { NoData } from '@nodatachat/sdk';
const nd = new NoData({ apiKey: process.env.NODATA_API_KEY });
const fabric = await nd.fabric.open({ secret: process.env.NODATA_FABRIC_SECRET });
// Organization A: send this link to B
const { url } = await fabric.invite({ note: 'Acme orders' });
// Organization B: accept, then send a command
const acme = await fabric.accept(url);
await fabric.send(acme, 'order.create', { sku: 'A-17', qty: 3 });
// Organization A: open it here
for (const m of await fabric.inbox()) await fabric.reply(m, 'order.ack', { ok: true });One request, one decision, one proof. Six capabilities on one engine.
What an AI agent can read in a folder, in your browser.
Every request computed against policy.
A file sealed so it opens only under its own policy.
Proof on every opening, checked without NoData.
Who opens what, and a person who revokes.
Any MCP agent, REST and SDK, Microsoft 365 and Google Drive.
| Category | The link they touch | What they leave open |
|---|---|---|
| Enterprise AI · Copilot, ChatGPT Enterprise, Gemini | give the model access | the vendor sees your data and holds the keys. |
| Search & RAG · Glean, Pinecone, Elastic | retrieve context | the store sees the data. No policy gate, no selective key release, no proof. |
| DLP · Purview, Forcepoint, Zscaler | stop leaks | they read your data themselves and block bluntly. No per-request decision, no proof. |
| Identity · Okta, Entra ID, Ping | who signs in | not what the AI sees per request. |
| Audit · Splunk, Microsoft Sentinel | log it | after the fact. Does not prevent. |
Connections, Capsules and proofs are live. Early access lets in the first organizations and developers.
Existing users:Sign in to the console