Home / Products

Apps

See it working. Then read the code.

Every demo below is a real app in the open-source repo, and the App Registry lists signed apps you can deploy.

Registryapps.calimero.network
my-app.mpkSigned
  • frontendsigned
  • app logicsigned
  • manifestversion · publisher
Sealed nodeverifies the bundle on install

01 · Collaborative editor

Two people, one document, no server code.

Two people edit one document at once. The document is one app instance, replicated across attested nodes, so every edit is applied in one order.

  • No database and no servers to run.
  • One order: concurrent edits are applied the same way on every node.
  • Plain text or rich text, both in the repo.
same document for both · one app instance, replicated

02 · TEE Dice and TEE Cards

Results nobody can rig, secrets nobody can peek at.

The roll and the deck live inside a sealed node. Each player checks that node's attestation before playing.

  • TEE Dice: a roll no player can rig.
  • TEE Cards: hidden hands no player can peek at or stack.
one roll · produced inside Intel TDX · checked by both players

03 · More demos

Each one proves something.

Every card links to the app's code in the open-source repo.

Access rules are enforced by every node

Permissions showcase

One team space, many write rules. Every node refuses a forbidden write.

Apps get real features, not a toy runtime

Search chat

A chat log with full-text search served by the node.

A dev cluster for development and testing

Local dev cluster

Run merod local, three nodes in one process, and point the SDK at it before you deploy to Calimero Cloud.

04 · App Registry

Signed apps, ready to deploy.

Chat, documents, spreadsheets, calendars, signatures, design and games, each signed by its maker.

  • Signed by their makers, logic and frontend together, as one .mpk.
  • One name, one signer: reverse-DNS names like com.acme.notes.
  • Verified by the node on install.
How the registry worksShow less

What you'll find

  • Chat
  • Documents
  • Spreadsheets
  • Calendars
  • Signatures
  • Design
  • Games

Each listing has the app's page, its versions and its links. Publishing your own from Calimero Cloud? A package can be public, or private: served only to the clusters your environments run on. For packages no other tenant can see, use a dedicated cluster.

  1. 01

    Signed by their makers

    Every package carries its maker's Ed25519 signature over its manifest, which covers the logic and the frontend.

  2. 02

    One name, one signer

    A package name is reverse-DNS, like com.acme.notes. The first publisher's signer is pinned, so a later version must come from the same key.

  3. 03

    Verified on install

    Every node that installs a version checks the maker's signature before the app runs.

Your customers want control. You want to ship.

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