GitLab Direction

This page describes the direction and roadmap for GitLab. It's organized from the short to the long term.

Your contributions

GitLab's direction is determined by GitLab the company, and the code that is sent by our contributors. We continually merge code to be released in the next version. Contributing is the best way to get a feature you want included.

On our issue tracker for CE and EE, many requests are made for features and changes to GitLab. Issues with the Accepting Merge Requests label are pre-approved as something we're willing to add to GitLab. Of course, before any code is merged it still has to meet our contribution acceptance criteria.

What our customers want

As a company, GitLab tries to make things that are useful for our customers as well as ourselves. After all, GitLab is one of the biggest users of GitLab. If a customer requests a feature, it carries extra weight. Due to our short release cycle, we can ship simple feature requests, such as an API extension, within one or two months.

Previous releases

On our release list page you can find an overview of the most important features of recent releases and links to the blog posts for each release.

Future releases

GitLab releases a new version every single month on the 22nd. Note that we often move things around, do things that are not listed, and cancel things that are listed.

This page is always in draft, meaning some of the things here might not ever be in GitLab. New premium features are indicated with "EE Premium" label. This is our best estimate of what will be new premium features, but is in no way definitive.

The list is an outline of tentpole features – the most important features of upcoming releases – and doesn't include any contributions from volunteers outside the company. This is not an authoritative list of upcoming releases - it only reflects current milestones.

GitLab Community Edition




Coming Soon

GitLab Enterprise Edition




Coming Soon

2017 Goals

Some key achievements for Q2, Q3 for 2017.

1. Cloud Native and Container Schedulers

  1. (DONE) Q1: Make it work on Google Cloud
  2. Q2: EE Premium: Canary deploys
  3. Q2: Support app + database deployments

2. Monitoring and Feedback

  1. (DONE) Q1: Ship prometheus with GitLab
  2. (DONE) Q1: Monitoring of Customer Auto Deployed Apps on Kubernetes.
  3. (DONE) Q2: Support for non-Auto Deployed (Manually?) Apps on Kubernetes
  4. Q2: Monitor custom variables from within GitLab
  5. Q3: EE Premium: Code analytics

3. Made for enterprise

  1. (DONE) Q1: Ship nested groups
  2. Q2: EE Premium: Service Desk
  3. Q2: Group level issues support (boards)
  4. Q2: EE Premium: Multi project pipelines
  5. Q2: EE Premium: Detailed audit logs
  6. Q3: EE Premium: Reporting
  7. Q3: EE Premium: Disaster Recovery

4. Easy building, deploying, and monitoring

  1. (DONE) Q1: Introduce easier, more powerful filtering
  2. (DONE) Q2: Deploy boards
  3. Q2: Make auto deploy easier to discover and use
  4. Q2: Improve the navigation
  5. Q2: Bring real time to GitLab

5. as powerful SaaS

  1. Q2: Introduce plans and in-UI subscriptions


Below are features that represent the direction we see GitLab going in. This list is not prioritized. We invite everyone to join the discussion by clicking the direction items that are of interest to you. Feel free to comment, vote up or down any issue or just follow the conversation. For GitLab sales, please add a link to the account in that has expressed interest in a wishlist feature. We very much welcome contributions that implement any of these things.

Chat Commands


We want to help developers get their code into production; providing convenience and confidence to the developer in an integrated way. CI/CD focuses on steps 6 through 9 of our scope: Test (CI), part of Review (MR), Staging (CD), and part of Production (Chatops). When viewed through the CI/CD lens, we can group the scope into CI, CD, and things that are currently beyond any definition of CD.

GitLab CI/CD Scope

Many of the issues describe development of an n-tier web app, but could equally be applied to an iOS app, Ruby gem, static website, or other type of project.

See a slightly more complete rendering of an example pipeline.



GitLab CI provides an explicit build stage and the concept of build artifacts, but we might need to separate out the build artifacts from test artifacts. For example, you might want your test runner to create a JUnit-style output file which is available for external consumption, but not included in the build image sent to production. Creation of an explicit build aligns well with Docker where the result of the build stage is a Docker image which is stored in a registry and later pulled for testing and deployment.



A key part of CD is being able to deploy. We currently have this ability via scripts in the deploy stage in .gitlab-ci.yml. We will go further.


What's the difference between Deploy and Deliver? There's a big benefit to decoupling deployment of code from delivery of a feature, mostly using feature flags. Continuous integration helps improve the speed of development, but feature flags take it to another level, giving you the confidence to integrate code even more often while providing a gradual and granular method for delivery.


