Skip to main content

​
Story

You’re running 18 GitHub orgs. ~330 repos. Services in TypeScript, Rust, Go, Python. CI pipelines, integration tests, MCP servers, marketing deadlines, financial targets. The question that wakes you up at 2am isn’t “what’s the code doing?” — it’s “what did I forget?” HUBBLE is the answer. Named after the telescope that observes with extraordinary clarity from a fixed vantage point, HUBBLE is a read-only intelligence board that pulls from 7 data sources (GitHub, Linear, Vercel, ARES, PEBBLE, Stripe, Ramp) and presents 7 views:
  • Mission Control — 4-column kanban across all orgs with status derived from rules, not manually set
  • Orbit Map — SVG dependency graph showing which orgs are healthy, degraded, or critical
  • Sol Log — Chronological event feed with 6 alert rules that fire to Discord and email
  • Velocity — Throughput, cycle time, status distribution, Linear sprint progress
  • Campaigns — The one write surface: Gantt timeline for content drops, announcements, shoutouts
  • Launchpad — Financial progress toward the £8k/mo retirement threshold (full-access only)
  • Highlight Reel — Wins and milestones only, safe for observers

​
Meta Layer

HUBBLE doesn’t replace GitHub Issues, Linear, or Vercel dashboards. It sits above them. When you ask “when should I ship the blog post about the new auth system?”, HUBBLE shows you the deployment landed Tuesday, the PR merged Monday, and your content-drop campaign deadline is Friday. When you ask “is anything blocked?”, Mission Control shows it — derived from labels, ARES failures, and stale gates — without you checking 18 orgs individually. The Mars observatory aesthetic (so1.io design language) isn’t decoration — it reinforces the core metaphor: you’re looking through a telescope at your entire ecosystem from a single fixed point.

​
Signal

Built in a single session. 14 API routes. 7 views. Zero external chart dependencies. 87.3 kB shared JS. Authenticated via Airlock cross-subdomain cookies with 3-tier access. Deploys to hubble.devarno.cloud via Coolify. The pattern is replicable: any team running multiple orgs can fork the normalization layer and plug in their own data sources. The status derivation engine and alert rules are the real IP — they turn raw API data into actionable intelligence. Live at: hubble.devarno.cloud