PUBLIC BETA • LIVE
Sphere
The control plane behind every Kraliki product: who has access, what they pay, and whether services are healthy.
A product portfolio becomes fragile when access, billing, usage, health, and provisioning are managed by hand.
- Every app needs the same answer to who can access what and under which tier.
- Usage and model-cost events need product, customer, and account context before margins can be trusted.
- Operators need to know what services exist, where they run, and whether they are healthy.
- Provisioning customer runtimes requires records, approvals, backups, and safe apply gates.
How Kraliki Enables This
Sphere is the platform control plane below Orbit and beside the products. It owns identity alignment, tenant/account state, entitlement checks, billing and usage ledgers, service registry, observability, license and machine-token flows, and provisioning records.
Built with: IdentityEntitlementsUsage ledgerService registryProvisioningObservability
What You Get
- One entitlement truth for AgentJack, CourseRoom, BOZP, CouncilNow, and future apps.
- Usage and cost events that can be tied back to product/customer/account context.
- Service health and owner visibility without SSH archaeology.
- A safer path from customer record to runtime plan to approved provisioning.
Proven Patterns
Access gate
Ask Sphere whether a customer can use a product, feature, model lane, or vertical.
Usage accounting
Record model/provider/lane/cost context so margin and abuse controls are visible.
Service registry
Keep domains, health endpoints, owners, and runtime facts in one control-plane view.