I spent hours last month debugging why GitLab CI jobs were stuck "pending" despite having active runners. The issue? Tag mismatches and an offline runner that wasn't obvious in GitLab's UI.
HiveSpace connects to your GitLab instance and shows:
- Why each stuck job isn't running (mismatched tags, offline runners, capacity)
- Runner utilization and queue times at a glance
- Trends to spot degrading performance
Built because GitLab's built-in runner metrics require Ultimate tier + ClickHouse setup, and many teams (including mine) don't have that. Also, even with those, the "why is this specific job stuck?" question isn't answered clearly.
Privacy note: Your GitLab API token is stored locally in your browser (cookie) and never sent to our servers. The dashboard makes API calls directly from your browser to your GitLab instance.
HiveSpace connects to your GitLab instance and shows:
- Why each stuck job isn't running (mismatched tags, offline runners, capacity) - Runner utilization and queue times at a glance - Trends to spot degrading performance
Built because GitLab's built-in runner metrics require Ultimate tier + ClickHouse setup, and many teams (including mine) don't have that. Also, even with those, the "why is this specific job stuck?" question isn't answered clearly.
Privacy note: Your GitLab API token is stored locally in your browser (cookie) and never sent to our servers. The dashboard makes API calls directly from your browser to your GitLab instance.
Early beta available. Book a demo at https://calendly.com/hello-hivespace/30min or just try it directly.
Stack: Next.js, GitLab API, TypeScript. Works with GitLab SaaS and self-hosted.