Platform overview Core
Identity · mesh · licensing · console · audit
The Core every module stands on.
Identity, RBAC and SSO/SCIM; the security mesh; licensing; the AI Gateway; the console and the audit trail. The Core comes with every licence.
What it does
Core is the only identity provider. Modules trust Core-signed mesh tokens and are reached through one edge, yet each module still builds and runs on its own. Adding a module means adding one registry entry, not redesigning the platform.
The unified dashboard — Command Center, Approvals Inbox, Activity & Alerts — gives one view across every module from real APIs, with every pending human decision in one queue.
Licences are signed with ML-DSA-87 and activated per instance. Core checks the licence at its edges: when minting mesh tokens, when choosing field protections and when showing modules.
Key capabilities
Identity and access
Identity, RBAC, SSO and SCIM, with Core as the single identity provider.
Security mesh
Core-signed mesh tokens; modules reached through one edge.
Tenancy
Every SOC query is scoped to the tenant in the token; a two-tenant isolation check is part of the test runner.
Licensing
Signed with ML-DSA-87; the licence service is contacted only to activate an instance.
AI Gateway
Opt-in cloud LLM calls, capability-scoped, with the API key kept on the server.
Audit trail
Each entry and Merkle root signed with Ed25519 and ML-DSA-87.
How it works
01
Sign in
People sign in to Core, directly or through SSO.
02
Token
Core issues a mesh token scoped to the tenant.
03
Check
The licence decides which modules are shown and reachable.
04
Record
Actions and decisions land in the signed audit trail.
The human approval gate
The Approvals Inbox is part of the Core: every pending human decision, from every module, in one queue.
Licence
- Included in
- Every licence: Module, Platform and Sovereign
- Licence feature
- Core
The Core is never sold separately from a module; it comes with each licence.
See pricing and licencesWhere it stands today
Audit-log signing keys are software keys kept on the backend’s key volume; there is no TPM. TEE remote attestation is not available yet: every node reports “no TEE”, and the compliance reports say so.
See one console across every module.
Identity, approvals and the audit trail, on your deployment model.