The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
|Content Last Reviewed||
Thanks for visiting this direction page on the Runner SaaS category at GitLab. This page belongs to the Runner SaaS Group within the Verify Stage and is maintained by Gabriel Engel. Feel free to follow our YouTube playlist where we will upload walkthroughs of direction page updates and iteration kickoffs.
Runner SaaS is the product development effort for SaaS runners hosted by GitLab. Today those product offerings include:
The primary FY2024 runner themes focus on closing critical competitive gaps with other hosted solutions and also enable Ultimate adoption for GitLab SaaS, with the clear focus on achieving best-in-class ci build speed.
2xlargerunners on Linux to offer more powerful compute
In the next three months we plan to complete the following projects:
We are not actively working on the following:
BIC (Best In Class) is an indicator of forecated near-term market performance based on a combination of factors, including analyst views, market news, and feedback from the sales and product teams. It is critical that we understand where GitLab appears in the BIC landscape.
Cloud-native CI/CD solutions, such as GitLab.com, Harness.io, CircleCI, and GitHub, allow to run CI/CD pipelines on a fully managed runner fleet with no setup required.
In addition to eliminating CI build server maintenance costs, there are other critical considerations for organizations that can migrate 100% of their CI/CD processes to a cloud-native solution. These include security, reliability, performance, compute types, and on-demand scale.
CI build speed or time-to-result, and the related CI build infrastructure cost efficiency are critical competitive vectors. CircleCI and Harness.io are promoting CI-build performance in their go-to-market strategy. Both GitHub and Harness.io explored the cost impact of CI build performance measured by build times on hosted solutions.
Hosted Linux Compute
|small||2 vCPUs, 8GB RAM||Available||Available||Available|
|medium||4 vCPUs, 16GB RAM||Available||Beta||Available|
|large||8 vCPUs, 32GB RAM||Available||Beta||Available|
|x-large||16 vCPUs, 64GB RAM||Available||Beta||Available|
|2x-large||32 vCPUs, 128GB RAM||Available||Beta||Not available|
|3x-large||48 vCPUs, 192GB RAM||Not available||Beta||Not available|
|4x-large||64 vCPUs, 256GB RAM||Not available||Beta||Not available|
Hosted GPU Compute
|lite||Nvidia Tesla P4||Not available||Not available||Available|
|standard||Nvidia Tesla T4||Available||Planned Q4||Available|
|premium||Nvidia Tesla V100||Planned Q4||Not available||Available|
macOS - Offer Positioning and Hosted Build Machines
|Positioning statement||SaaS runners on macOS provide an on-demand macOS build environment fully integrated with GitLab CI/CD.||A GitHub-hosted runner is VM hosted by GitHub with the GitHub actions runner application installed.||A CI/CD service built into Xcode, designed expressly for Apple developers.||Industry-leading speed. No other CI/CD platform takes performance as seriously as we do.||Build better mobile applications, faster.|
|Value proposition||You can take advantage of all the capabilities of the GitLab single DevOps platform and not have to manage or operate a build environment.||When you use a GitHub-hosted runner, machine maintenance and upgrades are taken care of.||Build your apps in the cloud and eliminate dedicated build infrastructure.||The macOS execution environment allows you to test, build, and deploy macOS and iOS apps on CircleCI.||CI for mobile - save time spent on testing, onboarding, and maintenance with automated workflows and triggers|
|Available machines||Apple silicon (M1): medium||x86-64: small, x-large||n/a||Apple silicon (M1): medium, large; x86-64: medium, x-large||Apple silicon (M1): medium, large; x86-64: medium, large, x-large|