Skip to content
Calimero Calimero Docs

The Calimero ecosystem

Calimero is a stack, not a single app. At the center is the node; everything else exists to help you build against it, run it, or ship apps to it.

The node — merod

Section titled “The node — merod”

merod is the runtime. It executes your WASM app, stores CRDT state, tracks the causal DAG, and syncs with peers over libp2p. A node can host many contexts for many apps at once. Everything below talks to a node, or runs inside one.

Nodes What a node does and how it participates in contexts.
Core reference The runtime, node operation, CLI, and full protocol.

The SDK family

Section titled “The SDK family”

Two kinds of SDK, depending on which side of the node you're on:

  • App SDK (Rust) — for writing the WASM app itself. Ships in Core; declares state as CRDT collections and exposes views, mutations, and events. See the Builder Directory.
  • Client SDKs — thin clients that talk to a node's API from an app's frontend or a script. They authenticate, call methods over JSON-RPC, and stream events. Pick your language:
mero.js Pure-JavaScript client — browser, Node, Deno, Bun, edge. Zero dependencies.
calimero-client-py Python client over a native Rust core (PyO3). Great for scripts and automation.
mero-kotlin Native Kotlin client for Android, with optional Jetpack Compose UI.
MeroKit (Swift) Native Swift client for iOS/macOS, with optional SwiftUI components.
mero-devtools-js Generate a fully-typed TypeScript client from an app's ABI.

The client catalog and how to choose live in Client SDKs.

Calimero Cloud

Section titled “Calimero Cloud”

Not everyone wants to run infrastructure. Calimero Cloud provides managed nodes so you get a reachable, always-on node without operating servers — with single sign-on, plans, and one-time join keys for onboarding members.

The important part: a managed node still can't read your data. Cloud nodes run inside a Trusted Execution Environment, and the key-management service only releases a node's storage key when hardware attestation proves the node is running an approved build. The operator hosts the machine; they never hold the keys to what's inside it.

Calimero Cloud & MDMA Managed, TEE-backed nodes — dashboard, plans, and operator architecture.
TEE: attestation & KMS How a node proves what code it runs before a key is released.

Calimero Desktop

Section titled “Calimero Desktop”

Calimero Desktop brings a node and apps to the desktop as a native application (macOS, Windows, Linux), so end users can run Calimero apps without touching a terminal.

Desktop The native desktop app — what it is and how it works.

Apps Registry

Section titled “Apps Registry”

The Apps Registry is where WASM apps are published and discovered. Apps ship as signed bundles; the registry validates the signature on upload and nodes re-verify it on install — so what runs is exactly what the author published.

App Directory & Registry Publish, discover, and manage signed WASM app bundles.

Where to go next

Section titled “Where to go next”

| You want to… | Go to | | --- | --- | | Understand the design | Architecture | | Write an app | Builder Directory | | Add Calimero to a frontend | Client SDKs | | Run or host a node | Operate Nodes · Calimero Cloud | | See how it compares | How Calimero compares |