Calimero Cloud
Fully managed nodes on Intel TDX confidential VMs. The fastest start.
Confidential compute, secure and easy to manage.
Write your app once and run it sealed on Calimero Cloud, on your own nodes when customers need it on premises, or peer to peer on devices people own. No enclaves, key policies or sealed databases to manage, and nobody, including us, can read data inside a sealed node.
Backed by
02 · The problem
Customers want their data on their terms. Delivering that usually means an on-prem edition, patching, secrets, backups, on-call and long security reviews, and the admins can still see everything.
03 · Why Calimero
Each cost of running it yourself has a direct answer.
Before: One bad dependency owns the box.
With Calimero: Apps run as sandboxed WebAssembly and only reach their own state through the node.
Before: Harden, rotate, pen test, repeat.
With Calimero: Read-only images with no SSH. Keys are released only to nodes that prove their image.
Before: Patches, backups, on-call.
With Calimero: Signed, versioned bundles. On Calimero Cloud we run the nodes and their upgrades.
Before: Admins and vendors can read it all.
With Calimero: Nobody, including us, can read data inside a sealed node. Storage is encrypted at rest.
Before: Self-hosted means provisioning.
With Calimero: Install a bundle, not a server.
04 · How it works
Bundle your Rust logic with its frontend into one signed package, install it, and every sealed node proves what it runs before it gets keys.
cargo mero bundle.cargo mero bundle --dev --no-icon logic · frontend · signed ✓ my-app.mpk meroctl --node node1 app install --path ./dist/com.example.my-app-0.1.0.mpk ✓ installed
Write your app logic in Rust and bundle it with its frontend into one signed package.
cargo mero bundleInstall it on Calimero Cloud or your own node; state syncs between nodes on its own.
Every sealed node proves which image it runs before it gets any keys.
05 · Where it runs
Our cloud, your nodes, the devices your users own, or all of them, connected as one app. One build serves SaaS, on-prem and people who want to keep their data.
Fully managed nodes on Intel TDX confidential VMs. The fastest start.
Run nodes on your own infrastructure for customers who need data on premises.
Your servers and Calimero Cloud nodes join the same app and stay in sync. One build serves SaaS and on-prem customers.
People run the app on their own node with Calimero Desktop, and it syncs directly between their devices and the people they invite. No server keeps a copy of their data, and they can add Calimero Cloud later to stay online while their computer sleeps.
06 · Products
The same signed app runs on sealed Cloud nodes or on a node you run yourself.
Sealed nodes on Intel TDX confidential VMs, run for you, with a console that shows what each node attested.
Explore CloudYour own node on your own machine. Own your data: apps run on your device and sync peer to peer. Also for development, testing and on-prem. macOS, Windows, Linux and Chromebook.
Get DesktopYour own AI agent, sealed in a confidential VM, on open-weight models it verifies, with plugins whose keys stay in Mero Pass.
Explore Confidential AIWorking demos with their code, and the App Registry of signed apps you install onto any node.
See the apps07 · Verify us
Before a sealed node gets any keys, it proves which image it booted, and the key service checks that proof against the published release policy.
Measurements published
Intel TDX, read-only image
Hardware attestation quote
Checks it against release policy
Data unlocked inside the node
08 · Platform
You write the logic; we bring the stack.
Your frontend is signed with the app and served by the node from the app's own address. No frontend host, no CDN.
Read moreThe same sealed app on every node, its data split into contexts across the fleet. No central database to seal.
Read moreApp upgrades don't change node measurements or keys. One operation upgrades the app on every node.
Read moreWhy not just put your stack in a TEE?
Compare DIY in TEEs09 · Use cases
10 · Open source
The node, the SDK and the protocol are on GitHub, with a full protocol reference you could reimplement a node from.
Start on Calimero Cloud, or build on the open-source runtime.