Naming
When you ask Skalle to put a service on your domain, the name it receives is a Real-Time Domain. Skalle does not invent a second addressing scheme. It uses the naming layer Synx DNS already is.
/04Lab
Lab
The controls around Skalle. Each panel is a role in the toolchain, not a live status feed.
Synx DNS
Decentralized domain registration and mapping for the Real Time Web. A Real-Time Domain is how an autonomous endpoint gets a readable name, in public or in private business networks. It is the onboarding gateway.
Synx BIOS
The decentralized operating layer. It administers services across the stack, shares or transfers a data source, and shows what you own. It is network-agnostic and event-driven. The network does not store the stream.
Synx Pass
Identity and access for a decentralized network. Synx Pass recognizes people, services, and machines. When ownership moves, access moves with it.
Morph Space
Where people, AI agents, and machines enter the Real Time Web together. Register a domain, use the Synx tools, and publish Morphic Services other applications can depend on.
Synx names it, operates it, and secures who it belongs to. Skalle AI helps create, link, and administer it.
/05With Skalle
Each control stays itself. Skalle is the conversation that calls it, inside the identity you already have.
Operating
Sharing a source, seeing what you own, and moving a stream without parking it in the middle belongs to Synx BIOS. Skalle calls that layer. It does not become the operating system.
Identity
People, services, and machines are recognized in Synx Pass. When you tell Skalle to grant access, or to move a Ghost to a new owner, the right follows that identity.
Entry
Morph Space is where the service is joined to the network. Skalle can sit there as the conversation: create a Morphic Service, find what is already published, and administer what you own.
/06Who it is for
The same network, three seats. Skalle is how you speak to the seat you hold.
Developers
Build a service and link it, instead of standing up a private API for every neighbor.
Domain owners
Hold the namespace and the logic. They do not hold the consumer’s data.
Consumers
Sit at the data layer. When a device changes hands, the resource can transfer with it.