Developer tools decision
GitPulse
A capable engineer can reproduce the core profile and badge features (and there are open-source portfolio projects to borrow from), but the hosted product’s private-repo verification, scoring polish, and one-click UX are nontrivial and make a full replacement only partially realistic.
Visit website↗Built by Kevin Baur, who ships 3 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off42 h to build
$20/mo6 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Periodically fetch GitHub metadata (commits, PRs, issues) for an account or selected repos → deduplicate and aggregate timestamps/counts → compute activity metrics and score → render a shareable profile and embeddable badge → allow OAuth + GitHub App installation for private-repo metadata (optional)
What it still won’t have
- One-click verified/paid workflow and product polish (UX, badges, marketing)
- The vendor’s exact scoring algorithm and reputation/trust
- Any proprietary operational security review and legal assurances
- Potential convenience of a one-time purchase license and hosted backups
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
GitPulse does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal GitPulse replacement using Next.js for the frontend, Node.js + Express for the backend, and Postgres for aggregate storage; host frontend on Vercel and backend on Render. Core features in scope: GitHub OAuth + optional GitHub App install (read-only), scheduled fetch of repo metadata (commits timestamps, PR/issue counts) via GitHub GraphQL/REST, aggregation and scoring of activity, per-user profile pages with timeline graphs, embeddable badge/iframe and privacy controls (hide private repo names, revoke tokens). Out of scope: reading file contents, diffs, commit messages, or implementing a marketplace/leaderboard beyond single-user profile. Include encrypted token storage, TLS, background job retries, logging (no secrets), unit and integration tests, and CI deploy scripts.
How we checked
How the score was reached
- Partly verdict base52
- 2 cited sources+1
- Evidence score53
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 2
Every page the run actually retrieved.
- official productGitPulse | The Living Developer Profile
- official docsSecurity & Data Model | GitPulse
Integrity checks
What held up, and what did not.
