Course contentsShow
← Cloud and Infrastructure
Lesson 1728 of 2,98936. GitLab CI/CDFree lesson

GitLab Runners: Shared vs Specific

Learn the difference between shared, group, and project-specific runners and when to use each type.

GitLab Runners: Shared vs Specific

You'll learn how to choose between shared, group, and project-specific runners based on your security, cost, and isolation requirements.

What Are Runner Types?

GitLab Runners execute your CI/CD jobs, but they come in three flavors that differ in scope and availability:

Shared Runners

Think of shared runners as a public bus system—anyone in your GitLab instance can use them. These runners are available to all projects and groups, managed centrally by administrators. They're ideal for:

  • Teams with standard build requirements
  • Quick onboarding without infrastructure setup
  • Cost sharing across many projects

Trade-off: Less control over the environment and potential resource contention.

Group Runners

These are like a private shuttle for your department. Group runners are available to all projects within a specific GitLab group (and its subgroups). Use them when:

  • Multiple related projects need the same specialized environment
  • You want isolation from the broader organization
  • Your team manages its own infrastructure

Project-Specific Runners

These are your dedicated company car—exclusively assigned to one project. They provide maximum control and isolation. Choose them for:

  • Projects with unique dependencies or tools
  • Sensitive workloads requiring strict security boundaries
  • Performance-critical builds that need guaranteed resources
  • Testing on specific hardware configurations

When to Use Each

  • Shared: Default choice for standard web apps, microservices
  • Group: Shared toolchains (mobile builds, data pipelines) across related projects
  • Specific: Legacy applications, compliance-sensitive code, resource-intensive builds

You can also use multiple runner types in the same project—for example, shared runners for quick tests and specific runners for deployment.

Key Takeaway: Shared runners maximize convenience and cost efficiency, group runners balance sharing with isolation, and project-specific runners provide dedicated control—choose based on your security, performance, and management needs.