The editorial argues that CREDIT values weren't aspirational slogans but actual operating procedures embedded in GitLab's famous public handbook. Retiring them signals that the company GitLab wants to be going forward is fundamentally different from the transparent, remote-first pioneer it became known as.
The editorial notes that hundreds of startups — especially remote-first ones founded between 2018 and 2022 — explicitly copied GitLab's CREDIT framework and public handbook as their cultural template. When the originator abandons the playbook, every company that adopted it needs to re-evaluate whether those values still hold up independently.
The editorial characterizes the 'Act 2' framing as corporate theater, arguing the substance is a familiar pattern across enterprise SaaS: headcount that made sense during zero-interest-rate expansion being cut to show a path to sustained profitability as a public company.
The editorial flags that the 'Diversity, Inclusion & Belonging' component being retired alongside the rest of CREDIT will draw its own scrutiny. It notes GitLab isn't unique here — the broader tech industry has been pulling back from DEI commitments, and GitLab's move is part of that wider trend.
GitLab published a blog post titled "GitLab Act 2" announcing a workforce reduction and, perhaps more consequentially, the retirement of its CREDIT values framework. CREDIT — Collaboration, Results, Efficiency, Diversity Inclusion & Belonging, Iteration, Transparency — wasn't just an internal poster. It was the scaffolding of one of the most ambitious experiments in corporate transparency the tech industry has seen.
For years, GitLab's public handbook was the proof. Thousands of pages documenting everything from how to run a meeting to how compensation bands were calculated. The CREDIT values weren't aspirational slogans — they were operating procedures, and retiring them is an admission that the company GitLab wants to be is fundamentally different from the one it built its reputation on.
The workforce reduction itself follows a pattern now familiar across enterprise SaaS: headcount that made sense during the zero-interest-rate expansion doesn't survive the margin scrutiny of a public company that needs to show a path to sustained profitability. GitLab framing it as "Act 2" is corporate theater, but the substance underneath is real restructuring.
GitLab's CREDIT values had outsized influence beyond GitLab itself. Hundreds of startups — particularly remote-first ones founded between 2018 and 2022 — explicitly modeled their culture documents on GitLab's framework. The public handbook became a template. "Just do what GitLab does" was genuine advice in founder Slack channels. When the company that wrote the playbook on radical transparency decides that playbook no longer serves its interests, every company that copied the homework should be asking hard questions.
The "Diversity, Inclusion & Belonging" component of CREDIT being retired alongside everything else will draw its own headlines, and that's worth addressing directly. GitLab isn't unique in pulling back from DEI commitments — the industry-wide retreat has been well documented since 2023. But packaging a DEI rollback inside a broader values retirement is a specific rhetorical move: it lets leadership frame the change as strategic evolution rather than political capitulation. Whether you find that honest or cynical depends on priors this editorial won't resolve.
What's less ambiguous is the Transparency piece. GitLab's radical transparency was genuinely unusual. Public compensation calculators. Public OKRs. A handbook that any competitor could read. That transparency created real competitive disadvantages that GitLab accepted as the cost of living its values. Retiring Transparency as a core value removes the philosophical obligation to accept those costs — and if the next version of GitLab's values doesn't include something equivalently binding, the handbook will quietly start shrinking.
The Hacker News thread scoring 402 points captures something specific: developer grief. Not for the jobs lost — layoff threads rarely sustain that kind of engagement — but for the symbolic death of a particular idea about how tech companies should work. GitLab was proof-of-concept that a $10B+ company could operate with radical openness. If they can't sustain it, the implicit argument goes, maybe nobody can.
This fits a trajectory that's become almost mechanical in enterprise software. Phase one: build a distinctive culture that attracts talent and generates earned media. Phase two: go public and discover that the culture that attracted engineers doesn't always map to the operating model that satisfies public-market investors. Phase three: rebrand the retreat as evolution.
We saw it at Buffer (pulled back from public salaries), at Basecamp (abandoned political discussions at work), and now at GitLab (retiring CREDIT entirely). The common thread is that values frameworks optimized for talent attraction in a growth phase become liabilities in a profitability phase — not because the values are wrong, but because they constrain the operational flexibility that margin optimization requires.
The "Act 2" framing deserves scrutiny specifically because it implies the first act was a complete story. It wasn't. GitLab's first act included real innovations in remote work practices, a DevOps platform that genuinely unified the toolchain, and a culture experiment that produced usable artifacts for the entire industry. Calling what comes next "Act 2" implies continuity. What's actually happening is discontinuity — a different company with the same name and codebase.
If you're a GitLab customer, the product implications are indirect but real. Culture changes at platform vendors eventually manifest as product decisions. A GitLab that values Transparency with a capital T ships a public roadmap and accepts feature requests in public issues. A GitLab optimizing for enterprise sales velocity might decide that public roadmaps create competitive risk. Watch for the handbook to thin out over the next 12 months — that's the leading indicator.
If you're evaluating GitLab vs. GitHub for your organization, this changes the calculus slightly. GitLab's cultural distinctiveness was a genuine differentiator for teams that valued alignment between their own engineering culture and their vendor's. That differentiator is now deprecated. Evaluate on features, pricing, and integration depth — the same boring criteria you'd use for any enterprise tool.
If you're a founder or engineering leader who built culture docs inspired by GitLab's CREDIT framework, don't panic-retire them. The values weren't wrong. But do an honest audit: which of your stated values actually constrain decisions, and which are decorative? The ones that constrain decisions are the ones that will eventually face the same pressure GitLab just yielded to. Knowing that in advance is worth something.
GitLab will replace CREDIT with something. Every company has values, stated or unstated. The question is whether the replacement will have the same teeth — whether it will commit GitLab to specific behaviors that cost something to maintain. If the new framework is vague enough to be unfalsifiable ("We value excellence and customer focus"), that tells you everything about Act 2's actual script. The handbook is still public, for now. Bookmark it. It may become the most interesting artifact in the history of corporate transparency — precisely because we'll be able to watch it change in real time, or stop changing because it stopped being updated.
Lots of interesting information here:>The agentic era affords GitLab the largest opportunity in our history as a company, and we're making the structural and strategic decisions to meet it>Operationally, we grew into a shape that was right for the last era and isn't right for this on
After CVE-2023-7028 (account takeover via password reset, IIRC you just had to add a semi-colon between the correct email and the attacker email and it'd email both) was exploited against my cluster, the boasting about fully-automated changes and reviews scares me. I hope I'm far from the
GitLab could be the perfect case study on AI-powered efficiency improvements. I have never interacted with a piece of software that, for every single problem I found, there was an open issue always at least 4-7 years old that was just being shuffled around by managers adding and removing random labe
GitLab never ceases to amaze me in terms of just how bad their product roadmap is. Practical things like CI improvements are put off over UI rebranding on unicorn colours. Yet, good tooling is exactly why people used to pay for GitLab. For better or worse maybe this finally can change and we can get
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
https://www.google.com/search?q=gitlab+stock shows their stock price was ~$52 a year ago and is $26 today, so down 50% in 12 months. It's quite possible this is because they weren't making enough noise about their AI strategy.If investor fears are that AI makes GitLab's