GitLab frames the workforce reduction and values retirement as 'Act 2' — a deliberate transformation rather than a contraction. The company positions itself as entering a new phase, implying the old cultural operating system served its purpose but must evolve for what comes next, likely AI-augmented development workflows.
The editorial argues that layoffs are background noise in tech, but retiring CREDIT is culturally seismic. CREDIT wasn't decorative — it was operationalized across a 2,000+ page public handbook that became the template for an entire generation of remote-first companies. Retiring it acknowledges that what GitLab does has diverged from what it declared it believed.
The editorial contextualizes GitLab's moves within the wider trend of DevOps platform companies navigating the post-ZIRP environment. GitLab previously cut ~7% of staff in early 2023, and this latest round continues a pattern seen across the industry as companies simultaneously contract and try to reposition around AI-augmented development.
The editorial emphasizes that CREDIT was not a poster on a wall but a deeply embedded cultural system. Transparency meant public company meetings and open compensation calculators; Iteration shaped the product methodology; Collaboration was the engineering methodology for an all-remote company. Losing these values means losing the specific operational practices that made GitLab distinctive.
By framing the submission as 'end of their CREDIT values' rather than leading with the layoffs, this poster — identifying as a GitLab employee — signals that the cultural shift is the headline story. The submission drew 584 points and 569 comments, suggesting the HN community agreed the values retirement was the most newsworthy element.
GitLab published a blog post titled "GitLab Act 2," announcing a workforce reduction and — more culturally significant — the retirement of its CREDIT values framework. CREDIT stood for Collaboration, Results, Efficiency, Diversity Inclusion & Belonging, Iteration, and Transparency, and it wasn't just a poster on a wall. GitLab's CREDIT values were arguably the most operationalized corporate values in tech, embedded in a 2,000+ page public handbook that became the template for how an entire generation of remote-first companies defined their culture.
The "Act 2" framing is deliberate. GitLab's leadership is positioning this not as a contraction but as a transformation — a company entering its next phase. The layoffs, while painful, are the expected part. Every public tech company has done a round (or three) since 2022. The values retirement is the part that sent the Hacker News thread to 584 points.
GitLab had previously cut approximately 7% of staff in early 2023. This latest reduction continues a pattern across DevOps platform companies navigating the post-ZIRP environment while simultaneously trying to pivot toward AI-augmented development workflows.
### The values signal is louder than the layoff signal
Layoffs in tech are background noise at this point. What makes this story significant is that GitLab didn't just cut headcount — it retired the cultural operating system that made it *GitLab*.
Consider what CREDIT represented. Transparency meant GitLab ran company meetings publicly, kept compensation calculators open, and maintained a handbook that anyone on the internet could read and comment on. Iteration meant shipping the smallest viable change, which influenced how the entire product was built. Collaboration in an all-remote company wasn't a nicety — it was the engineering methodology.
When a company retires its values, it's not changing what it believes — it's acknowledging that what it *does* has already diverged from what it *said*. The handbook was already getting quieter. The radical transparency had been dialing back. The CREDIT retirement makes official what insiders likely already knew.
### The 'Act 2' pattern in DevOps platforms
GitLab isn't alone in this transition. The DevOps platform market is being reshaped by two simultaneous forces: the profitability imperative (public markets now demand it) and the AI integration race (developers expect it).
GitHub has Copilot. Atlassian has Rovo. Every platform company is trying to become the AI-native developer workflow layer. GitLab's "Act 2" almost certainly means doubling down on AI-powered DevSecOps — code generation, automated security scanning, AI-assisted merge reviews — while trimming the org to a shape that can execute on that bet without the overhead of maintaining a culture-first identity.
The uncomfortable truth is that radical transparency and rapid AI pivots are in tension. Transparency slows decisions. It requires explanation, debate, and consensus. When you're racing to ship AI features before your competitors eat your lunch, the CREDIT value of "Iteration" (ship small) can conflict with the market reality of "ship the AI thing now, at whatever scope gets attention."
### The Hacker News reaction tells its own story
A score of 584 on Hacker News for a corporate blog post about values and layoffs is extraordinary. For context, that's the kind of engagement usually reserved for major security breaches or paradigm-shifting open source releases. The developer community cared about GitLab's values — many adopted similar frameworks for their own teams.
The community reaction likely splits along predictable lines: those who see this as an honest acknowledgment of reality ("at least they're not pretending anymore") and those who see it as the final proof that VC-backed companies cannot sustain genuinely different cultures at scale. Both readings have merit.
What's harder to articulate but equally real: many developers chose GitLab *because* of what CREDIT represented. The open-core model, the transparent roadmap, the values-driven decision making — these weren't just employer branding, they were product differentiators. If GitLab stops being the company that operationalizes transparency, some users will start asking whether GitLab is still the product that operationalizes transparency.
### If you're a GitLab customer
Don't panic-migrate. Layoffs and values changes don't break your CI/CD pipeline tomorrow. But do pay closer attention to the product roadmap over the next two quarters. The features that get accelerated will tell you what "Act 2" actually means in practice. If AI-assisted features surge while community-requested improvements stall, that's your signal about where investment is going.
Watch the open-source tier specifically. GitLab's commitment to open core was a CREDIT-adjacent value. If "Act 2" means a harder push toward enterprise monetization, the free tier may see less love.
### If you're building team culture
GitLab's CREDIT retirement is a case study in what happens when values are too coupled to a specific phase of company growth. Values that work for a 500-person all-remote startup scaling to IPO may not work for a 2,000-person public company fighting for AI relevance. The lesson isn't "don't have values" — it's "design values that can evolve, or plan for the day you'll retire them."
The most durable engineering cultures anchor values to *how* decisions get made (e.g., "we write things down before meetings") rather than aspirational nouns (e.g., "Transparency"). Process-level values survive strategy pivots. Abstract values become debt.
### If you're on the job market
GitLab alumni carry real credibility in the remote-work and DevOps spaces. If you're affected by the reduction, the fact that you operated inside one of the most documented engineering cultures in history is a genuine differentiator. Lead with the specifics of how you worked, not just where.
GitLab's "Act 2" will be judged not by the blog post but by what ships in the next 12 months. If the leaner org delivers a genuinely competitive AI-native DevSecOps platform, the market will forgive the cultural reset. If it ships incremental features with fewer people and less soul, the CREDIT retirement will look less like a strategic pivot and more like the moment GitLab became just another DevOps vendor. The 584-point Hacker News thread suggests the developer community is watching closely — and it has a long memory.
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