Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Application types

Application types represent different types of projects that people and companies create and manage on GitLab. Gitlab delivers and replaces the disparate DevOps toolchain for both static content and traditional web applications. These are two examples of application types. We're actively investing in more robust support for new types such as cloud native and mobile apps, but we aren't done there. GitLab will expand to enable collaboration on new types.

Much like our product categories, not all application types are at the same level of maturity, which spans from being planned, to minimal, and ultimately to lovable. See below for where each application type currently stands and when they will reach higher maturity levels.

Application types

Static Content

Host your static websites on GitLab.com for free, or on your own GitLab instance, using any static website generator: Jekyll, Middleman, Hexo, Hugo, Pelican, and more. This application type is at the "complete" level of maturity.

Product lead: Jason LennyLearn moreDocumentation

Traditional Web Applications

This application type is at the "lovable" level of maturity.
Product lead: Jason Lenny

Cloud Native Web Applications

This application type is at the "complete" level of maturity.
Product lead: Jason Lenny

Mobile Apps

Developing and delivering mobile apps with GitLab is a critical capability. Many technology companies are now managing a fleet of mobile applications, and being able to effectively build, package, test, and deploy this code in an efficient, effective way is a competitive advantage that cannot be understated. GitLab is taking improvements in this area seriously, with a unified vision across several of our DevOps stages. This application type is at the "minimal" level of maturity.

Product lead: Jason LennyVision

Versioned Dependencies

Projects that generate packages as output, that are then included as dependencies in other projects. This application type is at the "minimal" level of maturity.

Product lead: Tim Rizzi

Serverless functions

This application type is at the "minimal" level of maturity.
Product lead: Viktor NagyVision

Microservices

Microservices or any system of distributed components. This application type is at the "minimal" level of maturity.

Product lead: Jason LennyLearn moreVision

Monorepos

Monorepos of related and unrelated services. This application type is at the "minimal" level of maturity.

Product lead: Eric BrinkmanVision

.NET Applications

.NET application development. This application type is at the "minimal" level of maturity.

Product lead: [TBD] • Vision

Java Applications

Java application development. This application type is at the "minimal" level of maturity.

Product lead: [TBD] • Vision

Application type maturity

Not all application types are at the same level of maturity. Some are just minimal while some are lovable. See the application type maturity page to see where each category stands.

Changes

Changes to application type maturity are effected in the application_types.yml file. Changes that impact our stated maturity goals should be approved by the VP of Product.