This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
GitSeer
Open-source PR & CI dashboard for all your git forges
GitSeer is a free, open-source, self-hosted dashboard that unifies pull requests and CI across Gitea, Forgejo, GitHub, GitLab, and Bitbucket. One "attention" feed surfaces what needs you: failed builds, PRs with red CI, merge conflicts, unreviewed PRs, stuck jobs. Single Go binary, embedded UI — SQLite by default, Postgres optional, Docker Compose included. Forge tokens encrypted at rest; read-only wallboard mode for the office TV. Apache 2.0, no tiers, no telemetry.
Hey everyone — I'm Lou, founder of NorthCoast DevOps, a DevSecOps consultancy.
My clients have code and automation spread across most of the major Git providers. Keeping track of which builds were failing and which PRs needed attention became a nightmare of tab-hopping.
So I built GitSeer: a self-hosted dashboard that gives you real-time and historical insight into PRs and CI activity across your repositories, whether you use one Git provider or several. It supports Gitea, Forgejo, GitHub, GitLab, and Bitbucket.
The core is an attention feed: failed default-branch builds, PRs with failing CI or merge conflicts, unreviewed PRs, and stuck jobs. There's also a wallboard mode for shared status screens.
You can run GitSeer as a single Go binary, anywhere Docker containers run, or on Kubernetes using the included Helm chart.
It uses SQLite by default, with optional Postgres, and supports verified webhooks with scheduled sync as a fallback, per-repository access controls, and forge tokens encrypted at rest with AES-256-GCM.
It's free and open source under Apache 2.0, with no telemetry.
I'd love your feedback: what do you find yourself checking manually across your repos, and what would GitSeer need to show to become part of your daily workflow?
About GitSeer on Product Hunt
“Open-source PR & CI dashboard for all your git forges”
GitSeer was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #159 on the daily leaderboard. GitSeer is a free, open-source, self-hosted dashboard that unifies pull requests and CI across Gitea, Forgejo, GitHub, GitLab, and Bitbucket. One "attention" feed surfaces what needs you: failed builds, PRs with red CI, merge conflicts, unreviewed PRs, stuck jobs. Single Go binary, embedded UI — SQLite by default, Postgres optional, Docker Compose included. Forge tokens encrypted at rest; read-only wallboard mode for the office TV. Apache 2.0, no tiers, no telemetry.
On the analytics side, GitSeer competes within Open Source, Software Engineering, Developer Tools and GitHub — topics that collectively have 673.8k followers on Product Hunt. The dashboard above tracks how GitSeer performed against the three products that launched closest to it on the same day.
Who hunted GitSeer?
GitSeer was hunted by Lou Grossi. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of GitSeer including community comment highlights and product details, visit the product overview.
Lou Grossi
Hey everyone — I'm Lou, founder of NorthCoast DevOps, a DevSecOps consultancy.
My clients have code and automation spread across most of the major Git providers. Keeping track of which builds were failing and which PRs needed attention became a nightmare of tab-hopping.
So I built GitSeer: a self-hosted dashboard that gives you real-time and historical insight into PRs and CI activity across your repositories, whether you use one Git provider or several. It supports Gitea, Forgejo, GitHub, GitLab, and Bitbucket.
The core is an attention feed: failed default-branch builds, PRs with failing CI or merge conflicts, unreviewed PRs, and stuck jobs. There's also a wallboard mode for shared status screens.
You can run GitSeer as a single Go binary, anywhere Docker containers run, or on Kubernetes using the included Helm chart.
Quickest start:
It uses SQLite by default, with optional Postgres, and supports verified webhooks with scheduled sync as a fallback, per-repository access controls, and forge tokens encrypted at rest with AES-256-GCM.
It's free and open source under Apache 2.0, with no telemetry.
I'd love your feedback: what do you find yourself checking manually across your repos, and what would GitSeer need to show to become part of your daily workflow?