Live engineering signal — in one place.
Pulse is the live-pulse backend for FiveD Studio. It listens to GitHub, normalizes every push, PR, review, and release the team makes, and broadcasts the signal to this site as it happens.
What it ingests
Two streams: webhooks from the GitHub App installed on the FiveD org, and a 60s polling worker that pulls each member's public events from the rest of GitHub. Whether you push to a studio repo or your own side project, Pulse sees it.
How it stays live
Every accepted event hits a Redis stream which fans out to every browser tab subscribed to the SSE endpoint. Open /live, push a commit, watch it appear within ~1 second.
What it doesn't do
No comparison features, no leaderboards, no AI judgment. The data is descriptive, not evaluative. Members own their visibility — paused, weekend-hidden, latenight-hidden, private-repo-hidden — toggleable per person.
Open by default
Backend is open source at fived-studio/pulse. Same for this site at fived-studio/fived-studio.github.io. The whole pipeline, top to bottom.
Built with
- Bun + Hono on Google Cloud Run
- Postgres 16 (Cloud SQL) for events, repos, members, daily rollups
- Redis 7 (Memorystore) as a fan-out stream + dedup buffer
- GitHub App for HMAC-verified webhooks; installation tokens for the polling worker
- Next.js 15 (static export) on GitHub Pages — every page pre-rendered, with a thin client layer that re-fetches on mount so nothing goes stale
- Cloud Build trigger on push-to-main → image → Artifact Registry → Cloud Run revision, ~2min cycle