SaaS Metrics
What works now: user signups, org creations, private/public repos, and importing GitHub repositories (both as read-only mirrors and full migrations). So basically, you can create, push and pull to a repo, but we don't have many features quite yet (issues, PRs, CI).What is a bit unique is: 1) we built it in Rust and 2) the website is a little odd. Its design is inspired by CLIs (e.g., fzf, broot, vim) instead of web apps, and as such, lacks some affordances that you might typically expect in favor of keyboard-driven instant navigations (we have the very ambitious goal of an FCP of 100ms). In case you're curious, here's how we we built it: https://gitdot.io/designsWe recognize that we're making some bold claims here and are also well aware that we have much to learn. Building software is still hard, and that's a fact we seem to relearn everyday.But we wanted to share what we built so far nonetheless.Cheers, thank y'all for reading, and till the next
—paul & mikkel.
Show HN: Gitdot – a better GitHub. Open-source, written in Rust
A keyboard-driven, CLI-inspired, open-source GitHub alternative built in Rust, prioritizing speed (100ms FCP) and core repository management, with a roadmap for advanced features.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
A keyboard-driven, CLI-inspired, open-source GitHub alternative built in Rust, prioritizing speed (100ms FCP) and core repository management, with a roadmap for advanced features.
Gitdot enters a highly competitive market dominated by GitHub, GitLab, and Bitbucket. Its differentiation lies in its Rust implementation for performance and security, and a CLI-inspired, keyboard-driven UI for power users. This targets a specific developer segment that values speed and efficiency over traditional web app affordances. While lacking advanced features like issues and CI, its focus on core repository management and migration capabilities provides a foundation. For B2B SaaS, this highlights the potential for niche, performance-optimized alternatives to established platforms, particularly for organizations seeking greater control, self-hosting options, or a highly customized developer experience.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is Gitdot – a better GitHub. Open-source, written in Rust?
Gitdot – a better GitHub. Open-source, written in Rust is analyzed by our AI as: A keyboard-driven, CLI-inspired, open-source GitHub alternative built in Rust, prioritizing speed (100ms FCP) and core repository management, with a roadmap for advanced features.. It focuses on Gitdot enters a highly competitive market dominated by GitHub, GitLab, and Bitbucket. Its differentiation lies in its Rust implementation for perfo...
Where did Gitdot – a better GitHub. Open-source, written in Rust originate?
Data for Gitdot – a better GitHub. Open-source, written in Rust was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Gitdot – a better GitHub. Open-source, written in Rust publicly launched?
The initial public indexing or launch date for Gitdot – a better GitHub. Open-source, written in Rust within our tracked developer communities was recorded on June 9, 2026.
How popular is Gitdot – a better GitHub. Open-source, written in Rust?
Gitdot – a better GitHub. Open-source, written in Rust has achieved measurable traction, logging over 175 traction score and facilitating 138 recorded discussions or engagements.
Which technical categories define Gitdot – a better GitHub. Open-source, written in Rust?
Based on metadata extraction, Gitdot – a better GitHub. Open-source, written in Rust is categorized under topics such as: Gitdot, better GitHub, Open-source, written in Rust.
Are there open-source alternatives related to Gitdot – a better GitHub. Open-source, written in Rust?
Yes, the GitHub ecosystem contains correlated projects. For example, a repository named Infatoshi/OpenSquirrel shares highly similar architectural descriptions and topics.
How does the creator describe Gitdot – a better GitHub. Open-source, written in Rust?
The original author or development team describes the product as follows: "What works now: user signups, org creations, private/public repos, and importing GitHub repositories (both as read-only mirrors and full migrations). So basically, you can create, push and pull to ..."
Community Voice & Feedback
Please, stop using "written in Rust" as some kind of advantage or killer feature.
>As of now, all repositories are free, but we do envision charging for private repositories for teams in the future.Please don’t do this.Charge a fair price, in fact find a fair price and double it.I don’t want a free GitHub clone, I want one that works.How about 50$50 private repos, 50GBs of git LFS storage. Add collaborators for free.Actually respond to customers. At this level you only need 1000 paying customers to make it worth while for 2 developers.
[flagged]
No mobile version, but I'm visiting from a tablet, should work at least if switch to "Desktop" in the browser manually. I don't care if I get horizontal scroll - not showing your visitors anything at all is an automatic "I'm out".Second, when I browsed from an actual desktop, and clicked on links for files it was all slow as hell - specifically the part when you click on a file an expect it to just load, you instead get: 1) some layout switch which looks like page reload 2) then it says "loading..." for several seconds.After looking at the source code, it appears to be React or similar frontend framework... Ugh. I don't know why people choose to use that stuff, just have a regular SSR which would work a hundred times faster and is more pleasant. And if you really want an SPA, don't use React, Vue or Svelte (and similar), it's horrible and always slow.Finally, since this appears to be a YC company, it shouldn't matter what's it written in. In fact, I don't even know why Rust would be a good thing here when Go or even Rails/Django would work just fine - but again, it just reinforces the meme that if it's written in Rust, you'll surely hear about it.Overall, the minimalism idea is welcomed, but it supposedly should appeal to people like myself and it doesn't for all the reasons I mentioned above.
Big fan of the design! Different but easy to get a hand of. Having /profile also be linked on the homepage with the other main pages for ease of navigation would be nice, the profile link at the bottom feels like it clashes with the rest of the UI to my eyes.
Interesting stuff! I really like the design philosophy you're applying here, where the browser/web behaviour is actually part of the UX. Pretty rare for web application nowadays!If I could make one suggestion, I really like the old MacOS "inspector" pattern. Basically a consistent way to get meta-information about any "thing" the user chooses to inspect. Your right sidebar is going towards that, but it would need some work to make it more consistent between views.GitHub's UI has these weird meta-states/restrictions that are so badly explained in the UI they feel like bugs. Each line gets a [...] menu in github which lets you see the blame/spawn a issue linking to it/get a permalink/etc. It's a totally different UI in the diff view, and then totally different again if you're looking at a comment referencing a line in a diff AND different if it's referencing a permalink to a line in a file, even if it's the same code that would be in that diff!I want the UI to have obvious "nouns". If the UI is showing me a line of code, even if it's in a diff view, let me "inspect" it and get the exact same meta-info + tools I get for lines of code anywhere. It's "a line", not a weird meta state of "a line, but you're in the comment of a PR linking to this line".Same concept applies to comments/commits/authors/etc. If the UI shows me a username, I should be able to pull up a "who is that again" inspector. Going into github's commit view, clicking on a name... and being sent to a filtered list of that person's commits makes zero sense to me because this is the ONLY place where that happens. That behaviour should be a "recent commits" button inside some "user inspector".
Love the idea of someone tackling this space in Rust, but please just make a normal UI, I have no idea what I am looking at.
I like the terminal aesthetics but please, for accessibility's sake, make input boxes look more like input boxes and buttons look like buttons.
The minimal look feels very refreshing, and yet it's not disorienting like many minimal web git UIs are in my experience; I actually feel like I know how to navigate this thing. Site feels very snappy too, especially with those instantly loading file previews when you hover. Congrats!
What's the differentiation against Forgejo going to be?
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.