gitlab.net, as data

Runway V1 | Runway DocumentationSkip to content## SummaryRunway is an internal Platform as a Service for GitLab, which aims to enable teams to deploy and run their services quickly and safely.## MotivationThe underlying motivation for this initiative is covered in the Service Integration blueprint. This blueprint can be considered the implementation of the strategic requirements put forward in that proposal.### Goals* Development teams aiming to deploy their service without having to worry too much about managing the infrastructure, scaling, monitoring.* We are focusing on satellite services that are stateless and thus can be autoscaled to meet demand.* We aim to integrate with existing GitLab features and tooling to provide a streamlined experience.### Non-Goals* Hosting the GitLab monolith: The monolith is a complex application with very specialized requirements, and as such is out of scope. Deployment of the monolith is owned by the Delivery team, and there are other tools and initiatives that target this space, e.g. Cells.* Arbitrary GCP resources: While we may support a commonly used subset of GCP resources, we will be selective with what we support. If you need more flexibility, you may want to request a GitLab Sandbox project instead.* Arbitrary Kubernetes resources: As a managed platform, we aim not to expose too much of the underlying deployment mechanisms. This allows us to have a well-supported subset and gives us the flexibility to change providers. If you have specialized requirements, getting your own Kubernetes cluster may be a better option.## ProposalRunway is a means for deploying a service, packaged up as a Docker image to a production environment. It leverages GitLab CI/CD as well as other GitLab product features to do this.## Design and implementation detailsSection titled “Design and implementation details”The design of Runway aims to decouple individual components in a way that allows them to be changed and replaced over time.