GitSeer
Open-source PR & CI dashboard for all your git forges
4 followers
Open-source PR & CI dashboard for all your git forges
4 followers
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.
Launch Team
LoomHit record, hand off to AI
Promoted
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?