Start on Cloud

Home / Platform

Use cases

Built for teams whose customers ask hard questions.

On-prem demands, data residency, security reviews, partners who won't hand over their data. Four places Calimero takes the operations off your plate.

Talk to us about your use case How it works

Use cases on this page

01 · On-prem edition

An on-prem edition without the on-prem work.

One build serves SaaS and on-prem customers.

  • Same signed bundle on Calimero Cloud and on your customer's nodes.
  • Connected: their nodes and Cloud nodes join one app and stay in sync.
  • One upgrade operation reaches every node in the group.
One buildtwo editions
my-app.mpkone signed bundle
SaaSCalimero Cloud · sealed
On-premyour customer's nodes

same bundle · same upgrade operation · one codebase

The problem, and how it goes awayShow less

The problem

Your largest customers want the product on their own premises. That usually means a second product: an installer, a support matrix, patches and upgrades you ship to every customer separately.

How Calimero answers

  • The same signed bundle runs on Calimero Cloud and on nodes your customer runs.
  • Their servers and Cloud nodes can join the same app and stay in sync.
  • One operation upgrades the app on every node in the group.

02 · Regulated teams

Internal tools for regulated teams.

Sensitive data stays inside sealed nodes, and auditors can check which build has access.

  • Nobody, including us, can read data inside a sealed node.
  • Access rules and group keys enforced by every node.
  • Auditable: the hardware quote names the exact build.
Internal toolsealed node

Expense approvalssealed

Financeread · write
Legalread
Auditorverify the build
Operatorno access to data

illustrative · rules enforced by every node

The problem, and how it goes awayShow less

The problem

Finance, legal and health teams need internal tools that hold their most sensitive data. Self-hosting them means admins who can read everything; buying SaaS means a vendor who can.

How Calimero answers

  • Nobody, including us, can read data inside a sealed node.
  • Group keys and access rules are enforced by every node.
  • Auditors can verify which build has access, from the hardware quote.

03 · Between companies

Shared apps, owned by none of them.

A supplier ledger or data clean room no single party owns; each company sees only what its group is granted.

  • An attested context no single party controls.
  • Each company sees only the data its group is granted.
  • Every party checks the exact build before it sends anything.
See how it fits togetherShow less

The problem

When companies work from the same live data, somebody has to host it, and whoever hosts it can see everything. So partners email spreadsheets, or the project never starts.

How Calimero answers

  • The shared app runs in an attested context that no single party controls.
  • Each company sees only the data its group is granted.
  • Every party can check the exact build before it sends anything.
Suppliers and partnersone attested context
Manufacturer
Supplier
Logistics
Bank

Shared supply contextattested

ordersstockshipmentsfinancing shared status everyone is granted

illustrative · each group's data, visible only to that group

04 · AI agents

Confidential AI agents.

Agents act on app data through the Calimero MCP, under the app's own rules.

  • Their own key: any agent, local, deployed or from a frontier lab, connects to your node.
  • The app's rules decide what an agent can read and change.
  • Data stays inside the node the app runs on.

Explore Confidential AI

Agent on your nodeown key
Any agentlocal · deployed · frontier lab
Calimero MCPacts under the app's rules
Your appdata stays in the node

connect an agent from Calimero Desktop · Settings · AI agent

The problem, and how it goes awayShow less

The problem

The most useful agents need your most sensitive data, and handing it to an outside service is exactly what your security team won't sign off.

How Calimero answers

  • Agents act on an app's data through the Calimero MCP, under the app's own rules.
  • Any agent gets its own key for your node: one running locally, one you deploy, or one from a frontier lab, coding agents included.
  • Connect one from Calimero Desktop in a few clicks.

Talk to us

Have a use case that isn't here? Tell us who needs to work together and what they can't share.

Talk to us about your use case

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