Home / Developers
Developers · Confidential apps
Build on Calimero. Write the logic.
Build a confidential app: write its logic in Rust, bundle it with its frontend into one signed package, and run it on Calimero Cloud: on shared clusters, paying per request, or on a dedicated cluster of your own.
#[app::state] pub struct KvStore { items: UnorderedMap<String, LwwRegister<String>>, } #[app::logic] impl KvStore { pub fn set(&mut self, key: String, value: String) -> app::Result<()> { self.items.insert(key, value.into())?; Ok(()) } }
Replicated across attested nodes. No server code.
- 1command for a three-node dev cluster:
merod local - 1signed package: logic and frontend together
- 9open-source tools and libraries
- 3client libraries: JavaScript, Python, Rust
01 · Quickstart
From an empty folder to a running app.
Build the example app into a component, start a local dev cluster and sign in with a development passkey. Then create an app instance and call it. Deploy signs the same build into a package for Calimero Cloud.
git clone https://github.com/calimero-network/core && cd core rustup target add wasm32-wasip2 curl -fsSL https://raw.githubusercontent.com/calimero-network/core/master/scripts/install.sh | sh -s -- merod meroctl meroctl app build apps/kv-store --out kv_store.wasm meroctl local up meroctl login --dev-passkey ./dev-passkey.json --name dev meroctl instance create --path kv_store.wasm --name my-kv --alias my-kv meroctl call -i my-kv set --args '{"key":"a","value":"1"}'
meroctl app signer new my-key.json meroctl app pack --wasm kv_store.wasm --package com.example.kv \ --app-version 0.1.0 --key my-key.json --out dist/com.example.kv-0.1.0.mpk # In the Cloud console: publish dist/com.example.kv-0.1.0.mpk, # deploy it to staging, promote it to production, create an API key. export CALIMERO_API_KEY=cal_... CALIMERO_TEE_PROFILES=locked-read-only meroctl node add prod https://<your-cluster>/ meroctl attest app <instance> meroctl call -i <instance> get --args '{"key":"a"}' --view
Calimero Cloud runs signed packages only. Publish them to Calimero's registry from the console, public or private; every node that runs one checks the publisher's signature. Raw WASM uploads are for local dev clusters. Against Calimero Cloud, meroctl takes an API key and the node images you trust, and checks each node's attestation before it sends anything. Upgrades are confirmed with the owner's passkey.
meroctl's names: app is a signed package, instance an app instance, namespace an organization and group one of its teams.
02 · Tools and SDKs
Everything you need, one install away.
The node, the command-line tools, the app SDK and the clients. Each is open source.
Node & CLI
Develop and test locally.
-
merodThe node.
merod localruns a three-node development cluster with mock attestation. On macOS, run it in Docker.curl -fsSL https://raw.githubusercontent.com/calimero-network/core/master/scripts/install.sh | sh -s -- merod meroctl -
meroctlThe one command line: start, build, sign and publish an app, run a local dev cluster around it, write typed clients from its ABI, and install packages, create app instances, call them, watch events and operate a cluster from the terminal.
curl -fsSL https://raw.githubusercontent.com/calimero-network/core/master/scripts/install.sh | sh
All tools and libraries: app SDK, clients, examplesShow less
App SDK
Write the app.
-
calimero-sdkWrite app logic in Rust, built for
wasm32-wasip2into acalimero:appcomponent.cargo add --git https://github.com/calimero-network/core calimero-sdk
Clients
Talk to a node from your code.
-
calimero-clientRust client: verifies a node's attestation, then seals every request.
meroctland the Python client are built on it.cargo add --git https://github.com/calimero-network/core calimero-client -
calimero-client-pyPython client for Calimero 1.0:
Client, with passkey and API key sign-in.pip install calimero-client-py -
mero-jsJavaScript client for Calimero 1.0, version 33:
CalimeroClient, with passkey sign-in, for the browser and Node.npm install @calimero-network/mero-js
03 · Calimero MCP
Let any agent drive your apps.
Any agent, local, deployed or from a frontier lab, gets its own scoped API key, so the Calimero MCP can drive your apps under each app's rules. Coding agents such as Claude Code, Cursor and Codex CLI included.
- Its own key, separate from yours, revocable any time.
- The app's rules apply to the agent like any other member.
- Sensitive methods can require a person's fresh passkey confirmation.
04 · Docs and open source
The runtime is open source.
The node, the SDK and the protocol are on GitHub, with a full protocol reference you could reimplement a node from. The docs come in four tracks.
- Stars
- Latest release
- Docs
- Build · Operate · Protocol · Contribute
05 · Showcase
Learn from working apps.
A collaborative editor, sealed dice and cards, a permissions demo and a searchable chat, each a real app in the repo with its code.
- Products
Apps
Six demos with their code, and the App Registry of signed apps.
See the demos - Docs
Examples
Every example app in the core repo, explained.
Read the examples - Platform
How it works
What every node brings so your app doesn't have to: runtime, replicated state, storage, networking and keys.
Read how it works
Your customers want control. You want to ship.
Start on Calimero Cloud, or build on the open-source runtime.