> 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** (Virtual Engineering & eXperimentation - Next eXperience) is a network lab appliance. You import one OVA into **VMware Workstation 16+** or **ESXi / vSphere 6.7+ (7/8)**, power it on, and work in a browser.

Inside the VM, VEX-NX runs your nodes on real Linux networking - not a single simulated hub:

* **QEMU/KVM** for vendor network OS images you supply (IOSv, vEOS, vSRX, and similar)
* **Docker** for light teaching stacks (FRRouting, Alpine, Linux tools)
* A **fabric** of L2 bridges between ports
* A **web UI** for Design, Operate, Observe, Validate, Present, Assist, and classroom sharing

VEX-NX does **not** ship Cisco, Arista, Juniper, or other commercial images. You register only disks you are licensed to use.

## What people use it for

| Goal                   | Typical path                                                                                         |
| ---------------------- | ---------------------------------------------------------------------------------------------------- |
| Learning               | Starter labs filtered by skill domain and Bronze-Platinum rank, FRR or Alpine containers, lab guides |
| Design / PoC           | Canvas topology, cloud uplinks, Validate before Start                                                |
| Bring existing configs | Running-config import (Pro), Convert & add / bulk folder image import                                |
| Teaching               | Local users, share labs, timers, Present mode                                                        |
| Automation             | Assist dock agent, MCP API (Pro)                                                                     |

## Who it is for

* Students and self-learners (Community + FOSS starters work without vendor disks)
* Instructors (sharing, quotas, Present)
* Engineers who need QEMU fidelity with their own images
* Teams wiring Assist / MCP into their tools (Pro)

You should be comfortable with VMware Workstation or ESXi, a modern browser, and - if you run QEMU nodes - obtaining vendor images legally.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vex-nx.com/getting-started/what-is-vex-nx.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.