Skip to main content
Celum is a single control plane for fleets of Kubernetes clusters. It connects to multiple Cluster API supervisor clusters, shows their tenant clusters and nodes, and drives the full cluster lifecycle — create, edit, and delete — while layering on the operational surface teams actually need day to day: networking, storage, monitoring, network-flow security, and virtual machines.
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 registered under Settings → Kubeconfigs 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 from spec.infrastructureRef.kind on each Machine.

​
Finding out what changed

Celum ships continuously, and the release notes are inside the product, at /whats-new. The page knows which build you are running and marks everything newer than it, so it answers “what did we just get” rather than listing everything ever shipped. Changes are tagged new, improved, fixed or breaking — and breaking is used for anything that needs an operator to do something, however small, which makes it the one tag worth filtering on before an upgrade. It is written for operators by hand rather than generated from commits, so it is short and it is worth reading.

​
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.