Sid Sijbrandij: Building GitLab into a Fully Remote Billion-Dollar Company

Sid Sijbrandij: Building GitLab into a Fully Remote Billion-Dollar Company

Introduction

Sid Sijbrandij is the co-founder and CEO of GitLab, one of the most influential developer platforms of the last decade and one of the world’s best-known fully remote companies. Under his leadership, GitLab evolved from a small open-source project into a publicly traded, multibillion-dollar DevOps platform used by tens of thousands of organizations worldwide.

For founders, investors, and operators, his story matters because it combines several powerful themes:

• Turning an open-source side project into a global SaaS business
• Proving that a fully remote, handbook-driven company can scale to IPO
• Competing in a market dominated by giants like GitHub, Atlassian, and Microsoft

Sijbrandij’s journey is not just about building a product for developers; it is about building a new operating model for companies in a distributed, digital-first world.

Early Life and Education

Sid Sijbrandij grew up in the Netherlands with an early curiosity for how complex systems work, from machinery to organizations. His academic path wasn’t a straight line into computer science or startup life. He studied in the Netherlands and initially followed a more traditional path in management and law before gravitating toward technology and entrepreneurship.

Crucially, he became a self-taught programmer. Rather than emerging from a formal CS background, he learned to code on his own while working in and around engineering-focused businesses. One formative experience was working at a company that designed and built custom submarines. This environment exposed him to:

• Highly complex engineering projects with strict safety and quality requirements
• Distributed collaboration among specialists in different locations
• The importance of process, documentation, and version control

These experiences planted early seeds for what would later become core to GitLab’s DNA: structured collaboration, documentation, and iteration.

Before GitLab, Sijbrandij also worked at a web consultancy, where he saw firsthand how teams struggled to coordinate on code, deploy software, and manage tooling sprawl. This direct exposure to the friction developers experienced in everyday work made him particularly receptive when he discovered an emerging open-source project called GitLab.

Startup Journey: From Open Source Project to Company

GitLab did not start as a company. It started in 2011 as an open-source project created by Ukrainian developer Dmitriy Zaporozhets, who wanted a self-hosted alternative to GitHub. In 2012, Sijbrandij discovered GitLab on Hacker News. He immediately recognized two things:

• The technical strength of the project and its momentum in the developer community
• The commercial opportunity to build a business around it for companies that needed support, features, and enterprise-grade stability

Sijbrandij reached out to Zaporozhets and proposed turning GitLab into a company. Together, they co-founded what would become GitLab Inc., initially offering support and services around the open-source project. In the early days, revenue came from:

• Consulting and custom development for companies adopting GitLab
• Paid features on top of the open-source core
• Hosted GitLab instances for teams that didn’t want to run their own servers

In 2015, GitLab was accepted into Y Combinator (Winter 2015 batch). This was a decisive moment. It forced the founders to:

• Clarify GitLab’s identity as a product company, not a consulting shop
• Focus on a recurring-revenue SaaS model
• Position GitLab as a serious alternative in the global DevOps and source control market

Y Combinator also validated that a company without a physical office, whose founders and early team members were distributed across countries, could still be funded and scaled. GitLab emerged from YC with a clear vision: become the single application for the entire DevOps lifecycle.

Key Strategic Decisions That Shaped GitLab

1. Committing to Fully Remote from the Start

While many companies adopted remote work reluctantly, GitLab embraced being all-remote from its earliest days. There was no headquarters. Team members were distributed across time zones and countries.

Instead of treating this as a compromise, Sijbrandij turned it into a strategic advantage:

• Access to global talent without geographic constraint
• Reduced overhead from offices and relocation
• Operational resilience well before remote work became mainstream

This forced the company to build robust systems for documentation, asynchronous collaboration, and explicit communication very early—systems that would later become part of GitLab’s public brand and operating playbook.

2. Adopting an Open-Core Business Model

