GitLab Announces Complete DevOps and Raising $20 Million in New Venture Capital Funding

During a recent GitLab live event, GitLab made several interesting  announcements:

  1. They presented their vision of “Complete DevOps”, and demonstrated capabilities that will soon be incorporated into their product.
  2. They announced that they had raised $20 million in new venture capital funding led by Google Ventures (GV). So far, the total amount of funding raised by GitLab exceeds $45 million.
  3. Matt Mullenweg, the founder of WordPress, has joined the GitLab board.

The full recording of the event is below:

Now for some more details about these announcements:

Complete DevOps vision and future product capabilities


Sid Sijbrandij, the CEO of GitLab, presented the vision of Complete DevOps (expected to be completed during 2018).  The idea is to include both developers and operations teams in one unified solution. Currently, GitLab covers (almost) every stage from idea to production. However, after a product reaches the production stage, there are still operations, and now GitLab intends to add capabilities that would support that stage too. As a result, GitLab will become a complete DevOps tool chain.

As a result, the following features will be added to GitLab during the next 6 months

  • Real-time editing of issues, merge requests and files, which shows in real-time who is currently changing the text (similar to Google Docs and Office 365) . See slide 40 in the upcoming presentation.
  • Portfolio management, including GANTT charts (slides 42-43).
  • Web IDE, which lets you write code on any device, without the need for an IDE client’s installation (slide 46).
  • Performance testing and security scanning will be included in the CI component (slides 49-50).
  • Improved Container Registry capabilities. You can already use the Container Registry to pack your product into a Docker container (slide 53).
  • Binary Repository for management of binary files (slide 54).
  • GitLab Tracing allows you to display traces of GitLab’s microservices (slide 71).
  • Auto Alerts: automatic detection and alerting of system anomalies (slide 72).
  • Ops View: An overview of all the production apps with the option to zero in on individual apps. (slide 73).
  • Auto Log automatically gathers and searches the logs of applications that are deployed by GitLab (slide 74).

and much more…

How to Select the GitLab Version that Suits Your Needs

GitLab users often ask us which GitLab version to select. No wonder: today there are essentially 10 (!) options (cloud, on-premise etc.), and the choice can be quite confusing.

The purpose of this article is to help you to choose the right version of GitLab.

So how do you choose?

To make it simple, let’s split the decision process into two steps:

  1. First, decide whether you want your GitLab in-house behind your firewall (on-premise), on their public cloud (gitlab.com) or on a private cloud. The private cloud option, which we provide, is actually a private server on the cloud, and it offers the best of both worlds: On one hand, there is no need for IT or physical server maintenance; on the other hand, you use your own server , giving you full control and many more advantages.
  2. Next you have to decide whether the free version (“Community Edition”) is good enough for you, or if you need one of the paid (Enterprise) options.