Home

GitSeer

Self-hosted CI/CD and pull-request ops console for Gitea and GitHub. Technical IDs: binary/module/Helm gitseer, env GITSEER_*.

Aggregates repositories, open PRs, Actions/workflow runs, and attention items into one ACL-scoped UI. Each forge stays the system of record; GitSeer syncs via API and webhooks. Login is bootstrap password and/or Gitea OAuth (PKCE) and GitHub OAuth (PKCE). No forge fork, no per-repo agents, no SaaS dependency. GitLab and Bitbucket are Coming Soon.

Source	github.com/ncdlabs/gitseer
License	Apache-2.0
Maintainer	ncdLabs
README	README.md
In-repo docs	docs/
Live	gitseer.ncdlabs.com

Guides

• Getting Started
• Install
• Architecture
• Features
• Configuration
• Authentication and ACL
• Setup Wizard
• Attention Engine
• API Reference
• Webhooks and Sync
• Deployment
• Operations
• Development
• Troubleshooting

Features

• Dashboard — summary and stats (Now / 1 / 7 / 30 / 90 day windows)
• Inbox — authored / review / failing CI / blocked-on-me queue with saved filters
• Attention — critical / warning / waiting, mute/snooze, optional log tail
• Repositories — health rollup and failure clusters
• Pull requests — CI and review badges across accessible repos
• Pipelines — runs by action; rerun/cancel; Active Actions flyout / pop-out
• Notifications — self-hosted SMTP + Slack/Discord/generic HTTPS
• Setup wizard — Prepare → forge picker → Connect → Validate → Finish
• Settings — Preferences / Integration / Access / Notifications / Status
• SSE live updates, Prometheus metrics, retention purge, backup/restore CLI
• Optional Gitea custom-template links (install-ui / Download Gitea UI Snippets)

Not in scope

• Writing workflow YAML, owning runners, or replacing forge Actions
• GitLab / Bitbucket forge clients (Coming Soon)
• Redis / WebSockets
• ncdLabs-hosted notification relay

Specs (in-repo)

• PRD / technical spec
• Implementation plan