Concepts

How Apelora is put together, and why.

• Platform architectureThe target design: who owns which state, and how Studio, the control plane and Incus fit together.
• Component modelThe ideas behind modules and assemblies, in our own words, and how the implementation stays original.
• Connections and scaleEvery connection between the layers, how each is authenticated, and how far each layer scales.
• One design at every sizeHow communication, audit, security, roles, failure detection, high availability and backups work from three servers to a global fabric.
• StorageHow Incus does storage, how Apelora abstracts it, and which options exist for module data.
• Access, roles and securityWho can do what at each layer: Studio, Console, API, Incus and the servers.
• Identity and authorizationSign-in, roles, scopes, approvals, tokens and the audit log: the full model and what has been tested.
• MonitoringThe metrics every layer exposes, collected inside your installation.
• Without internet accessWhat an installation without internet access needs, what Apelora does, and what you provide.