When GitLab filed for its IPO in October 2021, the prospectus contained a sentence that stood out from almost every other company going public that year: “We are a remote-only company, meaning that all of our team members work remotely. Due to this, we do not currently have a principal executive office.”
No headquarters. No floor plans. No corporate campus. Just over 1,400 people working from 65+ countries, and somehow, payroll, contracts, taxes, and compliance had to work for every single one of them. Most companies don’t think about Employer of Record (EOR) services until they hire their first international employee.
GitLab thought about EOR at a scale almost no other company has faced: how do you manage employment compliance across more than 65 countries when you have no legal entity in most of them? Their answer became one of the most ambitious EOR consolidation projects on record, moving from 30+ different EOR providers down to a single global partner, Global Expansion (GX), without disrupting hiring or breaking compliance in a single jurisdiction.
In this article, you’ll learn the GitLab EOR case study — what they were trying to fix, how they evaluated providers, what the migration actually looked like, and the lessons any company hiring globally can take from it.
GitLab Timeline
Dmitriy Zaporozhets creates GitLab from his home in Ukraine, a house without running water, with the first commit made remotely.
Sid Sijbrandij, working from the Netherlands, partners with Dmitriy after spotting his tweet about wanting to work on GitLab full-time.
GitLab Inc. is incorporated in Delaware. The first employee is based in Serbia, making the company accidentally remote from day one.
GitLab joins YCombinator. After briefly opening a San Francisco office that nobody attended, the team commits to all-remote permanently.
GitLab pioneers the Head of Remote role, triggering a global movement of dedicated remote-work leadership at other companies.
With over 1,200 team members in 65+ countries, GitLab is widely recognized as the world's largest all remote company
GitLab IPOs on the Nasdaq Global Select Market on October 14, 2021 under the ticker GTLBat $77/share, raising $800.8M.
GitLab grows past 1,500 team members across 65+ countries. Team Members are managed across more than 30 separate EOR providers — a fragmented stack that begins to slow hiring.
GitLab runs a competitive RFP and selects Global Expansion (GX) as its single global EOR partner. The consolidation is publicly profiled in a case study published by Global Expansion.
Why GitLab Needed an EOR Strategy in the First Place
Most companies hire international employees one of three ways: open a local entity, use contractors, or use an Employer of Record. For a company at GitLab’s scale and geographic spread, only the EOR option works in practice.
Opening a legal entity in every country where GitLab has a single team member would mean 65+ entities, 65+ tax registrations, 65+ payroll providers, 65+ sets of statutory benefits to administer, and a legal team an order of magnitude larger than the one GitLab actually runs. For most of those countries, places where GitLab might have one or two engineers – the cost of incorporation never pays back.
The contractor route is faster but legally fragile. Most countries have strict misclassification rules: if a contractor works full-time, takes direction from a single client, and uses the client’s tools, they’re functionally an employee and tax authorities will eventually treat them as one, with backdated payroll taxes and penalties owed by the company.
That leaves the Employer of Record model. An EOR is a third party that legally employs a worker in a country on behalf of a company that has no entity there. The EOR handles the local employment contract, payroll, taxes, statutory benefits, and compliance; the client company manages the day-to-day work. For a 1,500-person all-remote company spread across 65+ countries, EOR isn’t a convenience, it’s the only viable employment model.
The Real Problem: 30+ EORs Is Worse Than No EOR
By 2024, GitLab was using more than 30 different EOR providers worldwide. That number didn’t happen by design. It happened the way these things usually happen: hire a great engineer in country X (say, India), scramble to find a local EOR who can employ them, sign the contract, move on. Hire another in country Y (say, UAE), repeat.
Twelve years and 65+ countries later, you have a stack so fragmented that nobody on the People team knows the full picture without opening 30 separate dashboards. The downstream pain shows up in five places, all of which the Global Expansion case study explicitly names:
1. Inconsistent employee experience.
A new hire in Brazil onboarded through a different EOR than a new hire in Türkiye, who used a different EOR than a new hire in the Philippines. Different platforms, different paystub formats, different benefits portals, different support response times. For a company that publishes its internal handbook publicly and obsesses over consistency, that fragmentation contradicted the brand.
2. No unified reporting.
Headcount, cost-per-employee, benefits utilization, compliance status, all of it lived in 30+ separate vendor dashboards. Producing a single global headcount report meant manual consolidation. For a public company with quarterly reporting obligations, that’s expensive and risk-prone.
3. Inconsistent pricing.
With 30+ vendors, GitLab had 30+ pricing structures: some flat-fee, some percentage-based, some with hidden FX markups, some with surprise compliance surcharges. There was no leverage to negotiate; each vendor was too small a piece of the total spend to care about losing.
4. Compliance blind spots.
Every country has its own labor law updates. With 30+ EORs, GitLab had to trust that each vendor was monitoring local changes, and had no way to verify it independently across all jurisdictions simultaneously.
5. Slow new-country expansion.
Hiring the first employee in a new country meant evaluating, contracting with, and onboarding a new EOR — adding weeks to time-to-hire in a competitive talent market.
The strategic question wasn’t “should we use an EOR?” — it was “how do we move from 30 fragmented EORs to one global partner without breaking anything?”
The Selection Process: What GitLab Looked For in a Global EOR
GitLab ran what the case study calls a “thorough RFP process.” They weren’t just shopping for the cheapest provider, they had a specific set of criteria reflecting both the practical scale of their problem and the cultural standards of an open, handbook-first company.
The published criteria were:
1. Mission and values alignment.
GitLab’s culture is built on transparency, results, and “iteration over perfection.” A vendor that operated like a black-box outsourcer wouldn’t fit, regardless of pricing.
2. System integration.
With over 1,500 team members and a fully digital HR stack, the EOR had to integrate cleanly with GitLab’s existing tools – not require manual data entry across 65+ countries.
3. Reporting and compliance depth.
Single-pane-of-glass visibility across every country, with audit-ready compliance documentation.
4. Global support coverage.
Real local expertise in every country GitLab hires in, not a thin wrapper over partner agencies.
5. People-first transition approach.
This was the hidden differentiator. GitLab wasn’t migrating spreadsheets, it was migrating real human beings and their employment contracts. A misstep in any country could cost an employee their healthcare, their visa, or their salary timing.
Global Expansion won the RFP. According to the published case study, what set them apart was the combination of their proprietary GX1 platform (giving GitLab one consolidated view of all global EOR activity) and what GX called a “co-branded, employee-first” approach to the actual transition. The platform solved the reporting problem; the people-first methodology solved the migration risk.
How the Migration Actually Worked: GitLab's EOR Consolidation Approach
This is the part most case studies skip. How do you migrate hundreds of employees, across dozens of countries, off of 30+ legacy EORs and onto a single new one, without anyone losing a paycheck or a benefit?
GitLab and GX co-developed a four-stage playbook that any company facing a similar EOR consolidation can borrow.
1. Country-by-country requirements analysis
Before a single employee was migrated, GX built a strategic roadmap for every country. Each roadmap captured: the local labor law landscape, the existing EOR contract terms (especially termination notice periods), the employee’s current benefits and how they’d be replicated, the tax and social-security registration steps, and the payroll cutover dates.
This is the step most consolidations skip and it’s why most consolidations leak compliance issues for months afterward.
2. Employment contract review
Every existing employment contract was reviewed for local-law compliance under the new EOR. Where the legacy EOR had used non-compliant boilerplate (and many had), GX issued corrected contracts. Employees signed new contracts via digital signature.
3. Phased onboarding respecting notice and tax cycles
Not everyone moved at once. The migration was phased to respect three constraints:
• Notice periods owed to legacy EORs (typically 30–90 days depending on country)
• Employee PTO balances that needed to transfer cleanly
• Tax-year boundaries — moving an employee mid-tax-year in some jurisdictions creates double-filing complexity
Each employee got an individual cutover date that minimized disruption to their pay, benefits, and tax filings.
4. Communication overhaul
This is where the “people-first” approach became operational. GitLab and GX held individual and town-hall meetings with affected employees to explain what was changing, why, and what stayed the same (their actual job, manager, and salary).
Communication moved out of email threads and into project-management tools so HR had clear visibility on every employee’s status. The case study explicitly notes that this reduced email traffic and gave the HR team clear visibility on every transition, an important detail because GitLab runs a small People team relative to its headcount.
The Results
The headline outcome from the Global Expansion case study is striking for any company that’s tried to manage a vendor consolidation: GitLab initiated over 30 critical new hires within the first 30 days of the new EOR going live. That number matters because it answers the most common objection to EOR consolidation: “the migration will slow down hiring.” It didn’t. Hiring continued at full speed during the cutover, which is the inverse of what most large vendor migrations look like. Other documented outcomes:
• Single source of truth. GitLab’s HR team gained consolidated visibility across all global EOR activity through the GX1 platform, replacing 30+ fragmented dashboards.
• Reduced administrative load. Communication moved into structured project management workflows, cutting email traffic on EOR matters.
• Phased, no-disruption transition. No employees lost benefits, salary continuity, or tax compliance during the migration.
• Foundation for faster future expansion. New-country hires now route through one provider instead of triggering a fresh EOR evaluation.
What CRM and Other Tools Did GitLab Use Alongside Their EOR?
While the EOR managed legal employment, GitLab’s day-to-day operations ran on a familiar all-remote stack: GitLab itself for code and project management, Slack for chat, Google Workspace for documents, Zoom for video, and the GX1 platform as the single dashboard for global EOR oversight.
On the sales side, GitLab uses Salesforce as its CRM — fitting for a public company with enterprise customers and complex deal cycles. The takeaway: the EOR sits next to the CRM in the modern remote-company tech stack, not inside it. CRM manages customer relationships; EOR manages legal employment relationships. Both are non-negotiable infrastructure for a company hiring across borders.
What Other Companies Can Learn From GitLab's EOR Strategy
Most companies will never have GitLab’s scale problem: 1,500 employees in 65+ countries is genuinely rare. But the lessons from this case study apply at almost any size, from the 20- person startup hiring its third international engineer to the 500-person scale-up planning its first M&A integration.
1. Don’t accumulate EOR providers by accident.
Every time you hire in a new country and pick an EOR on the spot, you’re adding to a future consolidation problem. Pick a primary global EOR early and make exceptions deliberate, not reactive.
2.The cheapest EOR is rarely the cheapest in three years.
Vendor sprawl is the hidden cost of always optimizing for the lowest per-country price. GitLab’s 30+ providers were each “the right pick” at the moment they were chosen; the aggregate cost of managing them is what eventually forced consolidation.
3. RFP for values fit, not just price and coverage.
GitLab evaluated mission alignment alongside compliance depth. For a public, mission-driven company, that’s table stakes. For private companies, it still matters, the EOR becomes the employment face of your brand to international hires.
4. Plan migrations around employees, not contracts.
The biggest risk in any EOR consolidation isn’t a missed compliance deadline, it’s a missed paycheck or a benefits gap that erodes trust with one of your best people. Phase the rollout around notice periods, PTO, and tax cycles, even when it slows the migration calendar.
5. Demand a single platform, not just a single vendor.
Some “global” EORs are really 50 partner agencies under one brand, with 50 different dashboards. GitLab’s selection of GX hinged in part on the GX1 platform – one login, one report, one source of truth. That’s what consolidation actually means.
Conclusion
GitLab’s EOR consolidation is a useful proxy for what mature global hiring looks like. The company didn’t start with a clean strategy, it accumulated 30+ EOR providers the way most fast-growing remote companies do, one country at a time. The strategic move was recognizing when fragmentation became a tax on the business and committing to a deliberate consolidation, even at the cost of a complex multi-quarter migration.
For any company hiring across borders: an EOR isn’t a temporary workaround until you “open a real entity.” It’s a strategic decision about who legally employs your people, where, and how. Make that decision early, evaluate against the same criteria GitLab used (mission fit, integration, compliance depth, support coverage, people-first methodology), and you’ll avoid the 30-EOR sprawl that took GitLab a major project to unwind.
If you’re starting that evaluation now, our guide to the best Employer of Record services in 2026 compares the leading providers – Deel, Remote, Rippling, Oyster, and Global Expansion among them across pricing, country coverage, and platform depth. And if you’re trying to decide between two specific providers, our Deel vs Multiplier comparison breaks down the trade-offs in detail.
Frequently Asked Questions
GitLab employs people in 65+ countries. Opening a legal entity in each one would require 65+ separate incorporations, tax registrations, payroll providers, and ongoing compliance overhead, most of which would never pay back the cost in countries with only one or two employees. An Employer of Record provides legal employment in those countries without GitLab needing a local entity.
According to the Global Expansion case study, GitLab used more than 30 different EOR providers before consolidating to a single global partner.
GitLab selected Global Expansion(GX) after a competitive RFP process. The selection was driven by GX’s GX1 platform for unified global reporting and a “people-first” transition methodology, alongside compliance depth and mission alignment.
No. GitLab initiated over 30 critical new hires within the first 30 days of the new EOR going live, indicating that hiring velocity was preserved through the migration.
An EOR becomes the legal employer of workers in countries where the client has no entity — which is GitLab’s situation in most of the 65+ countries where it hires. A PEO co-employs workers alongside an existing client entity, so it only works in countries where the company is already legally established. For a remote-first company without local entities, only the EOR model applies.
Yes. The biggest lesson: pick a primary global EOR early rather than accumulating providers country by country, applies even at 10 international employees. The migration cost compounds with every additional vendor, so making the consolidation decision early is dramatically easier than making it at GitLab’s scale.
