> 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/images/catalog-and-compatibility.md).

# Catalog and Compatibility

Open **Images**, then pick **Catalog** or **Compatibility**.

## Catalog

Lists template IDs, models, runtimes, and high-level status, grouped by vendor.

Use the search box, runtime chips (QEMU, Docker, Dynamips, IOL), and status filter to narrow the list. **Expand all** / **Collapse all** and the A-Z bar jump to vendor sections.

A template is a YAML definition: runtime type, resource hints, boot parameters, config injection. It is **not** a disk image. The **Console** column / `console.primary` field chooses the default Terminal UI:

| Primary             | Terminal opens     |
| ------------------- | ------------------ |
| `telnet` / `serial` | HTML5 text console |
| `vnc`               | HTML5 VNC          |
| `docker-exec`       | Container shell    |

QEMU nodes still start **both** serial and VNC backends. When both exist, the lab **Terminal...** menu offers **Open serial** and **Open VNC** in addition to the default Connect action.

### Choosing a runtime

| Runtime            | When to use it                                        |
| ------------------ | ----------------------------------------------------- |
| **Docker**         | FRR, Alpine, Linux services - low RAM, fast boot      |
| **QEMU**           | Vendor NOS fidelity; needs a licensed disk in Library |
| **Dynamips / IOL** | Classic IOS images you copy-register                  |
| **Cloud**          | Uplink to VMware networks (from the lab drawer)       |

### Coverage matrix

See [**Supported images**](/images/supported-images.md) for the full product -> template -> Serial/VNC list. In the product, the same blueprints appear under **Images -> Catalog** / **Compatibility**.

## Compatibility

Same vendor grouping, wider columns: support status, boot/console/interface notes, minimum and recommended resources, limitations, licence warnings, maintainer.

Use this before you promise a class that "XRv works here" - Compatibility statuses include **Certified**, **Tested**, **Community verified**, **Expected compatible**, **Experimental**, **Deprecated**, and **Unsupported**. (Raw `verified` in data normalizes to **Tested** in the UI.)

Community vs Pro template counts differ; Pro packs decrypt when a valid Pro licence is present.


---

# 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/images/catalog-and-compatibility.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.