Creator and commerce decision
Mainan
A one-person developer can reproduce the core curated-site experience (listings, affiliate product pages, favorites, privacy analytics) in about a week and maintain it; you would lose the site's existing audience, brand, and any negotiated affiliate partnerships.
Visit website↗Built by Yuyu, who ships 11 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-off32 h to build
$0/mo3 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
- Visitors browse curated toy listings by category/age/topic, open product pages (affiliate links), add items to a favorite list, and discover guides and brand pages; site records privacy-friendly analytics.
What it still won’t have
- Existing site traffic and SEO history
- Established brand and trust (built audience)
- Any affiliate links, partner relationships, or existing merchant integrations already negotiated
- Polish of the current curated selection and hand-tuned content
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Mainan 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 static curated ecommerce content site using Next.js (app router) + Tailwind CSS, Markdown for content, and Vercel for hosting. Core features in scope: CMS-compatible content model for toys (title, images, categories, topics, age ranges, brand, affiliate URL, description), category/topic/age listing pages with server-side static generation, product detail pages that surface affiliate links, client-side Favorites persisted in localStorage (and optional simple JSON API to export/import favorites), privacy-friendly analytics integration (e.g., Plausible/Seline-compatible), sitemap and basic SEO metadata, and a build/deploy pipeline on Vercel. Out of scope: payment processing, multi-user accounts, recommendation engine, advanced search indexing. Include error handling for missing affiliate links and image load failures, unit tests for listing and favorites logic, and end-to-end test for build and a sample deploy. Document deployment and content-editing workflow.
How we checked
How the score was reached
- Build verdict base78
- 2 cited sources+1
- 3/3 assessment runs agreed+4
- Evidence score83
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 productMainan
- official productFooter notes
Integrity checks
What held up, and what did not.
