Nodes and storage
The whole engine in one object: identity, storage, sync and encryption. The same node runs in a tab, a terminal, a server or an agent.
What it enables
- Minca in the browser, Node or Bun, with no server of your own
- Spaces kept online while devices sleep, by a host that can’t read them
- Data in IndexedDB, a folder the person picks, or S3 for files
- Scripts, servers and tests that hold an account’s keys themselves
In this section
- The node: A node is what takes part in Minca for an account. It holds the account's spaces, signs what it writes, checks what peers send, and keeps everything in sync. Most apps never make one: the…
- Sync and storage in the library: Where a node keeps its data, and how it syncs it. You rarely need this page to build an app. Read it to attach files to records, to know what a node keeps on a device, or to plug in storage of…
Node actions
Actions are the node's operations written down as data: a name, a description and an input schema for each. The CLI, MCP and WebMCP all build their tools from this one list, so an agent sees the…
The node
A node is what takes part in Minca for an account. It holds the account's spaces, signs what it writes, checks what peers send, and keeps everything in sync. Most apps never make one: the…