NetPilot

containerlab in the Cloud

containerlab is the open source engine. NetPilot runs it in the cloud and adds the AI agent.

Describe a lab in plain English and get real network OSes running on hosted containerlab in about 2 minutes.

app.netpilot.io

NetPilot is a containerlab contributor and integrator. The NetPilot team built the mikrotik_chr kind that shipped in containerlab v0.82.0. See our upstream contributions.

See It in Action

Watch NetPilot deploy a multi-vendor lab on cloud containerlab from a single plain-English description.

What NetPilot Adds on Top of containerlab

The engine stays the same. The host, the YAML and the per-vendor configs move to NetPilot and its agent.

The host

A managed cloud VM. Open a browser and start.

Running it yourself

A Linux host with Docker that you install and maintain.

The topology

Describe the lab in plain English. The agent writes the containerlab YAML and the per-vendor configs, then deploys.

Running it yourself

You write the YAML and the startup configs, with full control of every line.

Changes

"Add an Arista spine and move OSPF to area 0.0.0.1." The agent updates the topology and every device.

Running it yourself

You edit the file, redeploy, and push configs per device.

The CLI

SSH from the browser into every device. Real network OS, real output.

Running it yourself

SSH from your host into every device. Real network OS, real output.

containerlab Images, UI and Upstream Work

17+ network OSes and growing, in one browser tab, on the engine network engineers already use.

containerlab images, ready to run

Nokia SR Linux, FRR and Linux are built in. MikroTik RouterOS (CHR) and SONiC (community VS) are preloaded on every lab VM.

containerlab IOL and other vendor images

Upload a licensed image once, such as Cisco IOL or Arista cEOS, and NetPilot automates the build. Custom builds such as Cisco IOS-XE are built for you.

containerlab UI in the browser

Chat with the agent, view the live topology and open a terminal on any device. Nothing to install on your machine.

Upstream work

When a NetPilot lab needs something containerlab does not do yet, the NetPilot team sends the fix or the feature upstream.

Running containerlab Yourself vs on NetPilot

The same engine in two setups. Pick by who should own the host and the YAML.

Lab engine
Running containerlab yourself
containerlab
containerlab on NetPilot
containerlab
Where it runs
Running containerlab yourself
Your Linux host, WSL, or a Linux VM on macOS
containerlab on NetPilot
A managed cloud VM, reached from a browser
Who writes the topology
Running containerlab yourself
You, in YAML you own and version
containerlab on NetPilot
The AI agent, from a plain-English prompt
Who writes device configs
Running containerlab yourself
You, per vendor
containerlab on NetPilot
The AI agent, per vendor
Images
Running containerlab yourself
Pull from a registry, or build with vrnetlab
containerlab on NetPilot
Built in, preloaded, or uploaded once with the build automated
Interface
Running containerlab yourself
CLI, plus the containerlab GUI for VS Code, desktop and web
containerlab on NetPilot
Browser app with chat, topology view and SSH terminals
Offline use
Running containerlab yourself
Yes, on hardware you own
containerlab on NetPilot
Internet connection for cloud labs, on-prem through Contact Sales
CI pipelines
Running containerlab yourself
One command from any CI runner
containerlab on NetPilot
REST API (enterprise), reproducible prompts
Host access
Running containerlab yourself
Full root on your own host
containerlab on NetPilot
Managed for you
Cost
Running containerlab yourself
Free and open source, plus your host and time
containerlab on NetPilot
Free tier and paid plans for teams

How It Works

Describe the lab, let the agent build it on containerlab, then verify it on the real CLI.

1

Describe Your Network

"Build a multi-vendor OSPF lab with Cisco and Nokia routers" or "Create a VXLAN EVPN leaf-spine fabric." Describe it in plain English, or import existing configs.

app.netpilot.io
2

The Agent Builds It on containerlab

The agent writes the containerlab YAML, assigns IP addressing, generates per-vendor device configs, deploys and checks the result.

app.netpilot.io
3

Verify on the Real CLI

"Flap the R2-R3 link" or "add a second leaf." The agent updates the YAML and every affected device, and you SSH into any node to check it yourself.

app.netpilot.io

Labs Engineers Run on containerlab

Real devices, real protocols and real CLIs, built by the agent and checked by you.

OSPF & BGP Labs
MPLS / Segment Routing
Multi-Vendor Topologies
Firewall Integration
Data Center Fabrics
Network Automation Testing
Change Validation Sandbox
CCNA/CCNP/CCIE Prep

Which Setup Fits Your Work

The two fit together: containerlab on your CI runners, NetPilot for fast multi-vendor work.

Run containerlab yourself when

  • You need labs fully offline on hardware you own
  • You already have Docker and vrnetlab image pipelines
  • Declarative YAML in CI is central to your workflow
  • You want root on the host for custom tooling

Run it on NetPilot when

  • You want a multi-vendor lab in about 2 minutes
  • You would rather describe the lab than write the YAML
  • You want the agent to write and change per-vendor configs
  • You want to work from any browser, Chromebooks and iPads included

Frequently Asked Questions

Common questions about running containerlab in the cloud with NetPilot

Yes. NetPilot runs containerlab in the cloud on managed lab VMs. You open a browser, describe the lab, and the agent deploys it on containerlab with no Docker or Linux host of your own. A full multi-vendor lab is ready in about 2 minutes.
NetPilot is a containerlab integrator and contributor. containerlab is the open source engine that deploys every lab, NetPilot hosts it and adds the AI agent, and the NetPilot team sends work back upstream, including the mikrotik_chr kind that shipped in containerlab v0.82.0.
Yes, two kinds. containerlab has its own GUI, built on TopoViewer, as a VS Code extension, a desktop app and a web app, which run against a Linux host you operate. NetPilot is a browser app on a hosted VM: you chat with the agent, see the topology, and open an SSH terminal to any device.
Nokia SR Linux, FRR and Linux are built in. MikroTik RouterOS (CHR) and SONiC (community VS) are preloaded on every lab VM, replaceable with your own versions. Cisco IOL, Cisco XRd, Cisco NX-OS, Arista cEOS, Juniper cRPD, Juniper vJunos, Palo Alto, Fortinet, Aruba AOS-CX and Dell SmartFabric OS10 run from an image you upload, and NetPilot automates the build. That is 17+ network OSes and growing.
Yes. Upload your licensed Cisco IOL image once and NetPilot builds it for you. Running containerlab yourself, the cisco_iol kind uses an image you build with vrnetlab from the IOL binary. Either way the node is the same real IOS software with the same CLI.
Yes, through a hosted service. containerlab needs Docker on a Linux host. On NetPilot that host is a managed cloud VM, so your own machine needs only a browser.
Yes. The NetPilot agent writes the containerlab topology from a plain-English description, then generates the IP plan and per-vendor device configs, deploys the lab and checks that it works. You can SSH into any device to verify the result on the real CLI.
NetPilot has a free tier with paid plans for teams. containerlab itself is free and open source under the BSD 3-Clause license, so running it on your own Linux host costs you the host and your time.
To run it yourself, yes: containerlab runs on a Linux host, on Windows through WSL, and on macOS through a Linux VM or dev container. On NetPilot it runs on a cloud VM, so any browser on any operating system works.
Yes. NetPilot offers a self-hosted deployment on your own Linux hosts for teams with compliance, data-residency or air-gapped requirements, with the agent writing the YAML and per-vendor configs. Cloud hosting is the default, and on-prem is available through Contact Sales.

Your Next containerlab Lab, in the Cloud

Describe the network. The agent writes the YAML and the configs, deploys on containerlab, and you verify on the real CLI.