Runners

Runners are single-tenant, self-hosted, flexible orchestrators of remote development environments. They are self-hosted in order to compartmentalize any sensitive information related to your development environments. Runners are responsible for operational tasks like

• Scaling
• Backup
• Caching

To reduce operational overhead, runners offload all non-sensitive administration responsibilities to the management plane.

Runners are shared across developers in an organization. Organizations can have as many runners as needed, and deploy them in any region or availability zone to support remote teams in different timezones, adhere to data sovereignty, and other compliance requirements.

To create or modify runners, you must have an admin role inside the Gitpod organization.

The advantages to this architecture are:

• Private networking: runners are installed within your internal network, granting access to resources that are inaccessible from the public internet.

• Low latency: runners can be deployed in geographically close regions, minimizing latency for developers.

• Access to private source control: runners manage access to your private or public Git repositories.

• GPU support: runners have support for GPU-enabled development environments.

• Use committed spend: runners operate within your cloud environment, enabling you to leverage computing resources on your own commercial terms.