Skip to content

Journeys by goal

Each journey threads pages across tracks in the order that gets you to a goal. Follow one top to bottom.

  1. Quickstart — a local cluster, an app, a call from the CLI and from code.
  2. Build your first app — state, methods, build, call.
  3. Writing apps for a cluster — what a cluster changes: identity, organizations, teams, handlers, timers, outbound.
  4. Collections — the state types your app is built from.
  5. Emit & handle events and call another app.
  6. Packaging & signing — ship a signed release; migrations for the next one.
  1. Calimero Cloud — what runs where, and the trust model in one page.
  2. Operating a cluster — the storage key, peers, governance, the Ops API.
  3. Deployment governance — decide who approves images, app upgrades and outbound hosts before the first start.
  4. The operator & the Ops API — what you can do, and what you deliberately cannot.
  5. Replication — joining nodes, replica moves, snapshots, failover.
  6. The merod and meroctl references.
  1. Protocol overview — the one idea everything hangs on.
  2. The model: Concepts → The system group → Replication.
  3. The call path: Execution → The write path → Reads, views & events.
  4. Trust: Networking & sealed channels → Attestation & receipts → Encryption → Security & threat model.
  5. People: Accounts & sessions → Who a run acts as → Organizations & teams.
  6. Look things up: Storage schema, Limits, Glossary.
  1. Attestation & receipts — the quote, the measurement policy, verify_app_cluster.
  2. Deployment governance — what the attested governance tells a user.
  3. Encryption — the storage key from mero-kms and what an observer still sees.
  4. Security & threat model — including what is not protected yet.