See Prometheus Monitoring.


Code Review

Code review meta issue

Container Registry

No current issues

Moderation Tools

Moderation tools meta issue

Open Source Projects

Features for open source projects



Prometheus Monitoring

Service Desk

Team-first collaboration with issue boards


User management

User management meta issue

Version Control for Everything


Wiki improvements meta issue

Workflow management with issues

No current issues


Moonshots are big hairy audacious goals that may take a long time to deliver.

Premium Features

Premium features will only be available to EE Premium subscribers. These issues appear in direction above, but are collected here for convenience.


Our vision is an integrated set of tools for application lifecycle management based on convention over configuration. To achieve this we ship the following features in our Omnibus package:


  1. Idea (Chat) => Mattermost
  2. Issue (Tracker) => Issue Tracker
  3. Plan (Board) => Issue Boards
  4. Code (IDE) => Web editor and web terminal
  5. Commit (Repo) => GitLab Repositories
  6. Test (CI) => GitLab Continuous Integration and Container Registry
  7. Review (MR) => GitLab Merge Requests and Review Apps
  8. Staging (CD) => GitLab Deploy and auto deploy
  9. Production (Chatops) => Mattermost slash commands and Slack slash commands
  10. Feedback (Monitoring) => Cycle Analytics and Prometheus.

Also see our demo.

Outside our scope

  1. Error monitoring Sentry, Airbrake, Bugsnag
  2. Logging Fluentd, ELK stack, Graylog, Splunk, LogDNA
  3. Tracing OpenTracing, LightStep
  4. Network Flannel, Openflow, VMware NSX, Cisco ACI
  5. Network security Suricata, Nmap, rkhunter, Metasploit, Snort, OpenVAS, OSSEC
  6. Configuration management although we do want to upload cookbooks, manifests, playbooks, and modules for respectively Chef, Puppet, Ansible, and Salt.
  7. Container configuration agents ContainerPilot, Orchestrator-agent
  8. Distributed configuration stores Consul, Etcd, Zookeeper, Vault
  9. Container Scheduler although we do want to deploy to CloudFoundry, OpenStack, OpenShift, Kubernetes, Mesos DCOS, Docker Swarm, Atlas/Terraform, Nomad, Deis, Convox, Flynn, Tutum, GiantSwarm, Rancher
  10. Operating System Ubuntu, CentOS, RHEL, CoreOS, Alpine Linux


From development teams to marketing organizations, everyone needs to collaborate on digital content. Content should be open to suggestions by a wide number of potential contributors. Open contribution can be achieved by using a mergeable file format and distributed version control. The vision of GitLab is to allow everyone to collaborate on all digital content so people can cooperate effectively and achieve better results, faster.

Ideas flow though many stages before they are realized. An idea originates in a chat discussion, an issue is created, it is planned in a sprint, coded in an IDE, committed to version control, tested by CI, code reviewed, deployed, checked and documented. Stitching all these stages of the application lifecycle together can be done in many different ways. You can have a marketplace of proprietary apps from different suppliers or use a suite of products developed in isolation. We believe that an integrated set of tools for application lifecycle management based on convention over configuration offers a superior user experience. The advantage can be quoted from the Wikipedia page for convention over configuration: "decrease the number of decisions that developers need to make, gaining simplicity, and not necessarily losing flexibility". In GitLab you only have to specify unconventional aspects of your workflow. The happy path is frictionless from idea to production.

We admire other convention over configuration tools like Ruby on Rails (that doctrine of which perfectly describe the value of integrated systems), Ember, and Heroku, and strive to offer the same advantages for a continuous delivery of software.

We prefer to offer an integrated set of tools instead of a network of services or offering plugins for the following reasons:

  1. We think an integrated set of tools provides a better user experience than a modular approach, as detailed by this article from Stratechery.
  2. The open source nature of GitLab ensures that that we can combine great open source products.
  3. Everyone can contribute to create a feature set that is more complete than other tools. We'll focus on making all the parts work well together to create a better user experience.
  4. Because GitLab is open source the enhancements can become part of the codebase instead of being external. This ensures the automated tests for all functionality are continually run, ensuring that additions keep working work. This is contrast to externally maintained plugins that might not be updated.
  5. Having the enhancements as part of the codebase also ensures GitLab can continue to evolve with its additions instead of being bound to an API that is hard to change and that resists refactoring. Refactoring is essential to maintaining a codebase that is easy to contribute to.
  6. Many people use GitLab on-premises, for such situations it is much easier to install one tool than installing and integrating many tools.
  7. GitLab is used by many large organizations with complex purchasing processes, having to buy only one subscription simplifies their purchasing.

