# Get started

> Connect RealHW to GitLab and run jobs on selected hardware.

Source: https://docs.realhw.dev/get-started/
Documentation index: https://docs.realhw.dev/llms.txt

RealHW supports GitLab jobs and a REST client for inspecting hardware and reserving interactive consoles.

For CLI setup, start with [Set up with your agent](https://docs.realhw.dev/get-started/agent-setup/). For CI, follow the GitLab steps below.

You do not build RealHW or run RealHW services yourself in the normal customer path. You connect a GitLab project, choose runner tags, and let RealHW place each job on matching capacity.

## Start here

1. [Connect a GitLab project](https://docs.realhw.dev/get-started/connect-gitlab-project/)
2. [Run your first job](https://docs.realhw.dev/get-started/run-your-first-job/)
3. [Choose a runner](https://docs.realhw.dev/get-started/choose-a-runner/)
4. [Review the marker catalog](https://docs.realhw.dev/reference/marker-catalog/)
5. [Run an image workload](https://docs.realhw.dev/guides/run-image-workload/)

## The model

RealHW exposes GitLab runner tags:

- GitLab-compatible SaaS tags such as `saas-linux-medium-amd64`
- RealHW hardware markers such as `gpu:nvidia`, `nic:tier:25g`, and `numa:nodes:2`

GitLab uses those tags to select the RealHW project runner. RealHW then reserves matching hardware before the job starts.