Why Muhkoo

Muhkoo Connect is a TypeScript SDK for building apps where the server is never trusted with user data. Authentication, storage, and messaging are all private by construction — yet you use them through one ergonomic client, the same way you’d use any BaaS.

The whole API is one object

const client = new Client({ apiKey, baseUrl });

client.auth      // ZK identity: register / login / sessions
client.kv        // per-user, encrypted-at-rest key/value
client.storage   // file storage (chunked, encrypted, erasure-coded)
client.message   // pub/sub + end-to-end-encrypted direct messages
client.space     // group Spaces: fan-out channels with persisted history
client.vfs       // your encrypted filesystem (with client.vcs for version control)
client.db        // the app's scalable database
client.agents    // Programmable Agents
client.functions // serverless functions

Everything hangs off client.<namespace>.<method>. There’s no separate auth SDK, storage SDK, and realtime SDK to wire together — one session flows through all of them. The Quickstart uses the first four.

What makes it different

• Zero-knowledge auth. A user’s identity descends from a random seed generated on their device and is proven with a Groth16 proof. The accelerator never receives a password: it stores a Poseidon commitment, plus copies of the seed wrapped under each login factor in a per-user vault. The same credentials unlock the same seed on any device, so login is federated. Password, passkey and recovery-phrase copies stay user-held, but Muhkoo could recover an account that has an email or Google factor (details).
• Encryption by default. client.kv values are sealed with AES-256-GCM under a key derived from the user’s identity before they ever leave the device. Direct messages use the Double Ratchet (the Signal protocol’s ratchet). The platform relays ciphertext.
• Edge-native. The backend runs on the edge, so state lives close to users globally and there’s nothing to operate.
• Metered + multi-tenant. Every app authenticates with an app key (mk_…) that attributes usage for billing. The API is public — your users’ apps can run on any origin.

When to use it

Reach for Muhkoo Connect when you’re building:

• private, user-owned data apps (notes, journals, health, finance);
• end-to-end-encrypted chat or collaboration;
• multi-device apps that need federated login with keys users hold themselves (password, passkey or recovery phrase);
• anything where “the vendor can read your users’ data” is a non-starter.

When not to

• You need full-text search or server-side queries over encrypted user data — client.kv and files can’t be queried on the server by design (see Storage). Data you put in the app’s scalable database is the place for server-side queries; choose per table what belongs there (choosing a primitive).
• You need the server to process plaintext (e.g. server-side AI over user content) — that breaks the trust model.

Ready? The Quickstart gets you from zero to a signed-in user reading and writing encrypted data in a few minutes.