Websites and hosting decision

Selected Site

For a single technical user, building and running a modest Framer-template directory is realistic and cheaper than paying for a hosted directory; nothing on the supplied page indicates an unreproduceable moat.

Visit website

Built by Solt Wagner, who ships 7 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

$50one-off22 h to build

$20/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

  • Collect Framer template listings, allow submissions, show ranked/filterable listings, and link through to template marketplaces.

What it still won’t have

  • existing site traffic, brand recognition and any incumbent SEO/authority
  • community or marketplace reach associated with the live product
  • any proprietary curation, editorial content, or partnerships the product has

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Selected Site 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 Framer-template directory using Node.js (Express), Postgres, and a React + Tailwind frontend. Core features in scope: (1) a crawler script to fetch and normalize Framer template metadata into PostgreSQL, (2) a public listing page with pagination, search, and tag filters, (3) a public submission form with CAPTCHA and an admin moderation panel to approve listings, (4) a simple ranking score computed by a scheduled job (cron) and exposed on the listing, (5) deployable Docker configuration and CI pipeline. Out of scope: payment processing, user accounts beyond an admin user, and an integrated marketplace checkout. Include error handling for network and DB failures, input validation, and unit/integration tests for API endpoints and the crawler.
How we checked1 sources · 2/3 runs agreed · evidence score 78

How the score was reached

  • Build verdict base78
  • Evidence score78

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 · 1

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