Skip to content
Calimero CoreCalimero CoreCalimero Core

Calimero Core

Sandboxed WASM apps on a cluster of attested Intel TDX nodes. One Raft log per app, one for the cluster, every request sealed to an attested key — and nobody operating it can read the data.
Read the Protocol ReferenceView on GitHub

Build

Write a WASM app on the SDK. Quickstart, the SDK macros, and the collection types. Start building →

Run a cluster

Start a local cluster, deploy an app, and operate merod in production: the storage key, peers, governance and the Ops API. Calimero Cloud →

Protocol

How a cluster works and why: replication, the system group, attestation, sealed channels, accounts, organizations, upgrades. Read the reference →

Contribute

Work on Calimero core itself. Architecture orientation, the crate map, and the development workflow. Get oriented →

Architecture at a glance

Section titled “Architecture at a glance”
Clientmeroctl · mero-jsPython · Rust clientpasskey sessionor API keycluster: attested Intel TDX nodes (merod)every node holds the system group; an app's group lives on its replicas1 verify quote(release, profile)GET /attestation2 sealedrequestany nodeopens the envelopecredential + access onfresh system statesigns the receipt3 forwardpeer sealedchannelthe app's leader4 runs the WASM call, appends{ call, outcome { result, diff } }5 Raftfollowerapplies the difffollowerapplies the diffusually 3 replicas per app; nobody re-executes6 result + receipt(sealed)mero-kmskey for the cluster, only to anattested TD → storage key K_roperator (mdma)Ops API: counts, ids, Raft status;no read path into app data

A client verifies a node’s TDX attestation, then talks to any node through a sealed channel. That node checks the caller against the cluster’s system group and forwards the call to the app’s leader, which runs the WASM and replicates the result to the app’s other replicas. More in Calimero Cloud →

New here? How to use these docs · Journeys by goal · Browse by topic