Engineering

Why Isonomic runs exactly one stack

Six fixed services look like a limit. They are the reason the system can make guarantees that a general-purpose platform can’t.

Authors
Isonomic Team
Published
November 6, 2026

Developers who look at Isonomic usually ask the same thing first: why only six services? A general-purpose cloud lets you run any database, any queue and any binary you like. Isonomic lets you use Isonomic SQL, Graph, Vector, Content, Host and LLM, and nothing else.

The short answer is that the restriction is the product. Because every workload uses the same known components, the system can make statements about every app that a general-purpose platform cannot make about arbitrary code.

Arbitrary code cannot be confined

On a conventional platform, an app can open network connections, start processes and write wherever it has access. To know whether it sends your data somewhere, someone has to read its code or watch its traffic, and then trust that nothing changes in the next update. App store reviews are a promise that someone looked.

An Isonomic app is built against six interfaces and has no other channel. It cannot open an arbitrary connection or address storage except through the services of the Capsule it is installed in. Whether it can leak your data is not a question of review. It is a property the runtime enforces.

Four guarantees for every app

Because apps are confined to that one interface, every installed app has the same properties, checked by software:

  • Confinement: it can only talk to the services of your Capsule.
  • Integrity: the code running matches the published build for that version.
  • Least privilege: it can read only what you approved in its manifest.
  • Consent on change: an update that asks for more access waits for your approval.

One stack also means one release

The whole stack ships as a single versioned release, built reproducibly from public source. Anyone can rebuild a release and check that its measurement matches what a node reports it is running. Nobody, including us, has to be trusted to vouch for the binaries.

It also makes Capsules portable. The same six services run on your desk, on a team Cluster and on the open network, so moving a Capsule between them changes where it runs, not how it works.

What we gave up

Some software will not fit. If an app needs a specific database we do not ship, it has to be expressed in the six services or wait for the stack to grow. We will add services slowly and in public, because every addition has to keep the guarantees above.

We think that trade is worth it. The details are in section 5 of the white paper. Read the white paper

Newsletter

Subscribe to our newsletter