Private by default
MeshKit encrypts data before it leaves the app and keeps provider bytes opaque.
Encrypted. IPFS-ready. Developer-first.
The encrypted storage SDK for modern applications
MeshKit gives web, mobile, server, CLI, and agent workflows one secure model for encrypted app storage, content addressing, proof metadata, sharing, and production provider boundaries.
End-to-end encryptedCID and proof awareMulti-runtimeAgent ready
A storage layer that explains itself
The docs route developers from first write to production decisions without hiding the hard boundaries: metadata, providers, runtimes, identities, and revocation.
Content addressed
Store encrypted envelopes, keep CIDs, and verify proof metadata across providers.
Runtime everywhere
Use one product model across Node, browser, React Native, Ionic, CLI, and agents.
Provider ready
Move from local-dev into IPFS, Kubo, gateways, Filecoin bridges, and policy services.
First win in minutes
Start with the SDK facade, store encrypted content locally, inspect the returned CID, then move into provider setup when you need production evidence.
import { meshkit } from "@meshkit/meshkit"
const mesh = await meshkit()
const file = await mesh.files.put("notes/intro.txt", "hello mesh")
console.log(file.cid)Choose your path
Jump into the documentation by intent: build, understand, configure, operate, or expose MeshKit to tools.
Getting Started
Install the SDK, store the first encrypted object, and learn the mental model.
Guides
Files, records, sharing, streaming, sync, providers, runtimes, and production setup.
Reference
Exact APIs, configuration fields, public types, and error handling contracts.
Tools
Operate MeshKit from the CLI and expose narrow, auditable tools to MCP agents.