GitLab Runner: Introduction

This documentation is part of the Getting started guide. You can view the complete guide here: Connect your Stackhero GitLab Runner to GitLab.com or a self-hosted GitLab and run your first pipeline.

👋 Welcome to the Stackhero documentation!

Stackhero offers you an easy-to-use GitLab Runner cloud solution, designed to efficiently run your GitLab CI/CD jobs. Here’s what you can expect:

• Unlimited CI/CD minutes: there’s no per-minute billing, so your pipelines can run whenever you need them.
• Concurrent jobs: run multiple jobs in parallel to speed up your entire pipeline.
• The Docker executor with Docker-in-Docker support: simplify building and pushing your container images.
• Compatible with GitLab.com as well as any self-managed GitLab instance.
• A private, dedicated VM powered by fast NVMe/SSD disks for consistent, reliable builds.
• Available in both 🇪🇺 Europe and 🇺🇸 USA regions.

Save time: connect your first GitLab Runner and start running pipelines in just a few minutes!

A GitLab Runner is the agent responsible for executing your GitLab CI/CD jobs. Each time a pipeline is triggered, the runner picks up each job, runs it inside a clean Docker container, and then sends the results back to GitLab.

With Stackhero, your runner operates on a private, dedicated VM. There are no per-minute fees or usage quotas, and your CI/CD minutes are unlimited. Depending on your plan, your runner can handle dozens of concurrent jobs at the same time.

This guide will show you how to connect your Stackhero runner to GitLab in just a few minutes.