Why I'm leaving GitHub for Forgejo

For years, GitHub has been the dominant force in code hosting. It's where I’ve housed personal projects, contributed to open source, and even used extensively within regulated financial environments. But recently, I’ve made a significant decision: I’m migrating away from GitHub and towards Forgejo. This wasn’t a light choice, and it’s driven by a confluence of factors that, particularly for those of us in the finance industry, are becoming increasingly important.

This article will detail my reasoning, exploring the specific concerns that led to this move and why Forgejo offers a compelling alternative. I’ll cover everything from data security and vendor lock-in to cost and the philosophical shift happening within the GitHub ecosystem. I’ll also touch on what Forgejo is and how it stacks up against other options like GitLab and Gitea.

§The Shifting Sands at GitHub: Why Concern is Growing

GitHub, under Microsoft’s ownership, has been evolving. While many changes have been positive for casual users, some have raised red flags for professionals, especially those operating in heavily regulated fields like finance. These aren't necessarily bad changes in isolation, but collectively they point towards a platform less focused on the core principles of open source and developer freedom.

§Here are the key concerns that began to accumulate:

• Increased Commercialization: GitHub has become increasingly focused on enterprise features and monetization. While a profitable business is understandable, the shift feels increasingly at odds with the spirit of open source.
• Copilot Integration & Data Privacy: The integration of Copilot, while a powerful tool, brought concerns about code privacy and licensing. Sending proprietary financial models to a cloud-based AI, even with assurances of anonymization, is a risk many firms aren't willing to take. Imagine a trading algorithm's core logic inadvertently influencing the training data for a competitor’s AI. The potential fallout is significant.
• Dependence on a Single Vendor (Vendor Lock-in): Relying entirely on one company for critical infrastructure creates a single point of failure and limits flexibility. In finance, regulatory compliance often requires redundancy and the ability to quickly switch providers.
• Changes to API Access & Rate Limits: Increasingly restrictive API access and rate limits make automation and custom tooling – which are vital for many financial applications – more difficult and expensive. We heavily used the API for automated compliance checks and report generation.
• Content Moderation Concerns: While content moderation is important, the increasingly broad scope of GitHub’s moderation policies raises concerns about potential censorship and arbitrary removal of legitimate code repositories.

These points, individually, might not be deal-breakers. But taken together, they represent a worrying trend that prompted me to look for alternatives. We deal with highly sensitive financial data. Accepting increased risk in our development pipeline isn’t an option.

§Introducing Forgejo: A Community-Focused Fork of Gitea

So, what is Forgejo? Simply put, Forgejo (https://forgejo.com/) is a self-hosted Git service forked from Gitea. It aims to provide a free and open-source alternative to GitHub, GitLab, and other centralized platforms. It's built with Go, making it lightweight, fast, and easy to install.

Image Suggestion: A screenshot of the Forgejo interface, highlighting the clean and minimalist design.

The critical difference between Forgejo and its parent Gitea is its commitment to remaining a fully community-driven project. Gitea has shifted towards a more corporate governance model, which concerned many in the open-source community. Forgejo was created specifically to prevent that shift, and it’s governed by a clear Code of Conduct and a strong focus on user needs.

§Key features of Forgejo include:

• Self-Hosting: You have complete control over your data and infrastructure. This is huge for finance, allowing you to meet stringent security and compliance requirements.
• Git-Based: It supports all the standard Git features you’d expect, including branching, merging, pull requests, and more.
• Web Interface: A user-friendly web interface for managing repositories, issues, and projects.
• Issue Tracking: Robust issue tracking system for managing bugs, features, and tasks.
• Wiki & Project Management: Built-in wiki and basic project management tools.
• Lightweight and Fast: Forgejo is designed to be efficient, even on modest hardware.
• Open Source: Licensed under the MIT license, giving you the freedom to modify and distribute the code.

§Why Forgejo is a Better Fit for Finance Professionals

For a finance professional, the benefits of Forgejo extend far beyond simply avoiding Microsoft’s ecosystem. Here’s a detailed look at why it’s a superior choice:

• Data Sovereignty & Compliance: Self-hosting allows you to keep your code and data within your own infrastructure, ensuring compliance with regulations like GDPR, CCPA, and industry-specific financial regulations. This is non-negotiable for many firms.
• Enhanced Security: You control the security of your environment. You can implement your own security policies, access controls, and auditing procedures. No more relying on a third-party’s security measures (which, while generally good, aren’t your controls).
• Reduced Vendor Lock-in: You're not tied to a single vendor. If Forgejo doesn’t meet your needs in the future, you can easily migrate to another Git service or even maintain your own custom solution.
• Customization & Automation: Forgejo's API, while still evolving, allows for greater customization and automation. We're rebuilding our automated compliance tooling around it, giving us far more control and flexibility than GitHub’s increasingly limited API allowed.
• Cost Savings: While there’s the cost of hardware and maintenance, self-hosting can often be cheaper than paying for GitHub Enterprise, especially for smaller teams. Even considering the cost of a dedicated server (https://example.com/ – for a server recommendation), it's a fraction of the cost.
• Privacy: No more concerns about Microsoft accessing or analyzing your code. Your data stays private and under your control.

§Forgejo vs. GitLab vs. Gitea: A Quick Comparison

Forgejo isn’t the only alternative to GitHub. GitLab and Gitea are also popular options. Here's a quick comparison:

§| Feature | Forgejo | GitLab | Gitea |

|---|---|---|---| | Licensing | MIT | MIT | MIT | | Self-Hosting | Yes | Yes | Yes | | Community Focus | Very High | Moderate | Shifting to Corporate | | Features | Core Git Features, Issue Tracking, Wiki | Comprehensive DevOps Platform (CI/CD, etc.) | Core Git Features, Issue Tracking, Wiki | | Complexity | Low | High | Low | | Resource Usage | Low | High | Low | | Ease of Installation | Easy | Moderate | Easy |

GitLab is a powerful, all-in-one DevOps platform, but it’s also complex and resource-intensive. It’s overkill for many teams, especially those primarily focused on code hosting and version control. Gitea is similar to Forgejo in terms of simplicity and resource usage, but Forgejo’s stronger commitment to community governance made it the more appealing choice for me.

§The Migration Process & Initial Impressions

Migrating from GitHub to Forgejo was surprisingly straightforward. Git makes it relatively easy to mirror repositories, and Forgejo provides import tools to help with the transition. The biggest challenge was rebuilding our automated tooling, but that was an opportunity to create a more robust and customized solution.

My initial impressions of Forgejo are overwhelmingly positive. It’s fast, responsive, and easy to use. The community is active and supportive. And the peace of mind knowing that I have complete control over my data is invaluable.

Image Suggestion: A screenshot showing the process of importing a GitHub repository into Forgejo.

§Is Forgejo Right for You?

Forgejo isn't a one-size-fits-all solution. If you're a casual user who doesn't care about data privacy or vendor lock-in, GitHub might still be a good choice.

§However, if you’re a finance professional, or anyone who:

• Handles sensitive data
• Requires strict compliance with regulations
• Values data sovereignty
• Wants to avoid vendor lock-in
• Prefers a community-focused, open-source solution

…then Forgejo is definitely worth considering. It’s a powerful, flexible, and secure alternative to GitHub that gives you the control and peace of mind you need.

§Disclaimer

Affiliate Disclosure: This article contains affiliate links (https://example.com/, etc.). If you purchase a product through one of these links, I may receive a commission. This does not affect the price you pay. I only recommend products and services that I believe are valuable and relevant to my audience. I have independently researched and evaluated Forgejo, and my opinions are my own.