SourceBee
GitHub collaboration app for engineering organizations - org-wide visibility for ICs and leaders, with AI analysis built in
Work together...better. SourceBee is a GitHub collaboration app for engineering orgs: install it against your GitHub org and get a real-time, org-wide view of how work is actually moving - useful for day-to-day work, daily huddles, or quarterly reviews - plus AI analysis of your team's metrics and an MCP server for wiring it into whatever agent tooling you already use. Currently in closed beta with a small batch of invited orgs.
- Zero-setup GitHub App install - connects to an existing GitHub org in minutes with no config files or new workflows required, works immediately and is customizable later
- AI analysis of org-wide engineering metrics included out of the box, plus an MCP server for optional access from any agent tooling
- Org-wide real-time view built for both ICs (day-to-day work) and leaders (statistical trends over time) from the same underlying data - no separate tooling per audience
- Reads only repo/PR/commit metadata via the GitHub App - no write access to code, no file contents ever touched, and all analysis is team/repo-level rather than tracking individual developers
- Self-distributed Firefox extension with a signed XPI and an auto-update feed for pre-release (dev/beta/rc) channels, independent of the Mozilla Add-ons review queue
- Turnstile-protected early-access request flow for closed-beta signups
Multi-service platform split across four repos: buzzcatcher (Go API backend) on DigitalOcean App Platform with a managed Postgres cluster, deployed by pushing a Docker image to GHCR and explicitly triggering a new deployment rather than relying on git-integration auto-deploy; sourcebee-app, housebee, and pollinator each as their own direct-upload Cloudflare Pages project (wrangler pages deploy from each app's own CI), kept separate specifically because a direct-upload deploy replaces a project's entire file tree and would otherwise clobber a shared project.
All shared/rarely-changing infrastructure - DNS, DO app specs, Pages project shells, Cloudflare zone settings - lives in one central repo (wagglebee) managed with OpenTofu, with dev and prod as fully separate applies: separate state files (in R2), separate variables, separate CI environments, so a dev-scoped CI job has zero access to prod secrets and vice versa.
Third-party integrations wired through the backend: GitHub App (webhooks + OSS token) for repo/PR/commit data, Clerk for auth, Paddle for billing (sandbox in dev), and the Anthropic API for the AI analysis and MCP features - each surfaced as scoped secrets per environment rather than shared across dev/prod.
Per-hostname Cloudflare Web Analytics (manually embedded snippet per app, not zone-wide auto-install) so each app's traffic is measured independently instead of blending into one zone total.