Uncategorised decision
ActivityProof
A capable technical user can implement the core badge service (GitHub integration, status computation, SVG endpoint, and a tiny dashboard) in about one week and run it for a small monthly hosting cost; ActivityProof's value is product polish and hosted convenience rather than unreproducible data or network effects.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off34 h to build
$30/mo3 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All ActivityProof alternatives, with the arithmetic →
What a replacement has to do
- Link a GitHub repo, compute recent commit activity to derive a status (Active / Quiet / Live since), render a public SVG badge URL that updates from that computed status, provide a dashboard preview and a publish toggle.
What it still won’t have
- Polished commercial dashboard polish, analytics, and UX polish
- Built-in payment handling, receipts and refund workflows (unless implemented)
- Hosted branding, support, and marketing reach
- Legal, billing, and consumer-facing guarantees (refund policy, support SLAs)
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
ActivityProof 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 self-hosted ActivityProof clone using Node.js (Express), PostgreSQL, and a single server host (Render or DigitalOcean). Core features in scope: GitHub OAuth/App installation, webhook receiver (and fallback periodic polling), commit-activity aggregation into statuses (Active/Quiet/Live since), a public GET /badge/:slug returning an SVG worker-rendered badge, a minimal authenticated dashboard to create projects, preview SVG before publishing, and a publish/unpublish toggle that sets the public slug. Out of scope: hosted payment/receipt/refund flows, multi-tenant billing, advanced theming gallery, CI/CD automation. Include error handling for webhook failures, GitHub API rate limits, and malformed requests; write unit tests for status computation and integration tests for the SVG endpoint; provide Dockerfile, simple deployment docs, and a small migration script for the DB.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score93
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 · 4
Every page the run actually retrieved.
- official pricingActivityProof homepage and pricing
- official productActivityProof homepage feature claims
- open sourcebadges/shields
- open sourcecstate/cstate
Integrity checks
What held up, and what did not.