Instead of choosing between pure open source or purely proprietary software, Sijbrandij pushed GitLab toward an open-core model:

• The core GitLab product remains open source, fostering a global contributor community.
• Advanced features for security, compliance, and large enterprises are offered as paid tiers.

This model allowed GitLab to:

• Leverage the reach and goodwill of open source
• Move faster through community contributions
• Build a sustainable revenue engine, particularly from large enterprises

3. Positioning as a Single DevOps Platform

Initially, GitLab competed primarily as a Git repository management tool. Over time, Sijbrandij made a critical positioning decision: GitLab would not just be a code hosting service; it would become a single application for the entire DevOps lifecycle, including:

• Source code management
• Continuous Integration and Continuous Delivery (CI/CD)
• Security scanning and DevSecOps
• Project management and planning
• Monitoring and analytics

This strategy differentiated GitLab from point tools and toolchains stitched together via integrations. For large organizations struggling with fragmented DevOps stacks, it was a compelling value proposition: one platform, one data model, one interface.

4. Radical Transparency and “Handbook-First” Culture

Another defining decision was to run GitLab with public transparency that most companies would consider unthinkable. GitLab maintains a massive, publicly accessible company handbook, documenting:

• Company values and principles
• Process for hiring, compensation, and performance
• Engineering and product management workflows
• Remote work practices and communication norms

The internal rule is: “If it’s not in the handbook, it doesn’t exist.” This handbook-first culture:

• Enables asynchronous work across time zones
• Reduces ambiguity and politics
• Signals trust and openness to both employees and the wider community

Growth of GitLab: From Startup to Public Company

GitLab’s growth trajectory illustrates how a focused, remote-first, open-core company can scale globally.

Funding and Valuation Milestones

After Y Combinator, GitLab raised multiple venture rounds from prominent investors. Key milestones included:

• Seed and early rounds following YC, allowing GitLab to invest in product and community
• Growth rounds from leading venture and growth equity firms as the company moved upmarket
• Achieving unicorn status (valuation above $1 billion) in 2018
• Additional late-stage funding valuing GitLab at multiple billions as its enterprise business matured

In October 2021, GitLab went public on the NASDAQ under the ticker GTLB, cementing its status as one of the most successful open-source–driven and fully remote companies to reach the public markets.

Scaling the Team and Culture

From a handful of distributed collaborators, GitLab scaled to thousands of team members across more than 60+ countries. Doing so without offices required deliberate design:

• Defaulting to written, asynchronous communication
• Clear decision-making frameworks documented in the handbook
• Transparent career paths and compensation structures
• Intentional onboarding to remote work and GitLab’s values

When the COVID-19 pandemic pushed the world into remote work, GitLab was often cited as a model organization. Sijbrandij and the company published extensive guides on remote work practices, further boosting GitLab’s reputation and brand.

Market Expansion and Product Depth

GitLab expanded well beyond its roots as a Git repository manager by continually shipping new capabilities. The company is known for its monthly release cadence, shipping a new version on a predictable schedule.

Strategically, GitLab focused on:

• Serving large enterprises in regulated industries with robust security and compliance features
• Partnering with major cloud providers and integrators to embed GitLab into enterprise workflows
• Positioning itself as a DevSecOps platform, integrating security earlier into the development lifecycle

This enterprise focus significantly expanded GitLab’s addressable market and underpinned its revenue growth leading up to and after the IPO.

Leadership Style: How Sid Sijbrandij Builds Teams

Sijbrandij’s leadership style blends systems thinking, transparency, and humility. Several elements stand out for founders:

• Values-driven leadership: GitLab documents and lives by explicit values such as iteration, transparency, and collaboration. These values are referenced in daily decisions, not just in brand materials.
• Servant leadership: His approach emphasizes enabling teams to do their best work. Leadership’s role is to remove blockers, not dictate from the top.
• Documentation over verbal authority: At GitLab, arguments are won by written reasoning and evidence documented in issues, merge requests, and the handbook.
• Comfort with public learning: GitLab has been open about incidents, outages, and mistakes, publishing postmortems and learning openly. This requires a high tolerance for vulnerability at the top.

