Start on Cloud

Confidential compute, secure and easy to manage.

Ship the app. Skip the infrastructure.

Write your app once and run it sealed on Calimero Cloud: on shared clusters, paying per request with a free allowance every month, or on a dedicated cluster of your own. No enclaves, key policies or sealed databases to manage, and nobody, including us, can read data inside a sealed node.

Start on Calimero Cloud How it works
One buildShared or dedicated
One signed app package, running on Calimero Cloud's shared clusters or on a dedicated cluster A signed package named my-app.mpk connects to Calimero Cloud's shared clusters, paid per request and marked sealed and verified, and to a dedicated cluster run by Calimero for you alone. A connector between the two says they run the same attested nodes. SIGNED PACKAGE my-app.mpk ├ frontend├ app logic└ signature ✓ Calimero Cloud shared · pay per request ✓ SEALED · VERIFIED Dedicated yours alone · run by us ONLY YOURS same attested nodes

Backed by

  • Khosla Ventures
  • NEAR
  • GSR Ventures
  • FJ Labs
  • Eniac
  • Hypersphere
  • Lyrik
  • Daedalus
  • Warburg Serres
  • Metaweb Ventures

02 · The problem

Today, control means hosting.

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.

  • No servers to run on Calimero Cloud.
  • Nobody, including us, can read data inside a sealed node.
  • Every node proves which image it runs.
See the comparisonShow less

Self-hosting

  • Ship and support an on-prem edition
  • Patch the OS and dependencies
  • Manage secrets
  • Configure backups
  • Staff on-call
  • Sit through long security reviews
  • Admins and vendors can still see the data

Calimero

my-app.mpkfrontend and app logic, signed
  • You run no servers on Calimero Cloud
  • Nobody, including us, can read data inside a sealed node
  • Every node proves which image it runs

03 · Why Calimero

Everything self-hosting asks of you, handled.

Each cost of running it yourself has a direct answer.

  • Sandbox

    Before: One bad dependency owns the box.

    With Calimero: Apps run as sandboxed WebAssembly and only reach their own state through the node.

  • Security

    Before: Harden, rotate, pen test, repeat.

    With Calimero: Read-only images with no SSH. Keys are released only to nodes that prove their image.

  • Maintenance

    Before: Patches, backups, on-call.

    With Calimero: Signed, versioned bundles. On Calimero Cloud we run the nodes and their upgrades.

  • Privacy

    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.

  • Serverless

    Before: Self-hosted means provisioning.

    With Calimero: Install a bundle, not a server.

04 · How it works

Build. Deploy. Verify.

Bundle your Rust logic with its frontend into one signed package, deploy it, and every sealed node proves what it runs before it gets keys.

  • Build one signed bundle with cargo mero bundle.
  • Deploy to Calimero Cloud; each app instance is replicated across attested nodes.
  • Verify every sealed node attests before it gets any keys.
How it worksRead the quickstart
terminal
$ cargo mero bundle --key my-key.json
$ meroctl app install --path dist/com.example.my-app-0.1.0.mpk
$ meroctl context create --package com.example.my-app --name my-app --alias my-app
$ meroctl call -c my-app set --args '{"key":"a","value":"1"}'
The three stepsShow less

  1. Build

    Write your app logic in Rust and bundle it with its frontend into one signed package.

    cargo mero bundle

  2. Deploy

    Publish the signed package to Calimero's registry, public or private, and deploy it from the Cloud console to staging, then production. Every node that runs it checks the publisher's signature, and each app instance is replicated across three attested nodes.

  3. Verify

    Every sealed node proves which image it runs before it gets any keys.

05 · Where it runs

Write once. Run it sealed.

Calimero's shared clusters, or a dedicated cluster of the same attested nodes for your apps alone. One build runs on both.

  • Shared clusters of sealed Intel TDX nodes, run by Calimero. Pay per request.
  • A dedicated cluster of the same attested nodes, for your apps alone. A flat monthly fee.
  • Replicated across attested nodes, so an app keeps serving when a node is lost.
Compare the optionsShow less
Available

Calimero Cloud

Shared clusters of attested nodes on Intel TDX confidential VMs, run by Calimero. The fastest start: pay per request, with a free allowance every month.

Available

Dedicated clusters

Three nodes of the same attested image for your apps only, provisioned and run by Calimero, at $1,200 a month.

Replicated, strongly consistent

Each app instance is replicated by its own Raft log across three or more attested nodes in a cluster. Calls are applied in one order, reads can be strong, and the app keeps serving when a node is lost. The same build runs on shared and dedicated clusters.

Explore Calimero CloudRun a local dev cluster

06 · Products

Run it on Cloud. Build it with our SDKs.

The same signed app runs on sealed Cloud nodes or on a dedicated cluster of your own.

07 · Verify us

Don't trust us. 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.

  • Read-only images with no SSH, no serial console and no rescue shell.
  • Keys only to nodes whose quote matches the signed release.
  • Open-source verifier so you can check a node yourself.
How we prove itVerify a node
The five checksShow less

  1. Signed release

    Measurements published

  2. Node boots

    Intel TDX, read-only image

  3. Node proves

    Hardware attestation quote

  4. Key service

    Checks it against release policy

  5. Keys released

    Data unlocked inside the node

08 · Platform

One attested node, every layer built in.

You write the logic; we bring the stack.

Why not just put your stack in a TEE?

Compare DIY in TEEs

09 · Use cases

Built for teams whose customers ask hard questions.

All use casesTalk to us

10 · 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.

View on GitHubDevelopers
  • GitHub stars on core
  • latest core release

Your customers want control. You want to ship.

Start on Calimero Cloud, or build on the open-source runtime.

Start on Calimero Cloud Talk to us View on GitHub