Websites and hosting decision

Linkero

A competent technical user can build and maintain a smaller self-hosted replacement; Linkero's value is product polish, hosted convenience and integrations rather than proprietary data or network effects.

Visit website
You pay

$10/mo

$120/yr

Read off the official pricing page.

You’d pay instead

$100one-off120 h to build

$0/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 1 seat.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Linkero alternatives, with the arithmetic →

What a replacement has to do

  • User creates/edit a single customizable public page with content blocks, configures domain and analytics, and shares the page URL.

What it still won’t have

  • Polish of Linkero's UI and theme gallery
  • Hosted team and billing UX (account management, upgrades)
  • Built-in discovery / Linkero hosted directory
  • Customer support and SLA
  • Some built-in integrations and analytics dashboards

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 1 seat.

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 minimal self-hosted link-in-bio website using Next.js (React) for the frontend, PostgreSQL for storage, and a small Node/Express API. Core features in scope: user signup/login, create/edit up to N pages composed of reusable blocks (text, button, image, video, form), theme support (CSS variables), render public page URLs, custom domain verification (DNS TXT check) and automatic HTTPS via Let's Encrypt, basic analytics (page views and simple event tracking), form storage with CSV export and webhook delivery, and a small admin UI for account settings and page listing. Explicitly out of scope: multi-tenant billing, marketplace/discovery, team multi-seat billing beyond a single-admin account. Include input validation, error handling, unit tests for API endpoints, and deployment instructions (Docker + docker-compose and Vercel notes).
How we checked4 sources · 3/3 runs agreed · evidence score 67

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score67

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded