Developer migrates from GitHub to self-hosted Forgejo

Developer jorijn has migrated from GitHub to Forgejo, a self-hosted Git platform, to regain control over code and infrastructure [jorijn]. The shift reflects a growing number of developers rejecting centralized platforms in favor of self-hosted alternatives.

Forgejo, a community-driven fork of Gitea, enables full self-hosting with minimal resource requirements. jorijn cited GitHub’s proprietary model, data ownership concerns, and dependency on third-party infrastructure as key reasons for leaving [jorijn]. He now hosts his repositories on his own server, retaining full administrative control.

This move matters for three concrete reasons:

• Developers are actively voting with their repositories. jorijn’s public migration includes tooling scripts and documentation to help others follow, signaling a shift beyond mere criticism to actionable alternatives.

• Self-hosting is no longer niche. Forgejo supports modern Git workflows, CI/CD integration, and federation via ActivityPub — features once exclusive to enterprise platforms.

• The exit from GitHub isn’t about cost. It’s about reducing reliance on U.S.-based platforms subject to foreign jurisdiction and opaque policy changes, a concern echoed by developers in Europe and Asia [jorijn].

The broader trend isn’t just anti-GitHub — it’s pro-sovereignty. As more developers treat code hosting as critical infrastructure, self-hosted platforms like Forgejo, SourceHut, and GitLab CE are gaining traction not for novelty, but for operational independence.