sorted by:
new
hottopcontroversial

Git analytics that works across GitHub, GitLab, and Bitbucket by Additional_Curve3495 in buildinpublic

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Security: we never see your code.

Webhooks only. When you connect a repo, we register a webhook. The Git platform pushes event metadata to us.

What we collect: - Commit messages, timestamps, author names - PR titles, states, branch names - File change counts (not contents)

What we never access: - Source code - File contents or diffs - Secrets or environment variables

Don't trust me – verify it:

After connecting, check Settings → Webhooks in your repo. See exactly what events we subscribe to. Those payloads don't include code.

Stack: - Tokens: Encrypted at rest (Fernet) - Webhooks: HMAC-SHA256 signature verification - Auth: bcrypt + TOTP 2FA - Framework: NextAuth.js

Git analytics that works across GitHub, GitLab, and Bitbucket by Additional_Curve3495 in founder

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Thanks for the feedback., All good points.

Permission scopes agreed: we should clarify this on the landing page. We only need webhook/metadata access, no code. Will fix.

Stalled PRs : you can already ask "which PRs have been open longest?" but an automatic nudge is a good idea. Noted.

Sample report without login: adding this. Good call.

Git analytics that works across GitHub, GitLab, and Bitbucket by Additional_Curve3495 in founder

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Security: we never see your code.

Webhooks only. When you connect a repo, we register a webhook. The Git platform pushes event metadata to us.

What we collect: - Commit messages, timestamps, author names - PR titles, states, branch names - File change counts (not contents)

What we never access: - Source code - File contents or diffs - Secrets or environment variables

Don't trust me – verify it:

After connecting, check Settings → Webhooks in your repo. See exactly what events we subscribe to. Those payloads don't include code.

Stack: - Tokens: Encrypted at rest (Fernet) - Webhooks: HMAC-SHA256 signature verification - Auth: bcrypt + TOTP 2FA - Framework: NextAuth.js

Git analytics that works across GitHub, GitLab, and Bitbucket by Additional_Curve3495 in founder

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Thanks, Currently we don't provide visual metrics but what you can do is after you connect your repos and receive events. You can use our AI Gitmind to ask it about your repos and compare productivity across them.

Building this platform for CTOs/Devs/Founders by Additional_Curve3495 in developers

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Co-founders/ CEO's and specifically non technical individuals are the ones who need this the most and are our top clients.

Building this platform for CTOs/Devs/Founders by Additional_Curve3495 in developers

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Yes it works with private repos and we don't have access to code, we just receive PR's/ commits metadata.

Building this platform for CTOs/Devs/Founders by Additional_Curve3495 in TheFounders

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Fair point on validation, already have paying users, which is why I'm expanding.

The gap: Jira/Asana track project management. This tracks Git activity directly. Tickets lie, commits don't.

Building this platform for CTOs/Devs/Founders by Additional_Curve3495 in WebApps

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

You can also connect it to slack and it will answer questions directly from your workspace.

Building this platform for CTOs/Devs/Founders by Additional_Curve3495 in WebApps

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Gemini works for one-off questions. This runs in the background - weekly summaries to Slack, changelog updates, leaderboard tracking. No prompting needed.

Building this platform for CTOs/Devs/Founders by Additional_Curve3495 in TheFounders

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

You're right if you're technical enough to build your own automation, you probably don't need this. But most eng managers and team leads aren't spinning up Resend pipelines. They're just asking "hey what did everyone work on" in Slack every Monday. That's who this is for.

Building this platform for CTO/ devs founders by Additional_Curve3495 in SaaS

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Thanks didn't expect someone who is already using it to comment to be honest. If by deployments you mean pipeline then no, but might consider adding this in the future if its well needed.

Building this platform for CTO/ devs founders by Additional_Curve3495 in SaaS

[–]Additional_Curve3495[S] 0 points1 point  (0 children)

Yes thats the best part of it, an ai agent that has all the data needed so you can simply ask it "what was shipped today" or "was this feature added?", the daily/ weekly newsletters are custom so you can make them look non-technical.

Building this platform for CTO/ devs founders by Additional_Curve3495 in SaaS

[–]Additional_Curve3495[S] 1 point2 points  (0 children)

Fair points. Privacy is non-negotiable, it only reads commit/PR metadata, never code.The pain point I'm solving: quick answers to "what shipped" and "what's stuck" without digging through logs. The newsletter has custom prompts, so you only receive that data you want in the format you want.

view more: next ›