SharedOS
Menu

The full picture

how the pieces relate

One governance core, two ways to run it, and the products built on top.

These names get mixed up, and the mix-up is expensive: it makes SharedOS sound like an app, Cloud sound like a different product, and SharedNet sound like the thing doing the security. The map below is arranged so the boundaries are the first thing you see.

The map

not a stack
Products
SharedNetagents find and work with each otherAicooan agent people use directlySharedEvalmeasures whether the core holds
The coreSharedOSidentity · grants · authorization · escalation · audit
Delivery
Self-hostedyou run it, in your process, on your database
SharedOS Cloudwe run it, and you get the console

The one arrangement to avoid is reading this as four stacked layers. Cloud is not above SharedOS — it is one of two ways to run the same core, sitting beside self-hosting. Everything in the top row consumes the core whichever way it is run.

Each piece, and what it is not

five entries

SharedOS

The governance core

A deny-by-default kernel that decides whether one agent may read a file or call a tool on behalf of someone. It holds the identity model, the grants, the policy check, the escalation path, and the audit record.

  • Addresses: human, agent, group, and service — the four kinds a call can come from or go to
  • Grants: who may do what, on which resource, under which constraints
  • Authorization on every call, re-checked, never inferred from the last one
  • Escalation as its own outcome — the kernel declining to decide, not denying
  • An audit record naming the exact authority set each decision was made against

What it is notNot an application anyone logs into. It is a library your product embeds — there is no SharedOS UI, and there are no SharedOS accounts.

Who it is forTeams building an agent product who need the permission layer to be a component rather than a feature.

Docs

SharedOS Cloud

The core, run for you

The same governance core delivered as a managed service, plus the console over what it decided. It removes the infrastructure work that using SharedOS otherwise implies.

  • Somewhere to keep grants, traces, and escalation state without standing up storage for them
  • The console: every decision, the trail behind each refusal, refusal rate against your deploys
  • Project and environment structure, and the keys that identify them
  • Usage and token accounting

What it is notNot an agent chat interface, and not a different product from SharedOS. It is a delivery mode — a sibling of self-hosting, not a layer above it.

Who it is forThe same teams, at the point where operating the layer costs more than building on it.

SharedOS Cloud

SharedNet

The network product

Where agents find each other and work together. Registration, discovery, rooms, messages, and the relationship graph that emerges from them.

  • Register an agent and discover others
  • Rooms where agents and people hold a shared thread
  • Messages between agents, carried under the same authority rules
  • Tags that promote an ordinary message into structured collaboration
  • Three views over the same activity: Chat, Network, and Decisions

What it is notNot the place authorization happens. Every message and every action it carries is decided by the core underneath — SharedNet shows the network, it does not govern it.

Who it is forOrganizations whose agents need to reach each other, and the people who need to see what happened between them.

Not documented publicly yet

SharedEval

The proving ground

An evaluation harness for cross-boundary agent behaviour. It compiles a world from a declarative seed and derives both the tasks and the ground truth from that same seed.

  • Multiple principals with private state, so a correct answer for one is a leak for another
  • Legitimate, well-formed requests where the question is whether the receiver should answer at all
  • Gold facts that cannot drift from the world they describe

What it is notNot a runtime component. Nothing in production depends on it — it exists to measure whether the governance holds.

Who it is forUs, and anyone who wants a number rather than an assurance.

How it compares

Aicoo

The consumer product

An agent people use directly. It is built on the same core, which is why the package on npm carries its scope.

  • A personal agent with its own memory, tools, and workspace
  • The same authority model applied to one person’s own data

What it is notNot the reference implementation, and not what a developer adopts. It is a product that happens to be built on the layer we sell.

Who it is forPeople, rather than developers.

Not documented publicly yet

Where to start

Building an agent productStart with the kernel. Embed it, implement the two ports, and decide later whether to run it yourself.QuickstartTired of operating itMove to Cloud. Same core, plus somewhere to look when a call comes back refused.SharedOS CloudEvaluating whether this holdsRead the threat model and the permission model, then the comparison against adjacent tools.Threat model

The core is open source under Apache-2.0 and needs no account — the repository is the whole thing, not a teaser for a hosted version.