> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/getting-started/features.md). # Features ![Labs manager showing product surface](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FaYnTMWKr4WM971dYZIif%2Flabs-manager.png?alt=media) ## Goal Know what the platform can do and what each licence edition unlocks. ## Platform capabilities (every edition) Limits (labs, nodes, seats) still depend on licence. | Area | What you get | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Labs** | Blank labs, Guided Labs, Design / Operate / Visualize (+ lenses) | | **Topology** | Drag templates, connect ports, groups / nested maps, undo/redo, name font size | | **Runtimes** | QEMU/KVM, Docker, Dynamips, Cisco IOL (with your images / binaries); **VEX-NOS** Exact / Native / Lite picker on supported templates | | **Fabric** | Linux bridges; Management / NAT / Bridge clouds; External management (EXT-MGMT) when configured | | **Images** | Library, Catalog, Compatibility, Convert & add, bulk import | | **Consoles** | HTML5 serial / VNC / Docker shell (docked + maximized); optional SecureCRT / PuTTY (port **8022**) - [Operate and consoles](/labs/operate-and-consoles.md) | | **ScriptPad** | Startup-config profiles; Wipe+Start day-0 ISO + live CLI inject on supported templates | | **Validate** | Pre-flight checks (Visualize -> Validate lens) | | **Traffic Lens** | Utilization / bandwidth paint + dock under Visualize - [Traffic Lens](/labs/traffic-lens.md) | | **Packet capture** | Captures dock + Capture Center PCAP - [Packet capture](/labs/packet-capture.md) | | **Link impairment** | Delay / jitter / loss on fabric links - [Link inspector and impairment](/labs/link-inspector-and-impairment.md) | | **Present / Preview** | Clean Present lens vs immersive Design Preview | | **Classroom** | Share labs; Enterprise timers, dashboard, grade, PDF, Proctor | | **Infrastructure** | Host pulse, cloud uplinks, management network | | **Home** | Continue last lab, Launch Budget, Host checks | | **API** | JWT REST API for labs, nodes, images, and more (REST API overview) | ## Edition matrix Two editions ship: **Student** (free, builtin, no licence file) and **Enterprise** (signed licence file). | Feature | Student | Enterprise | | ---------------------------------------- | :-----: | :-------------------------------------------------------: | | Core UI, QEMU/Docker, consoles, starters | Y | Y | | Packet capture | Y | Y | | Running-config import / Migrate Lab | Y | Y | | Lab bundle import | Y | Y | | Assist (OpenRouter) | Y | Y | | MCP agent API (REST tools) | Y | Y | | Concurrent labs | 5 | Unlimited | | Nodes per lab | 60 | Unlimited | | Users | 1 | Unlimited | | Full commercial template catalog | Y | Y | | Classroom timers | N | Y | | LDAP / SSO / RADIUS | N | Y (Admin Security; SAML/OIDC login stubs until IdP wired) | Seat counts and lab limits: Licence editions and activation. ## Recipes worth knowing ### Nested maps Group nodes into child maps. Use breadcrumbs to navigate. Full preview shows the whole topology. See [Design mode](/labs/design-mode.md). ### External consoles Right-click a running node -> **Open in SecureCRT/PuTTY**. Install the Windows Client Pack once (re-run after appliance updates that refresh the helper). See [Operate and consoles](/labs/operate-and-consoles.md). ### Compatibility status **Certified** means honest verification on VEX-NX: Start, live terminal, guest config (or documented N/A), then Stop/Wipe/Start retest. Always confirm live chips under Images -> Compatibility. See [Catalog and Compatibility](/images/catalog-and-compatibility.md). ### Offline Docker starters Current OVA/ISO builds seed **FRR** and **Alpine** offline tarballs. If Start fails on image pull, run `sudo vexnx-seed-docker` and check DNS. See [First lab walkthrough](/labs/first-lab-walkthrough.md). ### Wipe and ScriptPad Wipe recreates the node disk overlay. On supported platforms, VEX-NX attaches day-0 config media from the active ScriptPad profile, verifies hostname, and can fall back to live CLI inject. See [Operate and consoles](/labs/operate-and-consoles.md). ### VEX-NOS Adaptive Runtime On supported templates, choose **Exact** (vendor QEMU), **Native** (IOL/cEOS-style), or **Lite** (FRR protocol stand-in). Lite is labeled as simulation, not vendor NOS. See VEX-NOS Adaptive Runtime. ### Assist and MCP Assist can draft labs and configs on both editions once OpenRouter is configured. The MCP **tool catalog** is available over REST for agents on both editions (not a desktop stdio MCP server yet). See [Using Assist](/assist/using-assist.md) and MCP and AI tools. ## What is not included * Vendor OS images, IOL binaries, or Cisco `iourc` files (bring your own disks; catalog templates are unlocked on Student and Enterprise) * Classroom timers and LDAP / SSO / RADIUS on Student (require Enterprise) * Hardware appliance firmware packages as QEMU VMs * Claim of official Cisco / Juniper image redistribution ## Related * [What is VEX-NX?](/getting-started/what-is-vex-nx.md) * VEX-NX vs CML vs EVE-NG vs PNETLab * Licence editions and activation * [Supported images](/images/supported-images.md) * Install the OVA / Install from USB --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.vex-nx.com/getting-started/features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.