Project ideas from Hacker News discussions.

Why developers are ditching GitHub for Codeberg and self-hosting alternatives

📝 Discussion Summary (Click to expand)

1. Discontent with GitHub/Microsoft
Many users criticize GitHub’s reliability, moral stance, and Microsoft’s influence.
- “Our CI for our entire org at https://github.com/lightningdevkit was turned off for 3 weeks because an outside contributor who was wrongfully banned made a PR. After multiple appeals we received no explanation and was told it was a permanent ban until we made a stir on twitter.”benthecarman
- “Microsoft is a morally bankrupt and despicable organization, just like Meta, Amazon, and modern Google and Apple.”sneak
- “It's not technical difficulties, politics, nor AI. It's Microsoft. Like Apple, Facebook etc, I have a deep loathing for Microsoft and I want to remove as much of it from my life as I am able.”My_Name

2. Migration to self‑hosted alternatives (Gitea/Forgejo/Codeberg)
Commenters report positive experiences after moving to self‑hosted forges, citing performance, control, and feature parity.
- “I self-host Gitea … act runners for github actions alternative … I'm extremely satisfied with that setup. It is batteries included & fire and forget.”hambos22
- “Forgejo is pretty close. Its runners are largely compatible with GH’s, and its issues, labels, tags, releases, wikis, packages, branch protection, secrets/envs, signing keys, repo permissions, etc. are all largely identical.”nativeit
- “We ditched GitHub for self-hosted Forgejo and could not be happier. The experience is smoother, faster and distraction‑free.”klaussilveira

3. Skepticism about the claimed “mass exodus” trend
Several participants argue that the article overstates the shift, demanding evidence before accepting a trend.
- “Sentiment for/against GitHub aside... 'Why X are doing Y' articles like these pretend that the premise of 'X are doing Y' is true, conveniently skipping to the 'Why' before proving that the premise is even accurate in any meaningful way.”jorisw
- “If there's a trend to leave a platform it won't start with the most entrenched users (largest repos).”close04
- “If there's a trend […] The burden of proof is on the author here to show there's been an increase and they don't do that.”esperent

4. Concerns about AI training, data scraping, and privacy
Developers express worry that their code is being harvested for AI models and discuss ways to limit exposure.
- “Mostly because developers (me included) don't like to be told we are being laid off due to AI that was trained on our free open-source hobby projects.”littlecranky67
- “Quite a few commentors here mentioned using gitea or one of it's forks on a private tailnet. That would mean it isn't publicly available and can't be scraped.”_heimdall
- “FYI that Codeberg is currently holding a vote to broadly ban projects written mostly using AI, so its not a neutral space for hosting your projects like GitHub.”intunderflow


🚀 Project Ideas

GitVault

Summary

  • A lightweight backup daemon that mirrors any GitHub repository to multiple independent hosts (Gitea, Forgejo, Codeberg) in real‑time and alerts on account bans or rate‑limits.
  • Guarantees zero data loss and seamless migration without manual exports.

Details

Key Value
Target Audience Open‑source maintainers, small teams, and privacy‑concerned developers who rely on GitHub for public repos but fear bans or service outages.
Core Feature Real‑time multi‑host mirroring with automated conflict resolution and ban‑detection webhook.
Tech Stack Rust backend, PostgreSQL for sync state, Docker Compose, optional Gitea/Forgejo API adapters, Prometheus monitoring.
Difficulty Medium
Monetization Revenue-ready: Free self‑hosted tier; Cloud-hosted managed tier $9 /mo per active repo.

Notes

  • HN users repeatedly lament “CI blackouts” and “wrongful bans”; GitVault solves loss of access and provides an instant fail‑over.
  • The tool’s declarative configuration fits the “infrastructure as code” mindset popular on the forum.

PrivGit

Summary

  • An end‑to‑end encrypted Git hosting service that stores repository contents only decrypted on the client, preventing even the provider from seeing private code.
  • Offers GitHub‑compatible UI while keeping data private by design.

Details

Key Value
Target Audience Individual developers and small teams who need truly private source control without paying for corporate solutions.
Core Feature Zero‑knowledge encryption of every repository; Git‑compatible push/pull via a thin client library.
Tech Stack Go microservice, libsodium libs for encryption, SQLite for metadata, gRPC for client communication, React front‑end (self‑hosted).
Difficulty High
Monetization Revenue-ready: Tiered subscription – $4 /mo per user for 5 private repos, $12 /mo for unlimited storage.

Notes

  • Commenters like “cryo32” and “rob” expressed desire to “self‑host” and “don’t give a shit about public profile”; PrivGit satisfies that wish while remaining user‑friendly.
  • The zero‑knowledge model directly addresses distrust toward Microsoft‑owned GitHub.

CIHub‑in‑a‑Box

Summary

  • A one‑click deployable CI/CD platform that allocates isolated runner quotas per repository, preventing “entire org CI” shutdowns caused by single bad PR.
  • Integrates with GitHub, GitLab, and other forges to provide guaranteed run minutes.

Details

Key Value
Target Audience DevOps engineers and maintainers of multiple open‑source projects who have been affected by GitHub’s CI blackouts.
Core Feature Per‑repo runner pools with automatic scaling on demand and credit‑based usage accounting.
Tech Stack Kubernetes with KEDA, Tekton pipelines, Redis for credit tracking, Docker containers for runners, Helm charts for deployment.
Difficulty High
Monetization Hobby (open‑source core) with optional managed SaaS $7 /mo per 100 build minutes.

Notes

  • Repeated grievances about “CI for our entire org turned off” signal a clear market gap; CIHub‑in‑a‑Box offers a bullet‑proof alternative.
  • The credit system resonates with users who valued GitHub’s free action credits but lost them after policy changes.

CodeBridge

Summary

  • A unified UI layer that wraps any Git‑compatible forge (GitHub, Codeberg, Gitea, Forgejo) presenting a consistent GitHub‑like experience while letting users switch providers under the hood.
  • Enables seamless migration and reduces the learning curve when adopting alternatives.

Details

Key Value
Target Audience Developers who love GitHub’s UI but want to flee Microsoft’s ecosystem; teams evaluating multiple forges for resilience.
Core Feature Pluggable provider adapters that expose identical issue, PR, and wiki interfaces across disparate back‑ends.
Tech Stack Electron front‑end, TypeScript, provider SDK (Go), GraphQL abstraction layer, Docker for isolated provider containers.
Difficulty Medium
Monetization Revenue-ready: SaaS instance $6 /mo per user with admin analytics; open‑source core on GitHub.

Notes

  • HN discussions about “UI is intuitive” and frustration with “switching costs” illustrate demand for a universal interface; CodeBridge addresses it directly.
  • The abstraction layer encourages community contributions to support new forges, fostering a vibrant ecosystem.

Read Later