Why developers are ditching GitHub for this nonprofit alternative


You probably know that GitHub isn’t your only option for code management, but you’re probably not aware about the many alternatives we have out there. One alternative that’s currently gaining momentum is Codeberg, but what is it about?

What’s Codeberg?

Codeberg is a free, open-source code hosting platform that has been quietly building a loyal following among developers who want an alternative to the increasingly corporate nature of mainstream platforms. Founded in 2019 and headquartered in Berlin, Germany,Codeberg is operated by a nonprofit association called Codeberg e.V., which means its direction is guided by its community rather than shareholders or profit motives. The platform is built on top of Forgejo, a community-maintained fork of the Gitea software, which itself is a lightweight self-hostable Git service. This foundation gives Codeberg a familiar feel for anyone who has used GitHub or GitLab, while keeping the underlying infrastructure transparent and auditable by anyone who cares to look.

What sets Codeberg apart from the start is its mission. The platform exists specifically to provide a home for free and open-source software projects, and that purpose shapes every decision made about how it operates. There are no venture capital investors pushing for monetization strategies, no advertising, and no data harvesting. The service is funded entirely through donations and membership fees from the developer community that uses it. That model has resonated strongly with developers who grew uncomfortable after Microsoft acquired GitHub in 2018, or who became frustrated with GitLab’s gradual shift toward enterprise-focused features that left individual developers and small teams with a product that felt less and less tailored to their needs.

Codeberg supports all the standard features developers expect from a modern code hosting platform, including repository management, issue tracking, pull requests, wikis, and project boards.

How is it better than GitHub?

Privacy, simplicity, and freedom from corporate pressure

A mobile phone with logo of distributed version control system Git on screen in front of website. Credit: Shutterstock/T. Schneider

Comparing Codeberg to GitHub directly is a useful exercise, though it requires some honesty about tradeoffs. GitHub is undeniably larger, more feature-rich, and more deeply integrated into the broader software ecosystem. Millions of developers, organizations, and open-source projects call it home, and its network effects are genuinely powerful. But that scale comes with consequences, and a growing number of developers argue that those consequences are worth taking seriously.

The most immediate practical advantage Codeberg offers is privacy. GitHub, under Microsoft, collects substantial amounts of user data and integrates tightly with other Microsoft services. Codeberg’s nonprofit structure means there is no business model that depends on what you do with your code or how you interact with the platform. Your activity is not being analyzed to train commercial AI systems, and your repositories are not being indexed to feed products you never agreed to support. This became a particularly charged issue in 2022 and 2023 when GitHub Copilot, trained on public repositories, sparked fierce debate and (justified) ourtage about consent and compensation within the open-source community.

Other than privacy, Codeberg is meaningfully simpler to use. GitHub has accumulated years of features, integrations, and interface changes that have made it increasingly cluttered. Codeberg’s interface is clean, fast, and focused. Everything loads quickly, the navigation is intuitive, and developers report spending less time managing the platform and more time actually writing code. For independent developers and small teams who do not need GitHub Actions pipelines or enterprise compliance dashboards, that simplicity is a genuine quality-of-life improvement.

There is also an ideological dimension that matters to many users. Contributing to and hosting code on a platform that is itself open-source creates a kind of consistency between values and behavior that many in the open-source community find meaningful.

Should you use it?

The right choice depends on what you actually need

An illustration showing a blue JSONC file icon, a dark code window with comment lines and white curly brace symbols. Credit: Lucas Gouveia/How-To Geek

Whether Codeberg is the right platform for you depends largely on what you are trying to accomplish and how much weight you place on the values the platform represents. For developers working on personal projects, contributing to open-source software, or running small team repositories, Codeberg is a genuinely compelling option. It handles everything a typical workflow requires, it is free to use, and it operates in a way that aligns with the principles many open-source developers already hold.

The honest answer is that if your work depends heavily on GitHub’s ecosystem, including its integrations with CI/CD tools, third-party applications, or large organizational workflows, migrating entirely is not a trivial undertaking. Many companies and open-source projects maintain a GitHub presence simply because that is where visibility and contributors come from. Discoverability on Codeberg is still more limited than on GitHub, and the community, while growing, is smaller. These are real constraints worth acknowledging.

That said, Codeberg does not have to be an all-or-nothing decision. Many developers mirror their repositories on Codeberg while maintaining a GitHub presence, treating it as a backup, a statement of intent, or a primary home for projects where community values matter more than maximum exposure. Codeberg also continues to grow at a steady pace, with tens of thousands of active users and a development roadmap that is shaped by genuine community input rather than corporate strategy.

If you have never tried it, the barrier to entry is low enough that experimentation costs very little. The platform is available at codeberg.org, registration takes minutes, and importing existing repositories from GitHub is straightforward. For anyone who has been looking for a reason to reduce their dependence on big-tech infrastructure in their development workflow, Codeberg makes a compelling and surprisingly practical case.


The simplest case for a simpler, freer platform

Codeberg proves that open-source code hosting does not need corporate backing to be reliable, capable, and worth using. For developers who value privacy, simplicity, and alignment between their tools and their principles, it is perhaps one of the most refreshing options available today.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


The Windows Insider Program is about to get much easier

Ed Bott / Elyse Betters Picaro / ZDNET

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • Microsoft is making the Insider Program less complicated.
  • Beta channel will be a more reliable preview of the next retail release.
  • Other changes will allow testers to quickly enable/disable new features.

