> 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/what-is-vex-nx.md).

# What is VEX-NX?

![VEX-NX Home dashboard](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2Ffdq0RwLhU4rwIam94Rxy%2Fve20261112v5-home.png?alt=media)

## Goal

Understand what VEX-NX is, who it is for, and how it compares to other lab platforms.

## In one paragraph

**VEX-NX** (**V**irtual **E**ngineering & e**X**perimentation - **N**ext e**X**perience) is an AI-assisted, multi-vendor network and infrastructure emulation platform. You design topologies in a browser, attach your own licensed vendor disk images (or FOSS Docker starters), start nodes on QEMU/KVM, Docker, IOL, or Dynamips, open consoles from the UI or SecureCRT/PuTTY, and use Assist to generate labs and configs from natural language or production running-configs.

VEX-NX ships as a **VMware OVA** and a **bare-metal USB ISO**. Tagline: **Design. Build. Validate. Automate.**

## Category

VEX-NX sits in the same category as network emulation platforms such as Cisco Modeling Labs (CML), EVE-NG, and PNETLab. It focuses on:

* Multi-vendor emulation (you supply images you are entitled to use)
* Modern web lab designer and Operate consoles
* AI-assisted topology and configuration workflows (Assist, all editions)
* Configuration import and vendor remap / redesign
* REST API and REST-based MCP tool catalog for automation and AI agents

## Who should use VEX-NX

* Network and security engineers building multi-vendor labs
* Instructors and classrooms (classroom timers require Enterprise)
* Automation engineers driving labs over the API
* Teams recreating topologies from production configs

## What you can do

* Build labs with routers, switches, firewalls, Linux, and Windows guests
* Connect ports on a Linux L2 fabric with Management / NAT / Bridge cloud nodes
* Open HTML5 serial or VNC; optionally SecureCRT or PuTTY via the Console Helper (TCP **8022**)
* Apply ScriptPad startup-config with Wipe+Start day-0 media and live CLI fallback on supported platforms
* Import EVE-NG style folders and lab bundles; track Compatibility (**Certified**, **Verified**, **Experimental**)
* Use Guided Labs / presets for practice topologies
* Use Assist (all editions) with OpenRouter for NL lab creation, configs, and Migrate Lab workflows

## What VEX-NX does not do

* It does **not** ship Cisco / Juniper / Fortinet / Palo Alto (or other proprietary) OS images. You import disks you are licensed to use.
* It is **not** a production network controller or SDN fabric orchestrator.
* The free **Student** edition includes the full template catalog. It does **not** include classroom timers or LDAP / SSO / RADIUS, and capacity stays at 5 labs / 100 nodes / 1 user. Those enterprise features and unlimited capacity require **Enterprise**.
* Enterprise LDAP, SAML/OIDC settings, and RADIUS appliance auth are configured under Administration -> Security. SAML/OIDC sign-in stubs return a clear unavailable message until the IdP integration is completed.

## OVA vs bare metal

|                | OVA                              | Bare-metal USB                          |
| -------------- | -------------------------------- | --------------------------------------- |
| Host           | VMware Workstation / ESXi        | Physical server                         |
| Nested QEMU    | Needs VT-x / nested virt exposed | Native KVM (preferred for heavy guests) |
| Day-1 software | Same                             | Same                                    |

## Next

* Why I Created VEX-NX - The Founder's Vision
* [Features](/getting-started/features.md) - capability and edition matrix
* VEX-NX vs CML vs EVE-NG vs PNETLab
* Terminology
* System requirements
* Install the OVA or Install from USB
* [First lab walkthrough](/labs/first-lab-walkthrough.md)


---

# 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/what-is-vex-nx.md?ask=<question>&goal=<user_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.