Sourcegraph went dark

Product usage and praise

• Many commenters describe Sourcegraph’s code search as exceptionally fast and powerful (regex, path regex, JSON output), often superior to local tools.
• It’s used heavily for reverse engineering, academic/CS research, and exploring obscure macOS and framework internals.
• Public search over open-source code is seen as a major asset for learning and debugging.

Repository privatization and rationale

• The company made its main internal codebase private; a public snapshot and Software Heritage archives exist.
• A company representative cites:
  • Need to “focus” and reduce complexity of mixing open and closed components.
  • Abuse/anti-abuse logic for the AI product needing to live in private repos.
  • Confusion between open-source and enterprise builds, and migration pain between them.
  • Very few external contributions or customers truly relying on the OSS build.
  • Competitive risk (e.g., large competitors monitoring the public repo) and procurement using code visibility to negotiate.
  • Easier distribution/partner deals once code is no longer open, including a large ARR contract attributed to this shift.

Reactions to the open source shift

• Some accept the move as a hard but reasonable business decision in a tough startup market.
• Others view it as a “rug pull” after years of branding around openness, or as using open source as marketing and then closing it once successful.
• Debate centers on whether simply publishing tarballs (without support) would still carry significant overhead and risk.
• Broader argument over what “open source” implies: rights vs. expectations of long-term openness, support, and community.

Public code search index changes

• Users report many GitLab and low-star repos disappearing from public search, breaking “long tail” use cases.
• The company confirms culling non‑GitHub and low-star repos due to rate limits, scale, and cost, while keeping ~1M mostly GitHub repos.
• Some are grateful for the still-free service; others are frustrated that obscure, low-star academic or niche projects are now hard to search.

Pricing, market focus, and sustainability

• Current pricing (~$49/user/month with high minimum seat counts) is widely seen as too expensive for individuals and smaller companies.
• Commenters note that any tool indexing proprietary code inevitably triggers heavy security/procurement processes, pushing vendors toward larger customers.
• Some users would like a mid-tier or cheaper option; a representative hints that lower-priced code search tiers are being considered.

Alternatives, forks, and workarounds

• Alternatives mentioned: Hound, grep.app, and various Lucene-based tools; most are seen as weaker than Sourcegraph’s UX/search quality.
• Some run frozen forks of the last open version (e.g., community-maintained images) behind their own auth proxies.
• Others plan to continue using the public hosted search while it remains available.

Broader reflections on open source and startups

• Several argue startups shouldn’t begin as open source if they can’t sustain it; better to open up later.
• Others stress that transparency and clear expectation-setting matter more than the initial licensing choice.
• There is tension between appreciating years of free value and disappointment at loss of openness and documentation/handbook transparency.