General Product Strategy

Today you can create an entire product successfully in GitLab, from idea to production. But you still need domain-specific knowledge to be able to set this up and then maintain, monitor and scale this application.

GitLab provides an integrated product for teams of any size with any kind of projects to move faster from idea to production, while giving you actionable feedback, and making shipping products simple.

GitLab's product is opinionated, but still allows you to use other tools if you like to do so. GitLab plays well with others.

Integrated Product

GitLab is an integrated set of tools for conversational development. This offers a superior user experience and lowers the threshold between each step in going from idea to production.

Conversational Development

Conversational development carries a conversation across functional groups through the application lifecycle management, involving gatekeepers at every step. By providing relevant context, a feature that is only possible with an integrated solution like GitLab, we can reduce cycle time, making it easier to diagnose problems and make decisions.

Concretely, conversational development in GitLab means that a change can be easily followed from inception to the changes it made in performance and business metrics and feeding this information back to all stakeholders immediately.

Effectively, this allows cross-functional teams to collaborate effectively.

Idea to Production

GitLab contains all tools needed to bring any project from the ideation stage up to running in production and giving feedback. This includes repositories, issue tracking, CI, CD, monitoring, chat and more. GitLab focuses on lowering the threshold between each step, so that working on a project means focusing on collaboration and not on learning new tools.

External Integrations

GitLab plays well with others. To allow everyone to contribute, it's important that there is only one place where you'll have to look, even if you need to use external tools that are not part of GitLab. For this reason, GitLab plays well with others: Providing APIs for nearly everything you can do within GitLab and powerful, simple authentication and authorization tools for external integrations.

GitLab ships with built-in integrations to many popular applications.

Any Project

GitLab is the tool for anyone working on software in any form.

Multi-repository projects

Software projects are often more than single repositories. GitLab will evolve from being focused around single repositories towards being able to accommodate software projects that consist of multiple repositories.

From scratch or legacy

Starting a project from scratch makes it easy to do everything through GitLab and well integrated. But existing / migrated / legacy projects should benefit from the same features that GitLab offers. GitLab will offer the tools to help you integrate, setup and improve your projects with the tools we have at offer. A concrete example is setting up review apps: everyone would benefit from this. GitLab will give you all the handles to set this up. It should not be required to dive deep in the documentation to discover features like this.

Beyond code

Going from idea to production is not a matter of just code anymore. Modern products work with elaborate mockups and designs both in ideation, but also in production. Whether you’re working on assets in a game or working on the design of a new website, GitLab will allow you to collaborate on your work as a programmer would on their code.

Actionable Feedback

Deployments should never be fire and forget. GitLab will give you immediate feedback on every deployment on any scale. This means that GitLab can tell you whether performance has improved on the application level, but also whether business metrics have changed.

Concretely, we can split up monitoring and feedback efforts within GitLab in three distinct areas: execution (cycle analytics), business and system feedback.

Business feedback

With the power of monitoring and an integrated approach, we have the ability to do amazing things within GitLab. GitLab will be able to automatically test commits and versions through feature flags and A/B testing.

Business feedback exists on different levels:

System feedback

We can now go beyond CI and CD. GitLab will able to tell you whether a change improved performance or stability. Because it will have access to both historical data on performance and code, it can show you the impact of any particular change at any time.

System feedback happens over different time windows:

Execution Feedback & Cycle Analytics

GitLab is able to speed up cycle time for any project. To provide feedback on cycle time GitLab will continue to expand cycle analytics so that it not only shows you what is slow, it’ll help you speed up with concrete, clickable suggestions.

Teams of any Size

GitLab is built to work for teams of any size. By yourself, it gets out of your way and lets you quickly push you work and track your progress.

With a small team, you can easily communicate and quickly move through the otherwise time-intensive steps of bringing a creation to production, with infrastructure as code, a flexible issue tracker and very permissive defaults.

Large teams of thousands of collaborators working on complex projects can easily manage permissions. Automatic and batch actions for getting rolling quickly, up to fine-grained overrides to give certain users specific actions, temporary if needed.

Teams working with external collaborators will find it easy and safe to allow collaborators to work together with them in the same place as the rest of their work, while securing what is not to be shared.

Open source initiatives can use GitLab to effectively collaborate with a community, while having the moderation tools to keep the project clean and focused.

Enterprise Editions

GitLab comes in 3 editions, with Ultimate coming in the future: