Social media decision
LIZAONAIR
A single developer can build a basic multi-platform giveaway picker, but reproducing a reliable, hosted, multi-platform commercial product (resilient scrapers, auth handling, scale and anti-abuse) is operationally heavy and not realistic as a drop-in replacement.
Visit website↗Built by 350D, who ships 4 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-off60 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
- User pastes a social post URL → load and normalize comments/entries → apply filters/dedupe → select random winner(s) → display and export results
What it still won’t have
- Robustness to platform API/HTML changes and content-access blocking
- Scale, uptime guarantees, and anti-abuse/fraud detection used by the paid product
- Premium convenience features (one-click integrations, hosted reliability, branding/legal assurances)
- Trust/verification from a third-party provider (time-stamped hosted draws, official receipts)
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
LIZAONAIR 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 giveaway comment-picker web app using Node.js (TypeScript), Puppeteer for scraping/HTML API fallbacks, PostgreSQL for storing draws, and a React + Vite frontend. Core features in scope: paste a public Instagram, YouTube, TikTok, or VK post URL and fetch all comments (handle pagination), normalize and dedupe commenters, support simple filter rules (exclude duplicates, require mention), run a seeded random winner selection and persist the draw (timestamp, seed, selected rows), allow CSV export and render a reproducible results page. Out of scope: enterprise multi-account management, real-money payments, advanced anti-fraud analytics. Require: error handling for blocked content and rate limits, logging, unit tests for comment normalization and winner selection, and an integration test that simulates a scrape using saved HTML fixtures.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
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 →Integrity checks
What held up, and what did not.
