Hey Product Hunt 👋 I'm Aidan, one of the developers on sparQ. We kept noticing the same waste on our own team. You'd type out a status update ("worked on the auth refactor, no blockers"), then open the PR you'd just pushed and see you'd already written all of it in the commits and the description. The status was real work being retyped by hand That turned out to be one symptom of three problems we kept hitting on our own team: 1. The plan is not the work. Your PM board says what's planned, but not who's actually blocked, who's heads-down, or what shipped today. So in Pulse, status is derived straight from your GitHub activity, plus presence for availability, focus mode, and PTO. 2. Context is scattered everywhere. Decisions and updates get buried across Slack, GitHub, Drive, and AI chats. Pulse gives them a home so they stay put instead of vanishing into a thread. 3. Nobody wants to open another tool. If checking the PM tool means leaving GitHub or Slack, people just don't. So Pulse asks for almost nothing by hand: brief standups and blockers, inline issue refs like #1234, and optional Slack/Teams digests. The rest writes itself from the work you're already doing. It's fully open source (AGPL v3) and self-hostable, so `docker compose up` gets you the whole thing locally. Repo: github.com/gosparq/sparq Would love feedback on whether these three match the pain your team feels, or if we're missing one. Happy to answer anything!

sparQ

The first open-source DevEx suite for GitHub-native teams

The first open-source DevEx suite for GitHub-native teams