Social media decision
JudgeMyDecision.com
A one-person technical build is realistic — the site is a straightforward social/entertainment feed with voting and comments, no evident proprietary data or infrastructure moats, so self-hosting a minimal replacement is practical.
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-off39 h to build
$0/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 JudgeMyDecision.com alternatives, with the arithmetic →
What a replacement has to do
- User submits a decision with two options -> community 'judges' or votes -> site aggregates a verdict/score -> displays public courtroom feed with verdicts and short judge comments
What it still won’t have
- Existing user base and organic traffic
- Brand recognition and social reach
- Any community moderation processes and historical content curation
- Polish from iterative UX and A/B testing the live site
- Creator/owner credibility and trust earned over time
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
JudgeMyDecision.com 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 self-hosted 'decision courtroom' web app using React for the frontend, Node.js + Express for the API, and PostgreSQL for storage. In scope: (1) a decision submission form (title, description, Option A/B, optional metadata like gender/family vibe), (2) backend endpoints to create/read decisions, record votes and short judge comments, and compute a numeric verdict score, (3) public feed with pagination and per-decision pages showing comments and score, (4) anonymous voting and simple rate-limiting (IP + cookie), (5) basic moderation endpoints to flag/hide decisions. Out of scope: analytics dashboards, paid user accounts, search indexing, recommendation algorithms, and advanced trust/anti-abuse systems. Require proper validation, error handling, unit tests for API routes, and end-to-end tests for the submission and voting flows. Provide Dockerfiles for the app and Postgres and a README with deployment steps to a single VPS or platform-as-a-service (Vercel/Heroku).
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score90
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 · 3
Every page the run actually retrieved.
- official productJudgeMyDecision.com — official product page
- open sourcesurvey-library
- open sourceLimeSurvey
Integrity checks
What held up, and what did not.
