Games and entertainment decision

Gameclick

A small technical user can build and maintain a browsable site that embeds existing browser games; the product has no visible durable moats and the core functionality is straightforward to reproduce.

Visit website

Built by 两万焦, who ships 8 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$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

  • Browse game list → open game page → load game in-browser (iframe/player) → play as guest

What it still won’t have

  • Any proprietary curation or relationships that feed the existing library
  • ShipAny-specific boilerplate and bundled features shown on the pricing page (boilerplates, credits system)
  • Any paid support or built-in SaaS features referenced on the pricing page

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Gameclick 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

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a minimal self-hosted browser-game library using Next.js + React for the frontend, Postgres for metadata, and Vercel (or Cloudflare Pages) for hosting. Core features in scope: (1) REST API + Postgres schema for games (title, slug, tags, embed_url, thumbnail, width/height), (2) Next.js front page with tag/category filters and pagination, (3) game detail page that embeds the game's URL in a secure iframe with preload/spinner and mobile-friendly sizing, (4) simple admin UI to add/edit/delete game entries and upload thumbnails (store in S3-compatible bucket), (5) sitemap and basic SEO, (6) CI deployment configuration and Dockerfile for local dev. Out of scope: rehosting game binaries, DRM/licensing negotiation, multiplayer backend. Require: input validation, sanitized iframe embedding, error handling for missing games, unit tests for API routes, and end-to-end tests for browse and play flows.
How we checked2 sources · 2/3 runs agreed · evidence score 79

How the score was reached

  • Build verdict base78
  • 2 cited sources+1
  • Evidence score79

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.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded