Distributed containerlabs, powered by Kubernetes.
Clabernetes or c9s (pronounced: see-nines) turns every network node and wire into an independently reconciled resource, then runs your containerlab workloads across the cluster.
Distributed labs
Declaratively defined, intelligently distributed
'%20stroke-width='48'%20stroke-linecap='butt'%20stroke-linejoin='miter'%20/%3e%3cpath%20d='m389%20522%20123-97%20123%2097v67l-123-73-123%2073Z'%20fill='url(%23cyan)'%20/%3e%3cpath%20d='m512%20542%20169%2098a195%20195%200%200%201-338%200Z'%20fill='url(%23blue)'%20/%3e%3c/svg%3e)
spine-01
spine-02
leaf-01
leaf-02
leaf-03
One resource
per network node
One resource
per point-to-point wire
One cluster
for distributed labs
Designed for real labs
A Kubernetes API for network infrastructure.
Keep containerlab vocabulary while gaining the reconciliation, policy, and distribution model of Kubernetes.
Primary API
Node and Link first
Model each network node and wire as an independently reconciled Kubernetes resource.
Learn moreKubernetes native
Policy that composes
Use launcher profiles, scheduling, persistence, services, and familiar cluster workflows.
Learn moreEasy adoption
Containerlab compatible
Run existing topologies through the supported Topology compiler or emit primitive resources.
Learn moreHow it works
From intent to running lab.
Author direct resources or bring an existing topology. c9s handles the controller and launcher lifecycle.
Describe
Topology or direct CRs
Reconcile
Nodes, links, and policy
Run
One launcher per node
Ready to build?
Your first distributed lab is one quickstart away.
Launch a disposable KinD cluster, install c9s, and connect your first network nodes.
Open the quickstart