NetPilot

SONiC NOS Lab Online

Run real SONiC switches in your browser, with an AI agent that builds the fabric.

Describe a SONiC fabric in plain English and get a working lab with community SONiC in about 2 minutes.

app.netpilot.io

See It in Action

Watch NetPilot deploy a lab from a single plain-English description.

NetPilot is a containerlab contributor and integrator. Every SONiC node runs on the sonic-vs kind from the containerlab project, and the labs from our tutorials are public on GitHub. See our upstream contributions.

What NetPilot Adds to a SONiC NOS Lab

The same community SONiC you can run anywhere, with the host and the first draft of the config handled for you.

No host to run

A managed cloud VM with SONiC preloaded. Open a browser and start.

Running SONiC yourself

A Linux host with Docker, and an image from the SONiC build pipeline.

A switch that is ready

BGP and BFD running, sudo and show version working, ports up when the deploy returns.

Running SONiC yourself

bgpd stopped, no sudo, show version failing until you work around each one.

Both config layers written for you

Describe the fabric. The agent writes the config commands and the FRR config, then checks them.

Running SONiC yourself

You type config on each switch, then vtysh on each switch.

More than SONiC

Put SONiC next to other network OSes from one prompt, 17+ and growing.

Running SONiC yourself

Source and import each vendor image yourself.

SONiC Fabrics You Can Build

Each one runs on community SONiC, built by the agent and checked by you.

BGP with FRR

Leaf-spine eBGP through vtysh, with ECMP across both spines.

VXLAN EVPN

A VLAN mapped to a VNI, stretched across leaves with BGP EVPN.

Failover with BFD

Fail a link and watch BFD move the traffic to the other spine.

Port channels

LACP between SONiC switches, read from teamd.

SONiC internals

Follow a route through CONFIG_DB, APPL_DB and ASIC_DB in Redis.

Multi-vendor interop

SONiC and SR Linux or Arista cEOS in one fabric.

Ways to Run SONiC Without a Switch

Four honest ways to get hands on SONiC. Pick by who runs the host and who writes the config.

Where it runs
NetPilot
Browser, your cloud lab VM
NVIDIA Air
Browser, NVIDIA's cloud
GNS3 or EVE-NG
Your PC or lab server
containerlab yourself
Your Linux host
Starting point
NetPilot
A prompt
NVIDIA Air
A preconfigured SONiC EVPN lab
GNS3 or EVE-NG
An empty canvas
containerlab yourself
A topology file you write
Image step
NetPilot
Preloaded
NVIDIA Air
None
GNS3 or EVE-NG
Import a SONiC VS image
containerlab yourself
Download from the SONiC build pipeline
Who writes the config
NetPilot
The agent, or you on the CLI
NVIDIA Air
The prebuilt lab, then you
GNS3 or EVE-NG
You
containerlab yourself
You, in versioned files
Offline use
NetPilot
Internet for cloud labs
NVIDIA Air
No
GNS3 or EVE-NG
Yes
containerlab yourself
Yes
Cost
NetPilot
Free tier and paid plans
NVIDIA Air
Free of charge
GNS3 or EVE-NG
Free tools, your hardware
containerlab yourself
Free and open source, your host

Bottom line

Pick NVIDIA Air, GNS3 or containerlab when you need:

  • •A free hosted SONiC EVPN lab, ready to open, on NVIDIA Air
  • •Labs fully offline on hardware you own
  • •Topology files in your own Git repo and CI

Pick NetPilot when you need:

  • •A lab in about 2 minutes with nothing to install
  • •SONiC and FRR configs written and checked by the agent
  • •SONiC next to other vendors in one prompt

Verdict:To explore SONiC, the free options work well. For the fabric you actually need to test, from any browser, NetPilot does the host and the first draft, and you verify on the real CLI.

Frequently Asked Questions

Common questions about running a SONiC NOS lab online

Yes. NetPilot runs community SONiC switches on a cloud lab VM that you reach from a browser. NVIDIA Air is another hosted route, free of charge, with a preconfigured SONiC BGP EVPN VXLAN lab. A NetPilot lab starts from the fabric you describe, and an AI agent builds it for you.
Yes. Each switch is the community docker-sonic-vs image from the SONiC project's own builds, with the same config and show commands, Redis databases, orchagent and FRR. A virtual switch SAI stands in for the ASIC. The image is preloaded on every lab VM and can be replaced with your own build.
BGP, BFD, VLANs, port channels and EVPN VXLAN all work. On the docker-sonic-vs 202511 image, MC-LAG, VRRP, DHCP relay, data plane ACLs, QoS and NAT do not take effect, and ASIC behavior needs a real switch. The device guide behind the agent records each of these from tests on the device.
No. NetPilot preloads community SONiC, the open source build from the SONiC project. Dell Enterprise SONiC and other commercial distributions come from their vendors. containerlab has a dell_sonic kind for teams that hold the Dell image.
containerlab is the open source engine under every NetPilot lab, and SONiC nodes run on its sonic-vs kind. NetPilot is a containerlab contributor and integrator. To run SONiC on your own Linux host, follow the free tutorial and use the public labs from the NetPilot team.
Yes. A NetPilot lab can put SONiC next to Linux hosts, FRR, Nokia SR Linux and images you bring, such as Arista cEOS or Cisco IOL. 17+ network OSes and growing are on the supported devices list, so you can test BGP or EVPN across a vendor boundary.
Two commands, because SONiC keeps config in two places. config save -y writes interfaces, VLANs and VXLAN from CONFIG_DB to /etc/sonic/config_db.json. vtysh -c write saves BGP from FRR to /etc/frr/frr.conf. Neither file covers the other.

NetPilot is not affiliated with or endorsed by the SONiC project, the SONiC Foundation or the containerlab project. sonic-vs kind documentation

Your Next SONiC Fabric, in the Browser

Describe the fabric. The agent writes the SONiC and FRR configs, deploys real switches, and you verify on the CLI.