Last month, Microsoft took official notice of its customers’ many complaints about Windows 11. Pavan Davaluri, the executive vice president who runs the Windows and Devices group, promised sweeping changes to Windows 11. Today, the company announced the first of those changes in a post authored by Alec Oot, who’s been the principal group product manager for the Windows Insider Program since January 2024.

Those changes will streamline the Insider program, which has lost sight of its original goals in the past few years. (For a brief history of the program and what had gone wrong, see my post from last November: “The Windows Insider Program is a confusing mess.”)

Also: If Microsoft really wants to fix Windows 11, it should do these four things ASAP

If you’re currently participating in the Windows Insider Program, these are meaningful changes. Here’s what you can expect.

Simplifying the Insider channel lineup

Throughout the Windows 11 era, signing up for the Insider program has required choosing one of four channels using a dialog in Windows Settings. Here’s what those options look like today on one of my test PCs.

insider-program-channels-lineup-old

The current Insider channel lineup is confusing, to say the least.

Screenshot by Ed Bott/ZDNET

Which channel should you choose? As the company admitted in today’s post, “the channel structure became confusing. It was not clear what channel to pick based on what you wanted to get out of the program.”

The new lineup consists of two primary channels: Experimental and Beta. The Release Preview channel will still be available, primarily for the benefit of corporate customers who want early access to production builds a few days before their official release. That option will be available under the Advanced Options section.

windows-insider-channel-lineup-new

This simplified lineup is easier to follow. Beta is the upcoming retail release, Experimental is for the adventurous.

Screenshot courtesy of Microsoft

Here’s Microsoft’s official description of what’s in each channel now, with the company’s emphasis retained:

  • Experimental replaces what were previously the Dev and Canary channels. The name is deliberate: you’re getting early access to features under active development, with the understanding that what you see may change, get delayed, or not ship at all. We’ve heard your feedback that you want to access and contribute to features early in development and this is the channel to do that.
  • Beta is a refresh of the previous Beta Channel and previews what we plan to ship in the coming weeks. The big change: we’re ending gradual feature rollouts in Beta. When we announce a feature in a Beta update and you take that update, you will have that feature. You may occasionally see small differences within a feature as we test variations, but the feature itself will always be on your device.

These changes will apply to the Windows Insider Program for Business as well.

Offering a choice of platforms

For those testers who want to tinker with the bleeding edge of Windows development, a few additional options will be available in the Experimental channel. These advanced options will allow you to choose from a platform that’s aligned to a currently supported retail build. Currently, that’s Windows 11 version 25H2 or 26H1, with the latter being exclusively for new hardware arriving soon with Snapdragon X2 Arm chips.

Also: Microsoft account vs. local account: How to choose

There will also be a Future Platforms option, which represents a preview build that is not aligned to a retail version of Windows. According to today’s announcement, this option is “aimed at users who are looking to be at the forefront of platform development. Insiders looking for the earliest access to features should remain on a version aligned to a retail build.”

windows-insider-advanced-options-new

The Future Platforms option is the equivalent of the current Canary channel

Screenshot courtesy of Microsoft

Minimizing the chaos of Controlled Feature Rollout

Last month, I urged Microsoft to stop using its Controlled Feature Rollout technology, especially for builds in the Beta channel. Apparently, someone in Redmond was listening.

One of the most common questions we receive from Insiders is “why don’t I have access to a feature that’s been announced in a WIP blog?” This is usually due to a technology called Controlled Feature Rollout (CFR), a gradual process of rolling out new features to ensure quality before releasing to wider audiences. These gradual rollouts are an industry standard that help us measure impact before releasing more broadly. But they also make your experience unpredictable and often mean you don’t get the new features that motivated many of you to join the Insider program to begin with.

Moving forward, Insider builds in the Beta channel will no longer suffer from this gradual rollout of features. Meanwhile, the company says, “Insiders in the Experimental channel will have a new ability to enable or disable specific features via the new Feature Flags page on the Windows Insider Program settings page.”

windows-insider-feature-flags

Builds in the Experimental channel will include the option to turn new features on or off.

Screenshot courtesy of Microsoft

Not every feature will be available from this list, but the intent is to add those flags for “visible new features” that are announced as part of a new Insider build.

Making it easier to change channels

The final change announced today is one I didn’t see coming. Historically, leaving the Windows Insider Program or downgrading a channel (from Dev to Beta, for example) has required a full wipe and reinstall. That’s a major hurdle and a big impediment to anyone who doesn’t have the time or technical skills to do that sort of migration.

Also: Why Microsoft is forcing Windows 11 25H2 update on all eligible PCs

Beginning with the new channel lineup, it should be easier to change channels or leave the program without jumping through a bunch of hoops.

To make this a more streamlined and consistent experience, we’re making some behind the scenes changes to enable Insider builds to use an in-place upgrade (IPU) to hop between versions. This will allow in most cases Insiders to move between Experimental, Beta, and Release Preview on the same Windows core version, or leave the program without a clean install. An IPU takes a bit more time than your normal update but migrates your apps, settings, and data in-place.

If you’ve chosen one of the future platforms from the Experimental channel, those options don’t apply. To move back to a supported retail platform, you’ll need to do a clean install.

Also: Apple, Google, and Microsoft join Anthropic’s Project Glasswing to defend world’s most critical software

The upshot of all these changes should make things a lot clearer for anyone trying to figure out what’s coming in the next big feature update. Beta channel updates, for example, should offer a more accurate preview of what’s coming in the next big feature update, so over the next month or two we should get a better picture of what’s coming in the 26H2 release, due in October.

When can we start to see those changes rolling out to the general public? Stay tuned.





Source link