Get Started
Add the package, point CalimeroClient at a node, sign in with a passkey
and call an app. Quickstart →
Get Started
Add the package, point CalimeroClient at a node, sign in with a passkey
and call an app. Quickstart →
Sign-in
Passkeys, sessions and refresh tokens, failover between nodes. Authentication →
Guides
Calls, views and events; orgs, teams and invites; the consent page; the
app layer (MeroAppSession). Calls and events →
Reference
Every CalimeroClient method and every typed error.
CalimeroClient →
MeroKit never runs a node. A Calimero 1.0 cluster is a set of attested TDX
nodes; each app instance is one replicated log on them. MeroKit is the Swift
port of mero-js’s
CalimeroClient: the same methods, the same errors, the same retry and
failover rules.
| Layer | What it is |
|---|---|
MeroKitUI.MeroAppSession |
An app’s signed-in account and its MeroAppBackend (orgs, teams, app instances, invites, events). |
MeroKitUI.MeroClient |
The observable session: sign-in, restore, sign-out, the consent page. |
MeroKit.CalimeroClient |
Every node route, typed errors, refresh and failover. |
MeroKit.SealedTransport |
Noise NK to the attested transport key (calimero/sealed-http/v2), sealed frames. |
MeroKit TEE trust |
Mock or real quotes: signed mero-tee releases (Sigstore), DCAP against Intel’s collateral. |