Gitdot - Open-Source GitHub Alternative in Rust

TL;DR

TL;DR: Gitdot is an open-source GitHub alternative written in Rust, focusing on code quality with stacked diffs for reviews and a secure CI/CD platform, deliberately avoiding AI features.

Source and Accuracy Notes

• Project page: gitdot.io
• Source repository: github.com/bkdevs/gitdot
• License: Apache-2.0 (verified via GitHub API license.spdx_id)
• HN launch thread: news.ycombinator.com/item?id=45421302
• Source last checked: 2026-06-17

What Is Gitdot?

Gitdot positions itself as “a better GitHub” — an open-source Git hosting platform built from scratch in Rust. The project launched on June 4, 2026, and quickly gained traction with 334 points on Hacker News.

Unlike GitHub’s feature-bloat approach, Gitdot focuses on three core pillars:

1. Hyper-performant Git server written in Rust
2. Code review tool using stacked diffs as the primitive
3. CI/CD platform that is secure by design, locally testable, and reproducible

The project is explicitly anti-AI-hype. From their FAQ:

“We view AI as an implementation detail — and do not think that using it is necessarily good. In fact, we think it makes many products worse by acting as a bandaid for poor design.”

Current Status and Roadmap

Gitdot is currently at v0.1 (released June 4, 2026). The roadmap is public and time-bound:

| Version | Feature | ETA | |---------|---------|-----| | v0.1 | Hello world | ✅ Released Jun 4, 2026 | | v0.2 | Infra & issues | July 15, 2026 | | v0.3 | Reviews (stacked diffs) | Sep 1, 2026 | | v0.4 | CI/CD platform | Q4 2026 |

The project is built by two developers in Brooklyn, funded by a small pre-seed round from friends and personal savings. They are financially independent and building for the long term.

Key Differentiators

1. Stacked Diffs for Code Review

Instead of GitHub’s pull request model, Gitdot uses stacked diffs — a workflow popularized by Phabricator and used internally at companies like Facebook and Uber. This allows developers to:

• Build chains of dependent changes
• Update individual diffs without affecting the stack
• Review smaller, more focused changes

2. Rust-Based Performance

The Git server is written in Rust, promising better performance and memory safety compared to traditional Git implementations. This is critical for large repositories and high-traffic scenarios.

3. No AI Features

In a market where every tool is adding AI copilot features, Gitdot deliberately avoids this. Their stance: AI is an implementation detail, not a product feature. They plan to be “judicious” in any future AI use rather than bolting it on for marketing.

4. Privacy and Data Sovereignty

• No data selling or training on user code
• Free repositories (may charge for private team repos later)
• Plans for end-to-end encrypted git protocol
• Apache-2.0 license with commitment to never change it

Getting Started

Gitdot is currently in early access. You can sign up at gitdot.io/signup.

The platform supports:

• Public repositories (free)
• Git operations (clone, push, pull)
• Basic repository browsing
• Stars and trending

Missing features (coming in v0.2-v0.4):

• Issue tracking
• Code review UI
• CI/CD pipelines
• Private repositories for teams

Technical Architecture

The project is open source under Apache-2.0. The codebase is primarily Rust, with a Next.js frontend. Design decisions are documented in the /designs folder, and weekly progress updates are in /weeks.

GitHub repository: github.com/bkdevs/gitdot (26 stars as of June 17, 2026)

Practical Evaluation Checklist

Before migrating to Gitdot, consider:

• [ ] Maturity: v0.1 is minimal — no issues, reviews, or CI yet
• [ ] Timeline: Core features (reviews, CI) arrive Sep-Dec 2026
• [ ] Team size: Two-person team — bandwidth risk
• [ ] Ecosystem: No GitHub Actions equivalent yet
• [ ] Migration path: Standard git protocol — easy to move repos, hard to move history/reviews
• [ ] Funding: Pre-seed from friends + personal savings — sustainable but limited

Good fit for:

• Early adopters who want to support open-source infrastructure
• Teams frustrated with GitHub’s direction
• Developers who prefer stacked diffs
• Projects that don’t need CI/reviews yet

Wait for v0.3+ if you need:

• Code review workflows
• CI/CD pipelines
• Issue tracking
• Private team repositories

Security Notes

Gitdot makes several security-focused promises:

1. No data selling: Explicit commitment in privacy policy
2. No AI training: Won’t use your code to train models
3. E2EE git protocol: Planned for future (not yet implemented)
4. Open source: Apache-2.0 — auditable codebase
5. Local CI testing: CI will be reproducible locally

Current security posture is basic (v0.1), but the architecture prioritizes security from the start rather than bolting it on later.

FAQ

Q: Is Gitdot a fork of GitHub or Gitea? A: No. Gitdot is built from scratch in Rust. It’s not a fork of any existing Git platform.

Q: Can I self-host Gitdot? A: The code is Apache-2.0 licensed, so self-hosting is legally allowed. However, there are no self-hosting instructions yet (v0.1 is hosted only). Check back after v0.2.

Q: Will Gitdot support GitHub Actions? A: Not GitHub Actions specifically. v0.4 (Q4 2026) will introduce a CI/CD platform that is “secure by design, locally testable and reproducible” — likely a different model.

Q: Why stacked diffs instead of pull requests? A: Stacked diffs allow smaller, more focused reviews and better handling of dependent changes. This is the same model used at Facebook, Uber, and other large-scale engineering orgs.

Q: Is Gitdot production-ready? A: Not yet. v0.1 is a “hello world” — basic git hosting with no reviews, issues, or CI. Wait for v0.3 (Sep 2026) for code review, v0.4 (Q4 2026) for CI.

Q: How does Gitdot make money? A: Currently free. They plan to charge for private repositories for teams in the future. The founders are financially independent and funded by a small pre-seed from friends.

Conclusion

Gitdot is an ambitious attempt to build a better GitHub from first principles. The Rust-based performance focus, stacked diffs for code review, and deliberate avoidance of AI hype are refreshing in a market saturated with AI-washed developer tools.

However, v0.1 is minimal. The real test comes with v0.3 (reviews, Sep 2026) and v0.4 (CI, Q4 2026). If the team delivers on their roadmap, Gitdot could become a serious alternative for teams frustrated with GitHub’s direction.

For now, it’s worth watching and experimenting with for non-critical projects. If you value open-source infrastructure and want to support an alternative to GitHub’s monopoly, signing up early helps the project gain traction.

Links:

• Website: gitdot.io
• GitHub: github.com/bkdevs/gitdot
• HN discussion: news.ycombinator.com/item?id=45421302