A New Alternative to GitHub Has Arrived—Here's What You Need to Know
A New Alternative to GitHub Has Arrived—Here's What You Need to Know
A new project called Gitdot appeared on Hacker News on 8 June 2026. It is built as an alternative to GitHub—the world's largest code storage and collaboration platform—and the team behind it has already secured early funding. (Hacker News)
What Gitdot Does
Gitdot is a tool that lets organisations store and manage their code on their own servers instead of relying on a company-hosted platform. Think of it like the difference between renting an apartment and owning a house: with GitHub, your code lives on Microsoft's servers. With Gitdot, your code stays under your own roof.
At launch, Gitdot handles the basics: people can sign up, create organisations, and store both public and private code repositories. It can also copy code from GitHub in two different ways. The first is a mirror—your code stays on GitHub, but Gitdot keeps a copy that you can view and use. The second is a full move—you transfer everything, including the entire history of changes, from GitHub into Gitdot.
Right now, Gitdot does not include some features that GitHub users rely on every day: ways to review code changes, track bugs, or automatically test code when someone updates it. That is normal for a very early project. The team is building the foundation first and will add the fancier tools later.
Why the Team Chose Rust
Gitdot is written in Rust, a programming language. That choice matters more than it might sound.
Most competing projects are written in Go, an older language that is easier to learn. Rust is harder to learn and takes longer to compile—factors that can slow down contributors joining the project. However, Rust is safer: it prevents a whole class of security problems that other languages allow, and it handles heavy workloads more efficiently without needing a garbage collector (a background system that cleans up unused memory). For a tool that stores code and runs complex operations, that matters.
The choice also sends a signal about what kind of people the team wants to attract. Engineers who choose Rust tend to care deeply about correctness and speed at a systems level. That shapes who volunteers to help build the project.
The Bigger Picture: GitHub's Dominance and Alternatives
GitHub, owned by Microsoft, is by far the most popular code storage platform in the world. It has enormous advantages: everyone uses it, integrations with it are everywhere, and it is the default place where developers share work. Switching away from GitHub is not easy.
That said, alternatives do exist. GitLab offers both a hosted version and self-hosted software. Gitea and Forgejo are lightweight self-hosted options that have built real user bases. Sourcehut is another player. Each one makes different trade-offs between features and simplicity.
Gitdot now enters this crowded space and will need to explain why someone should use it instead. That could be because it is faster, more secure, simpler to use, or something else—but the team has not yet said clearly what the answer is.
A Question About the Funding
Gitdot's pre-seed funding raises a practical point worth understanding. When a small, early-stage company raises money, investors are not just betting on the code they see today. They are betting on a plan for how the company will make money eventually. For project like this, that usually means two things: a hosted version you pay for, like GitHub itself, and a fancier enterprise edition with extra tools for large companies. This is not confirmed for Gitdot, but it is the standard pattern.
We have seen this before. GitLab, which is now a public company, started in 2011 in almost the same way: open-source software, a small team, early funding, and then a split between a free community version and a paid commercial version. That model worked for GitLab, but it also meant drawing a line between what stayed free and what cost money. It is reasonable to watch Gitdot's roadmap for the same kind of fork in the road.
Why the Import Feature Matters
One design choice stands out: the team built import tools for copying code from GitHub before they finished the tools for reviewing and discussing code changes. That is strategic. It makes it easy for someone to test Gitdot without committing fully—they can run it alongside GitHub and see if they like it. That is smart for a young project that needs to build a user base.
The mirror option in particular is useful. It lets an organisation keep GitHub as their main hub but maintain a copy in Gitdot for backup or compliance purposes, without making a final choice about migration. Some regulated industries need this kind of redundancy.
What We Still Do Not Know
Several important details have not been announced yet. There is no word on the licensing terms—whether Gitdot will be fully open, partly restricted, or somewhere in between. There is no public information on how much money was raised, who provided it, or what experience the founding team has. The project has not said whether it considers itself ready for production use or still early-stage alpha software.
None of this is unusual for a very new announcement. But these are exactly the things a team would need to understand before deciding whether to use Gitdot for real work or help develop it.
What Happens Next
The market for code storage and collaboration tools moves slowly most of the time, then suddenly fast. GitHub's dominance took years to build and was not guaranteed. A project written in Rust, openly available, with tools to import from GitHub, and backed by investors, is a credible start.
Whether Gitdot actually changes how developers work at large scale depends on decisions the team has not yet made public. In the near term, what Gitdot offers is clear: a lighter, possibly faster option for teams that want to run their own code infrastructure instead of depending on a hosted platform. Some teams have that need—whether for cost, security, compliance, or just preference. That need is real, and it exists separate from any excitement about the launch.
