Roadmap

1. Done

   Phases 1 to 6, finished on 1 November 2026.

   • 1 · Network core

     done 21 October 2026

     The editor, a simulator with switching, IPv4, ARP, ICMP, UDP, DHCP and DNS, the IOS-like and Linux consoles, the simulation mode with PDUs and pcapng, keyboard control and both languages.

   • 2 · Parallel lanes

     TCP and HTTP with a load generator, the scripting language, NAT and access lists, RIP, OSPF, spanning tree and IPv6.

   • 3 · Distributed systems

     done 22 October 2026

     Load balancer, sharded key-value store, cache, queue and workers, fault injection, scripts in hosts, metrics and the lab in the window.

   • 4 · A full network lab

     Wireless, graded tasks, BGP, rewinding the simulation, the physical view, groups and background pictures, and more services: files, TFTP and FTP, SNMP, mail, logins with RADIUS, SSH, 802.1X.

   • 5 · Scripts and web

     Script files on the devices and a web browser with forms, page scripts, style sheets, cookies and HTTPS over real TLS 1.3.

   • 6 · A workstation in every host

     A shell with folders and processes, several sessions per device, a small desktop with programs in windows, an IDE with debugger and tests, and services as units that are deployed and load-tested.

2. Under way

   Phase 7: breadth and depth, planned on 1 November 2026.

   • Editor and hardware

     done 2 November 2026

     Dock tabs move only after a short hold, new device models (49 in all), choosing the cable first and new kinds of cable, slim labels, a start page with templates.

   • Firewall

     done 2 and 3 November 2026

     A Firewall tab with rules, NAT, a rule test and the equivalent commands; then zones and stateful sessions on the firewall models.

   • Academy

     done 2 to 4 November 2026

     The course format and course view, quizzes, tests and fault hunts, installing courses from GitHub, and the first two courses: Network basics and Fault finding in networks.

   • Architecture lab

     done 2 to 4 November 2026

     CPU and RAM per device, parameter sweeps, experiments in the window and a database service.

3. Next

   The rest of the architecture lab, then the course that uses it.

   • Replication

     The database ships its log to replicas over the network, asynchronous, semi-synchronous or synchronous, with measured lag and lost commits; promotion, fencing and split brain; reads through the load balancer with a health check for lag.

   • Traffic steering

     A reverse proxy with routes, rewriting and TLS termination that costs CPU; a load balancer with connection limits, sticky sessions, path routing, slow start and outlier ejection; rate limits, circuit breakers, retries with backoff, a database pooler and DNS round robin.

   • Autoscaler and studies

     An autoscaler over a pool of switched-off hosts, canary and blue-green releases, and guided labs that weigh one design against another: bigger or more, replica or cache, when to shard.

   • Course: Scaling

     An academy course built on the labs above.

4. Later

   The order is decided when the time comes.

   • Module slots

     Cards in devices, swapped while the device is off, and saving a device of your own.

   • More protocols

     EtherChannel with LACP, port security, VRRP, PPP and PPPoE, GRE and IPsec with a VPN client, QoS.

   • More courses

     Switching and VLANs, routing, services.

   • Firewall details

     Object groups and access lists for IPv6.

   • Ideas

     Sharding with moves while running, cache strategies, regions and failover, tracing across services, chaos experiments.

Not planned: protocols that belong to a single vendor.