> 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/home.md).

# Home

![Home dashboard with Launch Budget and host checks](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2F2I7EkGpRX79lmsOaP52b%2Fhome-annotated.png?alt=media)

More visuals: Home and navigation in the Visual Feature Atlas.

## Goal

Use the Home page as your day-1 dashboard: resume work, check capacity, and take the next useful step.

## Why Home exists

New appliances look empty. Home answers: Can I run something? What is broken? What is next?

## What you see

| Block                        | Purpose                                                 | Why it matters                           |
| ---------------------------- | ------------------------------------------------------- | ---------------------------------------- |
| **Continue / Get started**   | Jump back into your last lab, or create the first one   | Saves hunting through Labs               |
| **Focus** (next to Continue) | Open the lab maximized                                  | Drawing or projecting                    |
| **Launch Budget**            | Rough "how many typical labs fit" from CPU / RAM / disk | Avoid Start-all when slots are \~0       |
| **KVM / Docker chips**       | QEMU needs KVM; Guided FRR/Alpine need Docker           | Red chips -> fix before vendor labs      |
| **Sizing guide**             | Opens sizing docs                                       | Before packing many heavy nodes          |
| **Next steps**               | Smart shortcuts (import, labs, catalog, infra)          | Home tells you the next click            |
| **Host checks / Live floor** | Problems list, or labs with running nodes               | See which class lab is still burning RAM |
| **Recent**                   | Last labs by activity                                   | Reopen yesterday's lab in one click      |
| **Host pulse**               | Hostname, version, IPs                                  | Tell support exact appliance identity    |

## Recipe: confirm the appliance is healthy

1. Open **Home**
2. Host checks: Docker should be up; for QEMU labs, KVM should be available
3. If KVM is red on VMware: fix nested VT-x (System requirements), then refresh
4. If Images count is 0 and you need vendor NOS: follow the Import shortcut - or use Guided Labs with Docker seeds first

## Recipe: start a Guided Lab from Home

1. Open Labs (Next steps or sidebar)
2. **Guided Labs** -> Foundations / Routing + Bronze
3. **Use this lab**
4. Operate -> Start -> Terminal

Details: [First lab walkthrough](/labs/first-lab-walkthrough.md).

## Story

Day 1, Launch Budget shows Docker OK, KVM OK, Images 0. Home nudges import. You open Guided Labs instead (FRR needs Docker, not vendor disks) and succeed without importing Cisco yet.

## Expected result

* Green or clear Host checks for your intended workload
* One click into a lab or Images

## If it fails

* Disk full -> free image storage or expand disk (Maintenance)
* Docker down -> wait for phase 2 install; `sudo systemctl status docker`
* Pressure / 0 slots -> Stop other labs before starting more

## Related

* [Menus and toolbars](/getting-started/menus-and-toolbars.md)
* [Labs page](/labs/labs-page.md)
* [Infrastructure](/getting-started/infrastructure.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/home.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.