Celum is vendor-agnostic. It detects the infrastructure provider from standard Cluster API objects, so the same dashboard manages vSphere, CloudStack, AWS, Azure, and any CAPI-compliant cluster.
What you can do
Manage clusters across supervisors
Switch between supervisor clusters and see every tenant cluster — nodes, IPs, availability zones, readiness, phase, and Kubernetes version at a glance.
Cluster lifecycle
Create, edit, and delete tenant clusters from reusable templates. Celum renders the configuration, shows you a preview, and applies it.
OIDC auth + IAM
Sign in with any OIDC provider (Entra ID and others). AWS-style policies and KRN resources gate every action; all access is audit-logged.
Run virtual machines
Create, start, stop, and expose KubeVirt VMs with cloud-init, golden-image cloning, and LoadBalancer publication.
Networking & BGP
Manage LoadBalancer pools, IP allocations, BGP sessions, and shared Gateway / HTTPRoute publication for tenant services.
Security & flow analytics
Author Cilium network policies, visualize the live traffic topology, and run flow forensics backed by ClickHouse.
How it works
Celum is a Next.js dashboard backed by a Go API. The backend owns authentication, evaluates IAM policies, and talks to each supervisor’s Kubernetes API to read and apply changes.1
Authenticate
You sign in through your OIDC provider. The backend issues a signed, httpOnly session cookie and resolves your IAM groups.
2
Pick a supervisor
Each kubeconfig Celum is given becomes a named supervisor. Choose one to scope the dashboard to its tenant clusters and resources.
3
Operate
View clusters and nodes, download kubeconfigs and SSH credentials, manage networking/storage/VMs, and author security policies — every mutating action is checked against IAM and recorded in the audit log.
4
Manage clusters
Create, edit, and delete tenant clusters from templates. Celum shows you a preview of the change before it’s applied to the supervisor.
Supported providers
Celum reads only standard Cluster API CRDs, so there are no vendor-specific dependencies. The provider is auto-detected fromspec.infrastructureRef.kind on each Machine.
Next steps
Quickstart
Connect your first supervisor and explore the dashboard.
Authentication & IAM
Configure OIDC and map provider groups to IAM policies.
Supervisors & clusters
The model behind supervisors, tenant clusters, and providers.
Architecture
How the dashboard, API, supervisors, and datastores fit together.