Games and entertainment decision

iWin

A storefront and launcher can be rebuilt. The licensed catalog, game packaging, entitlements, payments, weekly releases, and customer support are the product—and are substantially cheaper to buy than recreate.

Visit website
You pay

$14.99/mo

$180/yr

Read off the official pricing page.

You’d pay instead

$100one-off80 h to build

$50/mo10 h/mo upkeep

On cash alone, building overtakes the subscription at 4 seats.

The code exists. It is not what you are paying for.

This project is real, published, and does the core job — and this page still says keep paying. What the subscription buys is content licensing, secure game delivery and entitlements and installer compatibility, and none of that ships in a repository. Fork it anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All iWin alternatives, with the arithmetic →

What a replacement has to do

  • A searchable library for games you already own
  • Local launch and install-state tracking
  • Favorites and play history
  • Basic account entitlements

What it still won’t have

  • iWin's licensed game catalog
  • All Access membership rights
  • Managed installers and game updates
  • Publisher operations and customer support

What remains hard

  • Content licensing
  • Secure game delivery and entitlements
  • Installer compatibility
  • Catalog and publisher operations
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 4 seats.

Paid seatsseats

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 private Windows game library and launcher for games the user already owns.

Use C#, .NET, SQLite, and a native desktop UI.
Scan user-selected folders for installed games and store local metadata, cover art, executable paths, and play history.
Support search, filters, favorites, manual game entries, and launch arguments.
Keep all library data on the device and provide JSON export and import.
Allow cover art to be selected from local files; do not scrape or redistribute copyrighted assets.
Do not implement a commercial storefront, subscription, DRM, payments, publisher ingestion, or game downloads.
Add clear error handling for missing executables and moved folders.
Include tests for library import, path validation, and backup restore.
Document that users must own every game they add.
How we checkedno sources · evidence score 18