4 ms·
Dev visibility for non-technical founders
If you're a founder who doesn't code, you probably rely on engineers to tell you what's shipping. That works until investors ask for updates, customers want a changelog, or you just need to know where things stand.
*What it does:*
Connect your repos. Ask questions:
- "What shipped last week?"
- "What's in progress?"
- "Who worked on what?"
Get plain English answers from your commit history.
*Automated reports:*
Schedule weekly or monthly summaries. Delivered to Slack or email. Forward to investors or your board.
*Other features:*
- Slack bot for team-wide access
- Contributor stats
*Security:*
Webhooks only. We store commit messages, PR titles, timestamps, and authors. We never access source code.
Stack:
- Token encryption: Fernet (HMAC-SHA256 + AES-128-CBC)
- Webhook verification: HMAC-SHA256
- 2FA support
Verify by checking your repo's webhook settings after connecting.
Free for 1 repo: https://gitmore.io
- jackfranklyn 9mo ago[flagged]
- akhnid 9mo agoGood point on commit message quality. We've addressed this partly by design, every event gets normalized into a standard schema: message, description, author, timestamp, files changed, PR state. The AI reasons over structured data, not just raw commit messages. PR descriptions especially help. Most devs write oneline commits but actually explain context in the PR body. We capture that. Still, teams with good commit hygiene get better output. No way around it. Appreciate the thoughtful take.