Gitlab Explores Sale

Original Article ↗ Hacker News Discussion ↗

GitLab’s exploration of a sale, reportedly including talks with Datadog and interest from larger cloud players like Google, is prompting concern among developers and businesses that rely on it for source hosting and CI/CD. Commenters question the strategic fit with Datadog, fear price hikes, lock‑in, or product neglect, and criticize GitLab’s existing enterprise‑heavy pricing and feature decisions. Many highlight the appeal and risks of open core, on‑prem, and self‑hosted alternatives, noting that migration costs and the dominance of GitHub complicate any shift away.

Overall Reaction to Sale

  • Many see it as bad news for small businesses and developers who rely on GitLab.
  • Tone is generally pessimistic: “explores sale” is read as a sign the standalone model is failing.
  • Some express simple disappointment: they had rooted for GitLab but feel it lost its way around 2020.

Fit with Potential Acquirers

  • Datadog: widely viewed as a poor cultural and product fit with “negative synergy.”
    • Concerns about vendor lock‑in and upsell based on analyzing repos and stacks.
    • Fear that Datadog would milk the customer base, raise prices, and neglect core dev tooling.
  • Google/Alphabet: some think it could strengthen Google Cloud; many others expect Google would eventually kill it, citing past code-hosting shutdowns.
  • Red Hat/IBM: seen by a few as a more natural enterprise fit, but GitLab’s valuation and lack of profit are questioned.

Business Model, Pricing, and Moat

  • Repeated criticism of GitLab’s pricing:
    • Removal of cheap tiers, steep jumps from $4 → $20 → $30 per user, AI add‑ons, and expensive “Ultimate.”
    • All users must be on the same tier, making casual users (e.g., wiki-only) disproportionately costly.
    • Self‑hosted per‑seat pricing is called “insane” by some.
  • Many argue GitLab has no strong moat versus GitHub and is squeezed by a competitor subsidized by a trillion‑dollar parent.
  • Others argue “no moat” + open core can still work if costs were lower and focus shifted to hobbyists/SMBs.

GitLab vs. GitHub and Alternatives

  • Several report migrating from GitLab to GitHub due to visibility, pricing, and perceived product drift.
  • Feature comparisons are mixed:
    • Some praise GitLab CI/CD (e.g., dynamic child pipelines, on‑prem elegance).
    • Others call it a fragile, YAML-heavy system missing basic capabilities.
  • GitHub Actions is seen as having caught up enough that GitLab’s earlier CI advantage is gone.
  • Alternatives discussed: Gitea (now commercial), Forgejo/Codeberg (non‑profit fork), Fossil, Radicle (decentralized), Jenkins/Gerrit, and full self‑hosting.

Self‑Hosting, Open Source, and Risk

  • Self‑hosting is seen as increasingly attractive for compliance, outages, and future AI‑driven data-use scandals.
  • Some large users (e.g., research institutions) worry about the cost and pain of migrating thousands of GitLab pipelines if the acquirer changes strategy.
  • Open source (or at least open core) is still viewed as less risky than fully proprietary platforms, due to forking and migration options.