Operate a Calimero Cluster

A cluster is a set of merod nodes. In production each runs in an attested Intel TDX VM, takes its storage key from mero-kms, and holds the replicas of the apps placed on it; one Raft log per app keeps the replicas identical, and one system log holds accounts, organizations, packages and the fleet. You drive it with meroctl, and the operator’s side goes through the Ops API with an ops token, which reports counts and placement and never reads app data.

New to Calimero? Read the Cloud overview first, then the Quickstart.

Start here

1. Install & first run: build, start a development cluster, connect meroctl.
2. Production deployment: storage key, forming the cluster, governance, what goes in front.
3. Security and Observability before you put data on it.
4. Keep the runbooks and troubleshooting at hand.

Guides

Production deploymentTDX nodes, mero-kms, forming the cluster, TLS in front.

NetworkingThe listener, peer URLs, CORS, app frontend domains, egress.

SecurityTDX versus --dev, quote policies, governance, the ops token.

ObservabilityOps metrics, status, health and logs.

RunbooksAdd nodes, move replicas, back up, upgrade.

TroubleshootingError, cause, fix.

Reference

merodEvery node command and flag.

meroctlEvery CLI command.

Configurationconfig.toml and the [outbound] table.

Node APIEvery route, its credential and its meroctl command.

AuthenticationPasskeys, sessions, API keys, confirmations, the ops token.