Real hardware for developer workflows.

Point each GitLab project at one runner. Generic gates land on cloud capacity. KVM, ARM, NIC, GPU, and workspace leases land on the hardware they need.

Open dashboard Read the docs

.gitlab-ci.yml

gpu-smoke:
  tags:
    - saas-linux-large-amd64
    - gpu:nvidia
    - gpu:count:1
  script:
    - nvidia-smi

Connect a project runner, then request the hardware your job needs.

Set up with your agent

Give this prompt to your coding agent to install the CLI and verify access. Repository access is required during early access.

Preview prompt

Set up the RealHW CLI on this machine using https://docs.realhw.dev/get-started/agent-setup/index.md as the canonical guide. Read it first and follow its pinned checkout installation instructions; the CLI is not published on PyPI and repository access is required. Preserve existing checkouts and credentials. Use an existing environment token without displaying it, or guide me through browser login with read-only permissions. Never ask me to paste credentials into this conversation. Verify the CLI version, supported operations, and current hardware with JSON commands. Report any access or setup blocker clearly. Stop after verification; do not reserve hardware or start workloads.

Setup instructions

Connect once

One project runner keeps GitLab setup and cost attribution simple.

Target hardware

Use tags to place jobs on matching real capacity.

Reserve workspaces

Use interactive leases when a job needs a live session.