GitSeer
See what needs attention across your forges
Self-hosted console for Gitea, Forgejo, GitHub, GitLab, and Bitbucket Cloud: repositories, open pull requests, workflow runs, and attention items — without hopping repo to repo.
Open source · Built by ncdLabs · Docs in the repository README
Released
One Ops Console Across Your Forges
Your forges stay the system of record. GitSeer syncs over API and webhooks so you can answer what needs attention right now from a single ACL-aware view.
-
Attention
CI failures, review waits, long-running runs, merge conflicts, and related operational items in one list.
-
Pull Requests & Pipelines
Open PRs with CI state, workflow runs grouped by repository, and on-demand job logs.
-
Live Updates
SSE keeps the console current as webhooks land — no full-page refreshes to chase status.
-
Setup Wizard
Connect Gitea, Forgejo, GitHub, GitLab, or Bitbucket, validate credentials, and finish. Add more instances any time from Settings.
Screenshots
Click any screenshot to open the full-size view. Repo names in these shots are substituted placeholders.
-
Dashboard · Time-scoped summary and trends across accessible repos. -
Attention · Prioritized operational items, filterable by forge. -
Pull Requests · Open PRs with CI and review state. -
Pipelines · Workflow runs grouped for ops triage.
Self-Hosted
GitSeer runs on your infrastructure (Compose or Helm). SQLite by default; Postgres for multi-replica. Login is bootstrap password and/or forge OAuth (PKCE). Inventory sync uses a per-instance service token.
Source, install docs, and Helm chart live on github.com/ncdlabs/gitseer.
Get The Code
Install it against your forge instances, or open an issue if something in the ops console should work differently.