GitHours vs Git Invoice
Both start from git history and end at something you hand a client — GitHours reconstructs a time report from your commit history, while Git Invoice asks you to type the hours in yourself and produces a PDF-style invoice.
At a glance
- AvailabilityGit Invoice
- Pre-launch — waitlist only
- How hours are producedGit Invoice
- Entered manually per contribution
- Repository connectionGit Invoice
- GitHub OAuth only
- OutputGit Invoice
- PDF-style invoice
Facts verified 2026-07-29
Derived hours vs typed hours
GitHours reconstructs how long a session took from the timestamps already on your commits, using gap-threshold session detection — the number comes from the git history itself. Git Invoice's described flow is different: after connecting a repository and picking commits or pull requests, the user adds the hours spent on each contribution by hand. Its own copy calls this out directly: “Track Your Time — Easily add the hours spent on each contribution.” When a client asks where a number on an invoice came from, “I typed it in” and “it was reconstructed from timestamped commits” are different answers.
A waitlist, not a product yet
Git Invoice is pre-launch. Its own tagline reads “ Simplify Your Work Invoicing from GitHub Contributions”, but there is no working product to sign into yet — the page's primary call to action is Join waitlist, and its footer says: “We're working hard to make Git Invoice perfect for you. In the meantime, sign up to know when we launch.” That is a normal state for an unreleased product, not a reason to discount it.
What they say about your data
Git Invoice publishes several stated commitments about how it plans to handle the GitHub data it will eventually request access to:
“We use GitHub's secure OAuth flow for authentication, never storing your GitHub credentials.”