Merge pull request 'feature matrix price plans, survey' (#2) from introduction into main
Reviewed-on: #2pull/20/head
commit
c3f60ec727
|
|
@ -7,6 +7,8 @@
|
|||
\usepackage{multicol}[]
|
||||
\usepackage{blindtext}
|
||||
\usepackage{float}
|
||||
\usepackage{booktabs}
|
||||
\usepackage{makecell}
|
||||
|
||||
\usepackage{fancyhdr}
|
||||
\usepackage{geometry}
|
||||
|
|
@ -15,6 +17,8 @@
|
|||
\usepackage{acronym}
|
||||
\usepackage{hyperref}
|
||||
|
||||
\usepackage{amsmath}
|
||||
|
||||
\usepackage{biblatex}
|
||||
|
||||
\graphicspath{ {./bilder/} }
|
||||
|
|
@ -23,7 +27,7 @@
|
|||
a4paper,margin=25mm
|
||||
}
|
||||
|
||||
\title{\huge{Dev Ops mit Microservices - Gitlab}}
|
||||
\title{\huge{Dev Ops mit Microservices - GitLab}}
|
||||
\date{\today}
|
||||
\author{
|
||||
\begin{tabular}{ccc}
|
||||
|
|
@ -41,7 +45,7 @@
|
|||
\pagestyle{fancy}
|
||||
%... then configure it.
|
||||
\fancyhead{} % clear all header fields
|
||||
\fancyhead[L]{Gitlab}
|
||||
\fancyhead[L]{GitLab}
|
||||
\fancyhead[R]{DMS - DevOps mit Micro Services}
|
||||
\fancyfoot{} % clear all footer fields
|
||||
\fancyfoot[LE,RO]{\thepage}
|
||||
|
|
@ -59,48 +63,94 @@
|
|||
\tableofcontents
|
||||
|
||||
\section{Einleitung}
|
||||
|
||||
\subsection{Motivation}
|
||||
|
||||
\textbf{\ac{CI}} ist eine Methodik zur Softwareentwicklung. Ziele der Vorgehensweise sind die Erstellung von qualitativen Quellcode, durch stetiges Überprüfen der Funktionalität des verfassten Code. Der Entwicklungsstand einer Software liegt innerhalb des sogenannten Hauptzweiges. Entwickler nehmen fortlaufend kleinere Änderungen vor und bauen diese innerhalb kurzen Entwicklungszyklen in den Hauptzweig ein. Der Entwickler stellt eine Anfrage, ob sein Code in den Hauptzweig aufgenommen werden kann (Pull Request). Damit eine korrekte Funktionsweise des Hauptzweiges sichergestellt werden kann, wird jeweils eine Reihe an Tests durchgeführt. Schlagen diese Tests fehl, so muss der Entwickler seine Änderungen ausbessern und den Prozess erneut anstossen und wiederholt diesen Schritt solange bis die Tests erfolgreich sind. Die Änderungen können somit in den Hauptzweig übernommen werden (Merge).
|
||||
Häufig findet \ac{CI} in Kombination mit agiler Projektmethodik statt. \cite{arefeen_continuous_2019}.\\
|
||||
\textbf{\ac{CD}} beschreibt den durch \ac{CI} notwendigen Aspekt der Automatisierung. Eine manuelle Durchführung der Tests benötigt einen höheren zeitlichen Aufwand und kann fehlerhaft durchgeführt werden. Zu den Vorteilen von \ac{CI}/\ac{CD} zählen eine frühe Fehlererkennung und schnellere Entwicklungszyklen.
|
||||
GitLab ist eine Plattform, die es ermöglicht \ac{CI}/\ac{CD} in Verbindung mit agiler Entwicklung umzusetzen.
|
||||
Nach der jährlichen Entwicklerumfrage von Stack Overflow, ist GitLab, mit 35.6 \%, neben GitHub, mit 81.8 \%, und Jira, mit 46.4 \% eine der meistgenutzten Plattformen zur Dokumentation und zur kollaborativen Zusammenarbeit an Code \cite{2025StackOverflow}. Siehe \ref{fig:stackoverflow-devsurvey-tools}
|
||||
\begin{figure}[H]
|
||||
\includegraphics[width=\linewidth]{bilder/stack_overflow_developer_survey_collab_tools_documentation.png}
|
||||
\caption{Auswahl der 10 meist verwendeten Dokumentations- und Kollaborations Werkzeuge nach Stack Overflow Survey 2025 \cite{2025StackOverflow}}
|
||||
\label{fig:stackoverflow-devsurvey-tools}
|
||||
\end{figure}
|
||||
Diese wissenschaftliche Ausarbeitung beschäftigt sich damit, inwiefern sich die von GitLab v18.11 bereitgestellten Werkzeuge bzw. Möglichkeiten eignen um eine beispielhafte Anwendung zu entwickeln, zu testen und einzusetzen. Ebenso wird betrachtet in welchen Punkten sich die Implementierung von \ac{CI}/\ac{CD} in GitLab zu seinem Mitstreiter GitHub unterscheidet.
|
||||
\subsection{Softwarelösung}
|
||||
Gitlab ist eine mit Git kompatible Plattform für Code-Hosting. Der Code von Gitlab ist in Ruby verfasst \cite{degeler_gitlab_2014}. Unter der Haube verwendet Git die relationale Datenbank PostgreSQL. Auf Gitlab kann mithilfe einer Weboberfläche zugegriffen werden \cite{gitlab_about}:
|
||||
Gitlab kann in folgenden unterschiedlichen Formen genutzt werden:
|
||||
GitLab ist eine mit Git kompatible Plattform für Code-Hosting. Der Code von GitLab ist in Ruby verfasst \cite{degeler_gitlab_2014}. Unter der Haube verwendet Git die relationale Datenbank PostgreSQL. Auf GitLab kann mithilfe einer Weboberfläche zugegriffen werden \cite{gitlab_about}:
|
||||
GitLab kann in folgenden unterschiedlichen Formen genutzt werden:
|
||||
|
||||
\begin{itemize}
|
||||
\item \textbf{\ac{SaaS}} Die Plattform wird innerhalb der Cloud von Gitlab gehostet.
|
||||
\item \textbf{Selbst gehostet} Gitlab kann auf linux-basierten Servern selbst betrieben werden.
|
||||
\item \textbf{Dediziertes \ac{SaaS}} Für Unternehmen und Regierungen kann Gitlab in eigenen isolierten Instanzen verwendet werden, um hohe Sicherheitsstandards zu gewährleisten.
|
||||
\end{itemize}
|
||||
\item \textbf{\ac{SaaS}} Die Plattform wird innerhalb der Cloud von GitLab gehostet. Die Arbeit mit GitLab kann sofort gestartet werden.
|
||||
\item \textbf{Selbst gehostet} GitLab kann auf linux-basierten Servern selbst betrieben werden. Installation, Konfiguration und Administration der Infrastruktur muss selbst übernommen werden.
|
||||
\item \textbf{Dediziertes \ac{SaaS}} Für Unternehmen und Regierungen kann GitLab in eigenen isolierten Instanzen verwendet werden, um hohe Sicherheitsstandards und gesetzliche Regulierungen zu gewährleisten.
|
||||
\end{itemize}
|
||||
|
||||
Für die \ac{SaaS}- und die selbst gehostete Variante von GitLab gibt es drei unterschiedliche Preispläne: Free, Premium und Ultimate. Tabelle \ref{tab:saas_plans} zeigt eine Auswahl an Funktionalitäten und deren Verfügbarkeit nach Preisplan. In der selbst gehosteten Variante von GitLab sind die technischen Limitierungen Nutzeranzahl, Rechnungszeit und Speicher von der Bereitstellung eigener Serverkapazitäten abhängig. Die Verfügbarkeit der restlichen Funktionalitäten ist analog.
|
||||
\begin{table}[H]
|
||||
\begin{tabular}{@{}llll@{}}
|
||||
\toprule
|
||||
& \multicolumn{3}{c}{Verfügbarkkeit} \\ \midrule
|
||||
Preisplan & Free & Premium & Ultimate \\ \midrule
|
||||
Nutzerzahl & 5 & $\infty$ & $\infty$ \\
|
||||
\makecell[cl]{Rechnungs-\\zeit} & 400 min & 10000 min & 50000 min \\
|
||||
Speicher & 10 GiB & 500 GiB & 500 GiB\\\midrule
|
||||
\ac{CI}/\ac{CD} & X & X & X\\
|
||||
\makecell[cl]{Container-\\Scan} & X & X & X\\
|
||||
Web \acs{IDE} & - & X & X\\
|
||||
Pushregeln & - & X & X\\
|
||||
\makecell[cl]{Integrierte\\Testfälle} & - & - & X\\ \midrule
|
||||
\makecell[cl]{Zeitracking} & X & X & X\\
|
||||
Wikis & X & X & X\\
|
||||
\makecell[cl]{Issue-\\Gewichte} & - & X & X\\
|
||||
\makecell[cl]{Projekt-\\analyse} & - & X & X\\
|
||||
\makecell[cl]{Statusseite} & - & - & X\\
|
||||
\midrule
|
||||
Preis & 0\texteuro & \makecell[cl]{29\texteuro je$\frac{\text{Nutzer}}{\text{Monat}}$} & \makecell[cl]{kunden-\\spezifisch}\\ \bottomrule
|
||||
\end{tabular}
|
||||
\caption{Auswahl an Funktionalitäten und deren Verfügbarkeit, nach Preisplan \cite{gitlab_about}}
|
||||
\label{tab:saas_plans}
|
||||
\end{table}
|
||||
|
||||
|
||||
|
||||
|
||||
\subsection{Geschichte}
|
||||
|
||||
Gitlab wurde von Sytse Sijbrandij und von Dmitriy Zaporozhets gegründet. Zaporozhets entwickelte Gitlab 2011 als Hilfsmittel für seine eigenen Projekte. Gitlab war zu dem Zeitpunkt eine private und freie Plattform zum eigenen Code-Hosting, entwickelt von Zaporozhets. Nachdem Zaporozhets sich entschied den Quellcode von Gitlab frei zugänglich zu machen, entstand die Partnerschaft mit Sijbrandij. Um den Einstieg in die Nutzung von Gitlab zu erleichtern entschieden sich Sijbrandij GitLab als \ac{SaaS} unter der Domain \url{https://gitlab.com/} anzubieten. Der Quellcode von Gitlab ist frei unter \url{https://gitlab.com/gitlab-org/gitlab} verfügbar \cite{degeler_gitlab_2014}. 2014 wurde Gitlab erstmalig als Unternehmen eingetragen und erfuhr seitdem einen grossen Zuwachs an Mitarbeitern. Aktuell zählt Gitlab mehr als 2600 Mitarbeiter, die über 65 Länder verteilt leben \cite{gitlab_about}. Gitlab selbst besitzt keinen ausgebauten Firmenhauptsitz, da Mitarbeiter hauptsächlich remote arbeiten und freie Verfügung über ihre Arbeitszeit haben \cite{choudhuryGitLabWorkWhere2020}. Gitlab finanziert sich durch Spenden um neue Funktionalitäten zu realisieren. Ein weiterer Teil der Einnahmen kommt durch den Abschluss von Abonnements der Enterprise-Edition \cite{degeler_gitlab_2014}.
|
||||
Abbildung \ref{fig:gitlab-logo} zeigt das Logo von Gitlab. Es besteht aus einem Tanuki, einem in Japan heimischen Waschbärhund, und dem Gitlab Schriftzug.
|
||||
GitLab wurde von Sytse Sijbrandij und von Dmitriy Zaporozhets gegründet. Zaporozhets entwickelte GitLab 2011 als Hilfsmittel für seine eigenen Projekte. GitLab war zu dem Zeitpunkt eine private und freie Plattform zum eigenen Code-Hosting, entwickelt von Zaporozhets. Zaporozhets und Sijbrandij lernten sich auf der \href{https://thenextweb.com/conference}{The Next Web} Konferenz kennen. Nachdem Zaporozhets sich entschied den Quellcode von GitLab frei zugänglich zu machen, entstand die Partnerschaft mit Sijbrandij. Um den Einstieg in die Nutzung von GitLab zu erleichtern entschieden sich Sijbrandij GitLab als \ac{SaaS} unter der Domain \url{https://gitlab.com/} anzubieten. Der Quellcode von GitLab ist frei unter \url{https://gitlab.com/gitlab-org/gitlab} verfügbar \cite{degeler_gitlab_2014}. Der Quellcode des Konkurrenten GitHub ist nicht frei zugänglich. 2014 wurde GitLab erstmalig als Unternehmen eingetragen und erfuhr seitdem einen grossen Zuwachs an Mitarbeitern. Aktuell zählt GitLab mehr als 2600 Mitarbeiter, die über 65 Länder verteilt leben \cite{gitlab_about}. GitLab selbst besitzt keinen grossen ausgebauten Firmenhauptsitz, da Mitarbeiter hauptsächlich remote arbeiten und freie Verfügung über ihre Arbeitszeit besitzen. Der organisatorische Aufbau und der Ablauf interner Prozesse von GitLab, können in dem von GitLab öffentlichem Handbuch \url{https://handbook.gitlab.com/} nachgelesen werden \cite{choudhuryGitLabWorkWhere2020}.
|
||||
GitLab finanziert sich durch Spenden um neue Funktionalitäten zu realisieren. Ein weiterer Teil der Einnahmen kommt durch den Abschluss von kostenpflichtiger Abonnements. \cite{degeler_gitlab_2014}.
|
||||
Abbildung \ref{fig:gitlablogo} zeigt das Logo von GitLab. Es besteht aus einem Tanuki, einem in Japan heimischen Waschbärhund, und dem GitLab Schriftzug.
|
||||
\begin{figure}[H]
|
||||
\centering
|
||||
\includegraphics[width=0.8\linewidth]{./bilder/gitlab-logo-100-rgb.png}
|
||||
\label{fig:gitlab-logo}
|
||||
\caption{Logo Gitlab}
|
||||
\caption{Logo GitLab}
|
||||
\label{fig:gitlablogo}
|
||||
\end{figure}
|
||||
Gitlab erregte in mehreren Fällen mediale Aufmerksamkeit auf sich. 2017 verlor die \ac{SaaS}-Lösung von Gitlab sechs Stunden an Nutzerdaten, aufgrund von einer menschlichen Fehlreaktion, ausgelöst durch Spamanfragen die in Problemen mit der Datenbank resultierten \cite{GitLabcomDatabaseIncident}. Ebenso bestanden 2022 Pläne inaktive Repositories löschen. Nach starker Kritik wurde sich dazu entschieden, anstatt zu löschen, zu archivieren \cite{onlineVersionsverwaltungGitLabRudert2022}.
|
||||
GitLab erregte in mehreren Fällen mediale Aufmerksamkeit auf sich. 2017 verlor die \ac{SaaS}-Lösung von GitLab sechs Stunden an Nutzerdaten, aufgrund von einer menschlichen Fehlreaktion, ausgelöst durch Spamanfragen die in Problemen mit der Datenbank resultierten \cite{GitLabcomDatabaseIncident}. GitLab wagte im Oktober 2021 den Gang an die Börse und ist aktuell als Aktie im \ac{NASDAQ} unter dem Kürzel: GTLB erhältlich \cite{teamGitLabIncGTLB}.
|
||||
Ebenso bestanden 2022 Pläne inaktive Repositories löschen. Nach starker Kritik wurde sich dazu entschieden, anstatt zu löschen, zu archivieren \cite{onlineVersionsverwaltungGitLabRudert2022}.
|
||||
|
||||
\subsection{Aufbau}
|
||||
|
||||
Zusammenarbeit in Gitlab ist in Form von Gruppen organisiert. Diese können in Subgruppen unterteilt werden. Gruppen und Subgruppen können Projekte und Mitarbeiter zugeordnet werden.
|
||||
Zusammenarbeit in GitLab ist in Form von Gruppen organisiert. Diese können in Subgruppen unterteilt werden. Gruppen und Subgruppen können Projekte und Mitarbeiter zugeordnet werden.
|
||||
Jedes Projekt besteht aus einer Issue-Seite, einem Wiki und einem Code-Repository. \cite{gitlab_gitlab_nodate}
|
||||
|
||||
% Vergleich von Features mit Github möglich
|
||||
% Vergleich von Features mit möglich
|
||||
|
||||
\subsection{Funktionalitäten}
|
||||
|
||||
|
||||
|
||||
|
||||
\section{CI/CD}
|
||||
|
||||
%https://docs.gitlab.com/topics/build_your_application/
|
||||
\subsection{Einführung}
|
||||
\subsection{Gitlab Runner}
|
||||
|
||||
\subsection{GitLab Runner}
|
||||
\subsection{Pipelines}
|
||||
\subsection{Jobs}
|
||||
\subsection{CICD-Komponenten}
|
||||
\subsection{GitLab vs. GitHub}
|
||||
|
||||
\section{Anwendungsbeispiel}
|
||||
|
||||
|
|
@ -124,20 +174,20 @@
|
|||
|
||||
|
||||
\section{Diskussion}
|
||||
\ac{CI/CD}
|
||||
|
||||
\section{Ausblick}
|
||||
|
||||
\section{Zusammenfassung}
|
||||
|
||||
|
||||
Hallo Welt \cite{arefeen_continuous_2019}
|
||||
\subsection{Geschichte}
|
||||
|
||||
\section*{Abkürzungsverzeichnis}
|
||||
\begin{acronym}[Abkürzungsverzeichnis]
|
||||
\acro{CI/CD}{Continuous Integration/Continous Delivery}
|
||||
\acro{IDE}{Integrated Development Environment}
|
||||
\acro{CD}{Continous Delivery, kontinuierliche Auslieferung}
|
||||
\acro{SaaS}{Software as a Service}
|
||||
\acro{CI}{Continuous Integration, kontinuierliche Integration}
|
||||
\acro{NASDAQ}{National Association of Securities Dealers Automated Quotations}
|
||||
\end{acronym}
|
||||
|
||||
\printbibliography
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
|
|
@ -89,3 +89,394 @@
|
|||
year = {2022},
|
||||
file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\3N8Y75DY\\Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html:text/html},
|
||||
}
|
||||
|
||||
@inproceedings{fairbanksAnalyzingEffectsCI2023,
|
||||
title = {Analyzing the {Effects} of {CI}/{CD} on {Open} {Source} {Repositories} in {GitHub} and {GitLab}},
|
||||
issn = {2770-8209},
|
||||
url = {https://ieeexplore.ieee.org/document/10197778/},
|
||||
doi = {10.1109/SERA57763.2023.10197778},
|
||||
abstract = {Numerous articles emphasize the benefits of implementing Continuous Integration and Delivery (CI/CD) pipelines in software development. These pipelines are expected to improve a project’s reputation and decrease the number of commits and issues in the repository. Although CI/CD adoption may be slow initially, it is believed to accelerate service delivery and deployment in the long run. This study aims to investigate the impact of CI/CD on commit velocity and issue counts in two open-source repositories, GitLab and GitHub. By analyzing more than 12,000 repositories and recording every commit and issue, it was discovered that CI/CD enhances commit velocity by 141.19\% but also increases the number of issues by 321.21\%.},
|
||||
urldate = {2026-04-17},
|
||||
booktitle = {2023 {IEEE}/{ACIS} 21st {International} {Conference} on {Software} {Engineering} {Research}, {Management} and {Applications} ({SERA})},
|
||||
author = {Fairbanks, Jeffrey and Tharigonda, Akshharaa and Eisty, Nasir U.},
|
||||
month = may,
|
||||
year = {2023},
|
||||
note = {ISSN: 2770-8209},
|
||||
keywords = {Software, CI/CD, Codes, Mining Repositories, Open-Source Software, Pipelines, Recording, Software development management, Software engineering, Software Engineering},
|
||||
pages = {176--181},
|
||||
file = {Full Text PDF:C\:\\Users\\Roman\\Zotero\\storage\\EW4K6L72\\Fairbanks et al. - 2023 - Analyzing the Effects of CICD on Open Source Repositories in GitHub and GitLab.pdf:application/pdf},
|
||||
}
|
||||
|
||||
@misc{2025StackOverflow,
|
||||
title = {2025 {Stack} {Overflow} {Developer} {Survey}},
|
||||
url = {https://survey.stackoverflow.co/2025/},
|
||||
abstract = {The 2025 Developer Survey is the definitive report on the state of software development. In its fifteenth year, Stack Overflow received over 49,000+ responses from 177 countries across 62 questions focused on 314 different technologies, including new focus on AI agent tools, LLMs and community platforms. This annual Developer Survey provides a crucial snapshot into the needs of the global developer community, focusing on the tools and technologies they use or want to learn more about.},
|
||||
language = {en},
|
||||
urldate = {2026-04-18},
|
||||
file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\VL48NTTS\\2025.html:text/html},
|
||||
}
|
||||
|
||||
@misc{teamGitLabIncGTLB,
|
||||
title = {{GitLab} {Inc}. ({GTLB}): {History}, {Ownership}, {Mission}, {How} {It} {Works} \& {Makes} {Money}},
|
||||
shorttitle = {{GitLab} {Inc}. ({GTLB})},
|
||||
url = {https://dcfmodeling.com/blogs/history/gtlb-history-mission-ownership},
|
||||
abstract = {With GitLab Inc. (GTLB) reporting a full fiscal year 2025 revenue of over \$759.2 million, up 31\% year-over-year, do you defintely understand how this all-remote powerhouse built the most comprehensive DevSecOps platform?
|
||||
The company's shift to an AI-powered platform is clearly paying off, evidenced by the 29\% year-over-year growth in customers spending over \$100,000 in Annual Recurring Revenue (ARR), but what does its open-source mission-to empower everyone to contribute-really mean for its valuation?
|
||||
You need to see the full picture, from its mixed ownership structure, which includes institutional giants like BlackRock, to the mechanics of how its single-application model actually makes money, so let's break down the history and the financial engine that drives it.
|
||||
GitLab Inc. (GTLB) History
|
||||
You want to understand how GitLab Inc. went from a side project to a DevSecOps powerhouse, and honestly, the journey is a masterclass in open-source monetization and strategic focus. The direct takeaway is that two key decisions-going all-remote and committing to a single-application DevSecOps platform-are responsible for its current scale, which saw it achieve \$759.2 million in revenue for its fiscal year 2025.
|
||||
|
||||
GitLab Inc.'s Founding Timeline
|
||||
Year established
|
||||
The original open-source project was established in 2011 by Dmytro Zaporozhets. GitLab Inc., the company, was formally incorporated in September 2014, moving the project from a community effort to a commercial venture.
|
||||
|
||||
Original location
|
||||
The first version of the software was created by Dmytro Zaporozhets from his home in Ukraine. The company later established its headquarters in San Francisco, United States, but famously maintained its all-remote structure from the start.
|
||||
|
||||
Founding team members
|
||||
The project's creator was Dmytro Zaporozhets, a Ukrainian developer. The co-founder who joined in 2012 to build a business around the open-source code was Sytse 'Sid' Sijbrandij, a Dutch developer who would become the company's long-time CEO.
|
||||
|
||||
Initial capital/funding
|
||||
The project was initially bootstrapped, meaning it was self-funded and grew organically without external capital. The first significant funding came in 2015, with a \$1.5 million seed round, followed by a \$4 million Series A round from Khosla Ventures later that year.
|
||||
|
||||
GitLab Inc.'s Evolution Milestones
|
||||
|
||||
|
||||
|
||||
Year
|
||||
Key Event
|
||||
Significance
|
||||
|
||||
|
||||
|
||||
|
||||
2011
|
||||
Initial Open-Source Creation
|
||||
Ukrainian developer Dmytro Zaporozhets created the first version as a side project, establishing the open-source foundation.
|
||||
|
||||
|
||||
2014
|
||||
GitLab Inc. Incorporation
|
||||
Sytse Sijbrandij formalized the business, leading to the creation of the all-remote company and the adoption of the open-core business model.
|
||||
|
||||
|
||||
2016
|
||||
Shift to Single-Application DevOps
|
||||
A critical pivot from being just a Git repository manager to a comprehensive DevOps platform, integrating Continuous Integration/Continuous Delivery (CI/CD).
|
||||
|
||||
|
||||
2018
|
||||
Achieved Unicorn Status
|
||||
Raised \$100 million in Series D funding, valuing the company at \$1.1 billion, validating its expansive DevSecOps strategy.
|
||||
|
||||
|
||||
2021
|
||||
Initial Public Offering (IPO)
|
||||
Began trading on the NASDAQ under the ticker GTLB on October 14, 2021, marking a major financial milestone and liquidity event.
|
||||
|
||||
|
||||
FY 2025
|
||||
Revenue Surpasses \$750M
|
||||
Reported full fiscal year revenue of \$759.2 million, a 31\% year-over-year increase, showing strong enterprise adoption.
|
||||
|
||||
|
||||
|
||||
|
||||
GitLab Inc.'s Transformative Moments
|
||||
The company's trajectory wasn't just about incremental growth; it was shaped by a few defintely bold, high-stakes decisions that changed its market position.
|
||||
|
||||
|
||||
The Single-Application Vision: Moving beyond simple Git repository management to offer a complete DevSecOps platform in a single application was a game-changer. This integration of development, security, and operations tools reduced the common problem of tool sprawl for customers and became a core differentiator.
|
||||
|
||||
The All-Remote Mandate: The decision to operate as a fully remote company from its inception allowed GitLab Inc. to hire top talent globally, lower overhead costs, and build a unique, highly transparent culture documented in its public handbook. This model proved to be a massive competitive advantage, especially post-2020.
|
||||
|
||||
Embracing AI-Native Capabilities: The strategic focus in fiscal year 2025 on AI/ML integration, particularly with the launch of the GitLab Duo features, is the latest transformative move. This shift is designed to automate workflows and boost developer productivity by an estimated 40-50\% for early adopters, positioning the platform for the next wave of software development.
|
||||
|
||||
This relentless focus on a single, integrated platform has been key to expanding its enterprise customer base, where customers with more than \$1 million in Annual Recurring Revenue (ARR) grew to 123 in FY 2025. You can dig deeper into the financial mechanics of this growth by Breaking Down GitLab Inc. (GTLB) Financial Health: Key Insights for Investors.
|
||||
GitLab Inc. (GTLB) Ownership Structure
|
||||
GitLab Inc. (GTLB) operates with a highly concentrated ownership structure, where institutional investors hold the vast majority of the company's shares, a common trait for high-growth, publicly-traded software companies.
|
||||
This structure means that while co-founder influence is still present, the company's stock price and strategic direction are defintely heavily influenced by the trading decisions of large asset managers like BlackRock and Vanguard Group Inc.
|
||||
|
||||
Given Company's Current Status
|
||||
GitLab Inc. is a publicly traded company on the NASDAQ Global Select Market under the ticker symbol GTLB. It completed its initial public offering (IPO) in October 2021.
|
||||
As of November 2025, the company maintains a significant market capitalization, which was approximately \$7.39 billion just prior to its Q3 Fiscal Year 2026 earnings release, reflecting its standing as a leader in the DevSecOps platform space.
|
||||
|
||||
Given Company's Ownership Breakdown
|
||||
The company's ownership profile is dominated by institutional capital, which provides both stability and a strong mandate for financial performance. This is a crucial detail for any investor Exploring GitLab Inc. (GTLB) Investor Profile: Who's Buying and Why?.
|
||||
Here is the breakdown of the common stock ownership as of the most recent filings near November 2025, based on the total shares outstanding.
|
||||
|
||||
|
||||
|
||||
Shareholder Type
|
||||
Ownership, \%
|
||||
Notes
|
||||
|
||||
|
||||
|
||||
|
||||
Institutional Investors
|
||||
88.72\%
|
||||
Includes major asset managers like Vanguard Group Inc. (holding {\textasciitilde}9.16\%) and BlackRock, Inc. (holding {\textasciitilde}4.89\%).
|
||||
|
||||
|
||||
Insider Ownership
|
||||
3.75\%
|
||||
Represents shares held by executives and board members, including co-founder Sytse Sijbrandij.
|
||||
|
||||
|
||||
Retail/Individual Investors
|
||||
7.53\%
|
||||
This is the remaining float, calculated as 100\% minus the institutional and insider holdings.
|
||||
|
||||
|
||||
|
||||
Here's the quick math: when nearly 90\% of the stock is in the hands of institutions, their collective buying or selling can move the share price quickly, so tracking their 13F filings is a must.
|
||||
|
||||
Given Company's Leadership
|
||||
The management team steering GitLab Inc. is a blend of long-time leaders and recent strategic hires, reflecting the company's focus on scaling its DevSecOps platform and integrating artificial intelligence (AI) capabilities.
|
||||
The executive leadership team, as of November 2025, includes:
|
||||
|
||||
|
||||
Bill Staples: Chief Executive Officer (CEO).
|
||||
|
||||
James Shen: Interim Chief Financial Officer (CFO). He was appointed to this role in September 2025 following the departure of Brian Robins.
|
||||
|
||||
Manav Khurana: Chief Product and Marketing Officer.
|
||||
|
||||
Sabrina Farmer: Chief Technology Officer (CTO).
|
||||
|
||||
Ian Steward: Chief Revenue Officer (CRO).
|
||||
|
||||
Manu Narayan: Chief Information Officer (CIO).
|
||||
|
||||
The recent appointment of an Interim CFO in September 2025 shows a focus on maintaining financial stability during a transition, which is typical when a key executive departs for a competitor like Snowflake. Interim appointments like this signal that the board is taking its time to find a long-term fit to drive the next phase of sustainable growth and profitability.
|
||||
GitLab Inc. (GTLB) Mission and Values
|
||||
GitLab Inc.'s purpose extends beyond its impressive financial metrics-like the \$759.2 million in revenue for fiscal year 2025-by focusing on a deeply collaborative and transparent culture that fundamentally changes how software is created. This cultural DNA, built on six core values, is what drives their platform-first strategy and their commitment to open contribution.
|
||||
|
||||
GitLab Inc.'s Core Purpose
|
||||
You're looking for a company that stands on solid ground, and for GitLab Inc., that foundation is their mission to make all creative work accessible and modifiable, not just read-only. This is a powerful, almost philosophical stance for a software company, and it directly translates into their open-core business model (offering a free, open-source version alongside paid tiers).
|
||||
|
||||
Official Mission Statement
|
||||
The company's mission is simple but ambitious: to enable everyone to contribute to and co-create the software that powers our world. This isn't just about code; it's about breaking down the barriers between development, security, and operations (DevSecOps) teams, plus all the other stakeholders.
|
||||
|
||||
Enable everyone to contribute to and co-create the software that powers our world.
|
||||
|
||||
|
||||
Vision Statement
|
||||
Their vision is a clear roadmap for achieving that mission, aiming to be the singular platform that facilitates global digital transformation. Honestly, a single, integrated platform is what enterprises are demanding right now to cut down on tool sprawl and complexity.
|
||||
|
||||
Be the platform that empowers everyone to contribute to all digital transformation.
|
||||
|
||||
|
||||
GitLab Inc. Slogan/Tagline
|
||||
While they don't use a punchy, one-word slogan, their positioning is crystal clear, especially as they integrate more artificial intelligence (AI) into their offerings, which is a key growth driver for the business. This focus helped them generate \$120.0 million in Non-GAAP Adjusted Free Cash Flow in FY2025.
|
||||
|
||||
The most comprehensive AI-powered DevSecOps platform for software innovation.
|
||||
Start shipping better software faster.
|
||||
|
||||
|
||||
Core Values (CREDIT)
|
||||
GitLab Inc. is famously an all-remote company, and their six core values-which conveniently spell out CREDIT-act as a distributed decision-making framework for their global workforce. This level of transparency is defintely rare, with over 5,000 pages of their internal processes being public. You can see how these values directly support their mission.
|
||||
|
||||
|
||||
Collaboration: Prioritizing asynchronous communication and assuming good intent.
|
||||
|
||||
Results: Focusing on output and measurable business outcomes.
|
||||
|
||||
Efficiency: Working smarter, not just harder, to deliver value quickly.
|
||||
|
||||
Diversity, Inclusion \& Belonging (DIB): A commitment to a global, all-remote team.
|
||||
|
||||
Iteration: Doing the smallest thing possible and shipping it quickly; small, continuous improvements.
|
||||
|
||||
Transparency: Making information public by default, which builds trust with users and investors.
|
||||
|
||||
For a deeper dive into how these principles underpin their financial performance, check out Breaking Down GitLab Inc. (GTLB) Financial Health: Key Insights for Investors.
|
||||
GitLab Inc. (GTLB) How It Works
|
||||
GitLab Inc. operates by delivering the most comprehensive, AI-powered DevSecOps platform as a single application, allowing software teams to manage the entire software development lifecycle-from planning code to deployment and monitoring-in one place. This unified approach eliminates the friction and security gaps that come from stitching together disparate, best-of-breed tools, helping organizations ship more secure software faster.
|
||||
|
||||
GitLab Inc.'s Product/Service Portfolio
|
||||
The company's offerings are structured around a tiered, subscription-based model that scales with the size and complexity of the customer's needs, driving revenue growth through a clear 'land and expand' strategy. For the fiscal year 2025, this strategy helped drive total revenue to \$759.2 million.
|
||||
|
||||
|
||||
|
||||
|
||||
Product/Service
|
||||
Target Market
|
||||
Key Features
|
||||
|
||||
|
||||
|
||||
|
||||
Free/Community Edition
|
||||
Individual Developers, Small Teams, Open Source Projects
|
||||
Core Git repository management, basic CI/CD (Continuous Integration/Continuous Delivery), and issue tracking. It is the foundation of the open-core model.
|
||||
|
||||
|
||||
Premium
|
||||
Mid-Market \& Scaling Teams (e.g., 9,893 customers with {\textgreater}\$5K ARR)
|
||||
Enhanced workflow management, enterprise-grade support (24/7), advanced CI/CD features, and compliance controls. Focuses on improving team efficiency and collaboration.
|
||||
|
||||
|
||||
Ultimate (including GitLab Duo)
|
||||
Large Enterprises \& Highly Regulated Industries (e.g., 1,229 customers with {\textgreater}\$100K ARR)
|
||||
Full DevSecOps capabilities: Advanced security testing (SAST, DAST), compliance, portfolio management, and GitLab Duo (AI-powered code generation and assistance).
|
||||
|
||||
|
||||
|
||||
|
||||
GitLab Inc.'s Operational Framework
|
||||
GitLab's operational framework is built on a few core principles that translate directly into value creation for customers. Honestly, it's all about consolidation and efficiency. They are the only cloud-agnostic, model-neutral DevSecOps platform, meaning you can run it anywhere, which is a huge draw for large companies.
|
||||
The company's revenue growth, which hit 31\% for FY 2025, is primarily driven by this 'land and expand' motion, where customers start with lower tiers and expand to Premium or Ultimate as they consolidate their toolchains.
|
||||
|
||||
|
||||
Single Application Approach: Instead of integrating 10+ disparate tools for planning, coding, testing, securing, and deploying, GitLab provides a single codebase and unified data model. This cuts down on integration costs and context switching for developers.
|
||||
|
||||
Open-Core Business Model: The free, open-source Community Edition drives widespread adoption and a massive user base (over 50 million registered users), which acts as a powerful top-of-funnel for their paid Premium and Ultimate subscriptions.
|
||||
|
||||
AI-Driven Development: A key FY25 investment theme was enabling AI/ML efficiencies across DevSecOps, with GitLab Duo moving from 'AI-assisted' to 'AI-driven' to boost developer productivity and ensure security and compliance for AI-generated code.
|
||||
|
||||
You can see how this operational focus aligns with their core beliefs: Mission Statement, Vision, \& Core Values of GitLab Inc. (GTLB).
|
||||
|
||||
GitLab Inc.'s Strategic Advantages
|
||||
The company's market success comes down to three clear advantages: platform completeness, a superior economic model, and their commitment to AI-native security. What this estimate hides, though, is the intense competition from Microsoft's GitHub, still the primary risk.
|
||||
|
||||
|
||||
Toolchain Consolidation: The single DevSecOps platform is a major differentiator against competitors like Microsoft Corporation's GitHub, which often requires users to integrate third-party tools for security and operations. This consolidation saves time and money for enterprise customers.
|
||||
|
||||
Exceptional Unit Economics: GitLab maintains a very high gross profit margin, sitting at about 88.52\% as of late 2025, giving them significant capital flexibility to invest in their AI platform.
|
||||
|
||||
High Customer Expansion: Their dollar-based net retention rate (DBNRR) was a strong 123\% in Q4 FY25, meaning existing customers spent 23\% more on average than they did the previous year. This shows the 'expand' part of their strategy is working defintely well.
|
||||
|
||||
Financial Strength and Efficiency: For the full fiscal year 2025, the company achieved a non-GAAP operating margin of 10\% and a non-GAAP adjusted free cash flow of \$120.0 million, demonstrating a focus on profitable growth, which is rare in the high-growth software sector.
|
||||
|
||||
GitLab Inc. (GTLB) How It Makes Money
|
||||
GitLab Inc. (GTLB) primarily generates revenue by selling subscriptions to its comprehensive DevSecOps platform, which is offered as both a cloud-based Software-as-a-Service (SaaS) and a self-managed solution.
|
||||
The company's financial engine is built on recurring subscription fees, meaning predictable, high-margin revenue from customers who pay per user to access its integrated development, security, and operations tools.
|
||||
|
||||
GitLab Inc.'s Revenue Breakdown
|
||||
You need to see where the money is actually coming from, not just the top-line number. For the second quarter of fiscal year 2026 (ended July 31, 2025), GitLab's revenue was \$236.0 million, and the breakdown confirms the dominance of the subscription model.
|
||||
|
||||
|
||||
|
||||
Revenue Stream
|
||||
\% of Total (Q2 FY2026)
|
||||
Growth Trend
|
||||
|
||||
|
||||
|
||||
|
||||
Subscription (SaaS \& Self-Managed)
|
||||
90.13\%
|
||||
Increasing
|
||||
|
||||
|
||||
Professional Services \& Other
|
||||
9.87\%
|
||||
Increasing
|
||||
|
||||
|
||||
|
||||
That 90.13\% from subscriptions is the core of their business model, a classic high-quality SaaS revenue stream. The Subscription revenue of \$212.7 million in Q2 FY2026 was the main driver of the overall 29\% year-over-year revenue growth.
|
||||
|
||||
Business Economics
|
||||
The real story here is how GitLab is monetizing its customer base, and that means looking beyond the initial sale. Their business economics are shifting toward a hybrid model to capture more value from heavy users, especially with the rise of AI-powered development.
|
||||
|
||||
|
||||
High Retention: The Dollar-Based Net Retention Rate (DBNRR) was 121\% in Q2 FY2026. This means existing customers, on average, spent 21\% more this year than last year. That's a huge lever for growth.
|
||||
|
||||
Gross Margin Strength: Non-GAAP Gross Margin stood at a very healthy 90\% in Q2 FY2026. This high margin shows the platform's efficiency and scalability, proving that selling another user seat costs the company very little.
|
||||
|
||||
Hybrid Pricing Model: GitLab is transitioning from a purely seat-based subscription to a seat-plus-usage model. This lets them charge for the base access and for consumption of high-value features, like their AI agent, GitLab Duo, which is priced at \$19 per month per user. This is defintely a smart move to monetize the AI productivity boom.
|
||||
|
||||
Here's the quick math: a 121\% DBNRR means they grow revenue even if they don't add a single new customer, just by getting existing ones to expand their usage or upgrade their tier.
|
||||
|
||||
GitLab Inc.'s Financial Performance
|
||||
The financial trend is clear: strong growth is being paired with a rapid move toward operational efficiency, which is what you want to see in a maturing software company. For more detail on the structural health of the business, you should check out Breaking Down GitLab Inc. (GTLB) Financial Health: Key Insights for Investors.
|
||||
|
||||
|
||||
Annual Revenue: Total revenue for the full fiscal year 2025 reached \$759.2 million, marking a robust 31\% increase year-over-year.
|
||||
|
||||
Operating Profitability: The non-GAAP Operating Margin has seen massive expansion, moving from 10\% for the full FY2025 to 17\% in the more recent Q2 FY2026. This indicates serious operational leverage as the company scales.
|
||||
|
||||
Cash Flow Generation: GitLab is generating substantial free cash flow (FCF), a sign of financial health. Non-GAAP Adjusted Free Cash Flow for FY2025 was \$120.0 million. In Q2 FY2026 alone, it was \$46.5 million.
|
||||
|
||||
Enterprise Customer Growth: The most valuable customers are expanding quickly. The number of customers with over \$100,000 in Annual Recurring Revenue (ARR) grew 25\% year-over-year in Q2 FY2026, reaching 1,344 customers. These large contracts underpin the revenue stability.
|
||||
|
||||
GitLab Inc. (GTLB) Market Position \& Future Outlook
|
||||
GitLab Inc. is defintely positioned as the leading integrated DevSecOps platform, aggressively challenging the incumbent toolchain model by consolidating the entire software development lifecycle (SDLC) into a single application. The company's focus on AI-driven security and compliance positions it to capture a larger share of the enterprise market, targeting an estimated full-year Fiscal Year 2025 revenue of approximately \$753 million.
|
||||
You're looking at a company that's not just selling a tool, but a platform philosophy-so its near-term success hinges on converting customers from fragmented toolchains (like Jira + Jenkins + GitHub) to its all-in-one solution.
|
||||
Competitive Landscape
|
||||
The DevOps market, valued at around \$16.13 billion in 2025, is a battleground between integrated platforms and best-of-breed toolchains. GitLab's primary competition comes from Microsoft-owned GitHub and the Atlassian ecosystem, each dominating different parts of the SDLC. Here's the quick math on the relative market positioning as of late 2025, based on platform adoption and CI/CD tool usage:
|
||||
|
||||
|
||||
|
||||
Company
|
||||
Market Share, \%
|
||||
Key Advantage
|
||||
|
||||
|
||||
|
||||
|
||||
GitLab Inc.
|
||||
12\%
|
||||
Single, integrated DevSecOps platform; strong self-managed/compliance features.
|
||||
|
||||
|
||||
GitHub (Microsoft)
|
||||
55\%
|
||||
Dominant code hosting, largest developer community, expansive third-party Actions ecosystem.
|
||||
|
||||
|
||||
Atlassian (Bitbucket)
|
||||
18.61\%
|
||||
Deep integration with Jira and Confluence; strong presence in the Continuous Integration/Continuous Delivery (CI/CD) tools market.
|
||||
|
||||
|
||||
|
||||
|
||||
Opportunities \& Challenges
|
||||
GitLab's strategic initiatives for late 2025 and into 2026 center on AI and enterprise compliance, but still face headwinds from established competitors and a complex regulatory environment.
|
||||
|
||||
|
||||
|
||||
Opportunities
|
||||
Risks
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
AI-Native DevSecOps: Monetizing GitLab Duo (AI orchestration platform) to accelerate development by an early-reported 50\%.
|
||||
|
||||
AI Competition \& Pricing Pressure: Aggressive AI product launches from Microsoft (GitHub Copilot) and other cloud vendors.
|
||||
|
||||
|
||||
|
||||
Enterprise Consolidation: Driving adoption of the Ultimate tier, which focuses on security and compliance, to increase the Dollar-Based Net Retention Rate (DBNRR), which was 121\% in Q2 FY2026.
|
||||
|
||||
Macroeconomic Spending Slowdown: Enterprise customers optimizing cloud and software budgets, which can delay platform migration decisions.
|
||||
|
||||
|
||||
|
||||
Regulated/Sovereign Cloud: Expanding the GitLab Dedicated offering via the partnership with Amazon Web Services Inc. (AWS) to capture highly regulated industries requiring data residency.
|
||||
|
||||
Leadership Transition: CFO Brian Robins' departure in September 2025 introduces a minor, but real, operational risk during a critical growth phase.
|
||||
|
||||
|
||||
|
||||
|
||||
Industry Position
|
||||
GitLab is a clear leader in the DevSecOps platform category, often recognized for its completeness over competitors who rely on assembling toolchains. The company's unique all-remote structure also gives it an edge in talent acquisition and operational efficiency.
|
||||
|
||||
Win the Platform War: The strategy is to win on platform completeness, offering a single data model for the entire SDLC, which eliminates context switching and tool sprawl friction.
|
||||
Ultimate Tier Focus: Continued investment in security, compliance, and governance features drives higher average selling prices (ASPs) and targets the large enterprise market.
|
||||
Investor Confidence: The company's guidance for Fiscal Year 2026 revenue of \$936 million to \$942 million suggests strong confidence in sustaining momentum.
|
||||
|
||||
This aggressive push into AI and compliance is why you should be watching their customer adoption metrics closely. You can find more details on institutional holdings and investment theses here: Exploring GitLab Inc. (GTLB) Investor Profile: Who's Buying and Why?},
|
||||
language = {en},
|
||||
urldate = {2026-04-19},
|
||||
journal = {AI-Powered Discounted Cash Flow Model Templates},
|
||||
author = {team, dcf model},
|
||||
file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\C5XVTVNI\\gtlb-history-mission-ownership.html:text/html},
|
||||
}
|
||||
|
|
|
|||
Binary file not shown.
Loading…
Reference in New Issue