The layer underneath.
How independent platforms behave as one system — and what keeps that safe.
The composition principle.
Each platform stands alone. A company can adopt exactly one and get a complete product, with nothing else required. That is deliberate: we do not sell a monolith.
StoneOS is the layer that makes them behave as one system. Identity is shared, so a person is the same person everywhere. Events are shared, so what happened in one platform is legible from another. Operational standards are shared, so what you learn running one surface transfers to the next. The compounding advantage only appears when the pieces are composed — StoneOS is that composition.
The architecture.
How the ecosystem is organized and operated — from the execution core outward.
- 1 Execution core The architectural base and SDK the whole stack is built on
- 2 Cognitive & sensitive backbone Identity, intelligence, events, and the physical world
- 3 Enterprise channels Where daily operation and money run
- 4 Ecosystem activators Surfaces that energize the ecosystem
- 5 Third-party apps Created, published, and run — all on your rules
Every ring stands on the one beneath it. Universe and the App Store are how people move across all of them.
Built on Link Loom.
Underneath the layers there is one execution core: Link Loom — the architectural base and SDK every platform is built on. It is also what makes the stack extensible: App Engine, the app foundation of Link Loom Cloud, is how official and third-party apps are created, shipped, and run — IDE included. One core, one way of building. That is why everything above it can compose.
Identity, held once.
Identity in StoneOS is not a login database — it is infrastructure, run by Veripass. Each person and each device holds one identity with contextual access: what you can reach depends on who you are, what role you hold, and where you're operating from. Grants are explicit and centrally legible; revocation propagates to every platform immediately. Sessions traverse the stack without re-authentication because trust is established at the layer, not re-negotiated per tool.
Events, written once.
Every platform emits its operational events into a shared architecture, run by Vectry Analytics. Events are attributed — every one carries the identity that caused it — and durable, so history is total, not sampled. Because platforms write to the same record, causality is traceable across surfaces: a price change in Mi Retail, the approval that authorized it, and the result it produced are one chain, not three exports. This is what makes cross-platform questions answerable without an integration project.
Standards, learned once.
The third layer is the least visible and the most felt: every platform follows the same conventions for roles and permissions, for how records are structured, for how reports read, and for how administrative actions are confirmed and logged. The practical effect is transfer — a manager fluent in one surface is functional on the next one in hours, and an operating procedure written for one platform mostly survives contact with another.
The posture.
Explicit access
No permission exists unless someone granted it. Composition never widens access on its own.
Least privilege
People, devices, and apps get the narrowest scope that does the job.
Total traceability
Every consequential action is an attributed event. The audit trail is the system, not a feature of it.
Immediate revocation
Ending access is one action, honored stack-wide, at once.
Isolation by platform
Platforms share the layer — not each other's internals. A fault in one is not a fault in all.
Your data stays yours
Adopting, composing, or leaving: your records and your event history belong to you.
Why bother.
Alone, each platform saves you from one bad tool. Composed, they save you from the seams — the re-keying, the reconciliation, the "which system is right?" meetings. Seams are where businesses leak time and truth. The layer is how you stop paying for them.
Get started