His leadership validates that a CEO can be both highly analytical and deeply community-oriented, building trust with open-source contributors, customers, and employees simultaneously.

Lessons for Founders

Founders and investors can extract several practical lessons from Sijbrandij’s journey with GitLab.

1. Remote-First Is an Operating System, Not a Perk

GitLab shows that remote work is not just about hiring people who work from home; it is about designing a company around:

• Written, asynchronous communication
• Clear documentation and decision logs
• Explicit processes and expectations

Treating remote as a core operating system enabled GitLab to scale globally without the friction and cost of offices, while remaining resilient and efficient.

2. Open Source + Open Core Can Be a Powerful Engine

By embracing open source and layering commercial value where enterprises need it most, GitLab:

• Built a large user base organically
• Received contributions from a global community
• Converted a subset of users to high-value, paying customers

For technical founders, open core can be a viable path—if you are clear about which features remain open and where you add enterprise-grade value.

3. Clarity of Positioning Wins in Crowded Markets

GitLab entered a market with strong incumbents, including GitHub. Its success came not from being a slightly better Git host, but from:

• Reframing the category as DevOps / DevSecOps platform
• Offering a single application to simplify complex toolchains
• Targeting the specific pain of enterprises juggling many fragmented tools

Founders in crowded markets can similarly win by redefining the problem and owning a new, clearer category.

4. Transparency Builds Trust and Velocity

Radical transparency—public handbooks, visible roadmaps, open issue trackers—may feel risky. Yet GitLab demonstrates how it can:

• Align teams more quickly, because expectations are clear
• Attract candidates who self-select into the culture
• Build trust with users and customers, especially in open-source ecosystems

5. Iterate Relentlessly

GitLab’s monthly release cadence reinforces a core principle: iteration beats perfection. Instead of waiting for perfect, large releases, the company:

• Ships small, incremental improvements frequently
• Collects feedback quickly from real users
• Reduces the risk of large, brittle launches

For startups, consistent, incremental delivery is often a better strategy than betting the company on infrequent, “big-bang” releases.

Quotes and Philosophy

While GitLab’s philosophy is captured across thousands of handbook pages, several ideas capture Sijbrandij’s worldview:

• “Everyone can contribute” – GitLab’s core tagline reflects the belief that innovation can come from anywhere: employees, customers, and open-source contributors.
• Handbook-first work: If it isn’t written down, it doesn’t exist. This drives accountability and clarity across the company.
• Transparency by default: Make information public unless there is a clear reason not to. This reduces silos and politics.
• Iteration over perfection: Ship the smallest valuable change and improve from there.
• Remote as a core principle: Work should be something you do, not a place you go. Processes must support that reality.

These principles are not abstract ideals; they are directly translated into GitLab’s operating practices and are a large part of why the company could scale globally while remaining cohesive.

Key Takeaways

• You can build a world-class company without an office. GitLab proves that fully remote, well-structured organizations can reach IPO scale.
• Open core is a viable business model. By combining open source with enterprise features, GitLab balanced community growth and commercial success.
• Clear category positioning matters. Reframing GitLab as a full DevOps platform differentiated it from pure source control competitors.
• Documentation and transparency are competitive advantages. GitLab’s handbook-first, transparent culture increases alignment and execution speed.
• Iteration compounds. A disciplined, high-cadence release process enabled GitLab to move quickly and learn faster than many competitors.
• Values must be operational, not ornamental. Sijbrandij’s emphasis on values like iteration, collaboration, and transparency shows up in daily practices, not just marketing.

For founders and investors, Sid Sijbrandij’s journey with GitLab offers a blueprint for building remote-native, open, and high-performing technology companies in a world where software is built everywhere, by everyone.