News for hackers. Stuff that matters.

Show HN: Building dev visibility for non-technical founders and stakeholders

Gitmore (https://gitmore.io) – plain English access to your Git activity.

If you're a founder, PM, or exec 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.

*The problem:*

Your engineers already document their work. Every commit, every PR. But that information lives in GitHub – a UI built for developers, not stakeholders.

*What Gitmore does:*

Connect your repos. Ask questions like you're talking to a teammate: - "What shipped last week?" - "Who's working on the mobile app?" - "What's blocking the release?"

Plain English in, plain English out.

*Slack integration:*

Connect the bot to your workspace. Ask questions directly from Slack – no need to open another dashboard. Your whole team gets access without needing GitHub logins.

*Automated reports:*

Schedule weekly or monthly summaries to Slack or email: - Features shipped - Bugs fixed - Who contributed

Forward to investors. Share with your board.

*How it works:*

Webhooks only. Git platforms push metadata to us – commit messages, PR descriptions, authors, timestamps.

Every event normalized into a structured schema. The AI queries structure, not raw text.

*Who it's for:*

- Non-technical founders - PMs writing changelogs - Execs who need visibility - Anyone outside engineering who needs to know what's shipping

*Security:*

Metadata only. We never clone repos or access source code.

- Encrypted tokens (Fernet) - Webhook signature verification - 2FA support

GitHub, GitLab, Bitbucket – one dashboard.

Free for 1 repo: https://gitmore.io

Are there non-technical people on your team who struggle to get dev visibility?

( no comments | on HN )

There are no comments yet.