Antimony and the Containerlab apps
containerlab has its own graphical tools: the Containerlab apps, a VS Code extension, a desktop app and a web app that share one topology editor. They look similar to Antimony at first glance, since both draw topologies, deploy labs and open terminals. Underneath, they’re different kinds of software.
In short
Section titled “In short”- The Containerlab apps are a graphical front end for containerlab. They run containerlab on your machine, or through
clab-api-serveron a lab host, and show what it does. Your topologies are files in your workspace, and your login is a Linux account on the lab host. - Antimony is a multi-user platform. It has its own server and database, its own users and permissions, and its own model of topologies, labs and schedules. containerlab is the engine it deploys with, not the product.
If you build and debug labs for yourself, the Containerlab apps are a good fit. If many people should work with labs on shared infrastructure, such as a class, a training or a team, with control over who sees and deploys what, you want a platform, and that’s what Antimony is.
What a platform adds
Section titled “What a platform adds”Everything below is part of Antimony itself, not something you assemble around it:
- Access control through your identity provider. People sign in through your OpenID Connect provider, such as Microsoft Entra ID, Keycloak or authentik, and the groups you already have there decide which collections they see, and whether they may edit or deploy from them. Add a student to a class group and they get its labs the next time they sign in. No accounts to manage in Antimony or on the server.
- Topologies managed centrally. Topologies live on the server, organised in collections, with their config and bind files. Instructors prepare them once, everyone with access uses the same version.
- Labs for many people at once. A topology can be deployed as many labs in one step, one per student, each with its own start and end time. Antimony deploys and destroys them on schedule.
- Untrusted users, safely. A topology policy blocks every topology feature that would let a lab reach the server, its secrets or another user’s lab, so students can deploy labs without being trusted with the server.
- Access to nodes without host access. Terminals open in the browser for the people allowed to use the lab, and an SSH server gives shells and packet capture from your own tools. Nobody needs an account on the machine that runs the labs.
- A server that keeps running. Labs are recovered after a restart, their state is tracked live, and their recent logs are kept, whether or not anyone has the page open.
- An API for everything. The REST and Socket.IO APIs do everything the interface does.
Feature comparison
Section titled “Feature comparison”| Feature | Containerlab apps | Antimony |
|---|---|---|
| Users and permissions | ||
| Several users on one server | ||
| Sign-in and access control through your organisation's identity providerMicrosoft Entra ID, Keycloak, authentik or any other OpenID Connect provider. Users and groups are managed where they already are, not in Antimony. | ||
| Give a group, such as a class, access to its own labsUse the groups you already have in your identity provider, for example hs25-cn1. A group gets access to a collection, and its members only see the topologies and labs in it, while administrators see everything. | ||
| Per-group rights to view, edit and deploy | ||
| Topologies shared between usersThe Containerlab apps have one shared folder that every user can edit, deploy and destroy. | ||
| Security | ||
| Safe for users you don't trust with the serverIn the Containerlab apps, users can deploy whatever containerlab accepts, for example a topology that mounts the host's files. Antimony's topology policy blocks such features. | ||
| Restrict nodes to images from allowed registries | ||
| Users get no login on the lab hostclab-api-server signs users in with their Linux account and password on the lab host, so every user is a user of that machine. | ||
| Only administrators can deploy topologies with unsafe features | ||
| Labs | ||
| Deploy labs and control their nodes, on Docker or Kubernetes | ||
| Terminals, logs, node statistics and packet capture | ||
| Every node through one SSH port, from your own SSH client and WiresharkThe Containerlab apps open captures in your own Wireshark from the desktop app or VS Code, and SSH goes through a port clab-api-server forwards for each session. With Antimony, plain ssh is all you need: every node of every lab is reachable through one address. | ||
| Many labs from one topology in one step | ||
| Scheduled labs with a start and end time | ||
| Several lab hosts from one app | ||
| Link impairments (delay, loss, rate) | ||
| Tools | ||
| Graph and YAML editor, config files and Git | ||
| Web app, desktop app and REST API | ||
| Integrated into VS Code | ||
| Editor can be embedded in other tools | ||
| Desktop app on macOS and Windows | ||
Supported Partly Not supported
Where they overlap
Section titled “Where they overlap”Both edit topologies in a graph and as YAML, deploy and destroy labs, start, stop and restart nodes, open terminals, stream logs and capture packets, and run labs on Docker or on Kubernetes with clabernetes.
They also share a file format. Antimony stores the layout in containerlab’s annotations file, <topology>.clab.yml.annotations.json, the same one the Containerlab apps use, so a topology drawn in one opens with its layout in the other. You can build a lab in VS Code with the Containerlab extension, then upload it to a collection in Antimony and deploy it for everyone who needs it, without converting anything.