Websites and hosting decision

Singlelink

Self-hosting the existing open-source Singlelink repo is the smallest useful replacement; a single technical user can deploy and maintain it in a day and avoid paying once hosted.

Visit website
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

$20one-off6 h to build

$0/mo3 h/mo upkeep

No published price to break even against.

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 Singlelink alternatives, with the arithmetic →

What a replacement has to do

  • Serve a small customizable link-profile site where the owner can add/edit links and publish to a custom domain.

What it still won’t have

  • Managed SaaS hosting (one-click signup and hosted account)
  • Commercial support and SLAs
  • Any proprietary hosted analytics or paid integrations the SaaS might add later
  • Automatic multi-tenant conveniences (billing, team management) provided by a hosted product

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Singlelink 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 self-hosted Singlelink instance using Docker Compose on a single VPS (Ubuntu 22.04) with PostgreSQL and Nginx as a reverse proxy. Stack: Node/Next.js (or provided app), Postgres, Docker Compose, Let's Encrypt certbot. In scope: clone https://github.com/singlelink-co/Singlelink, create .env from repo docs, build and run containers, configure Postgres backup, configure Nginx for a custom domain with TLS, enable admin/auth to add/edit links, and verify pages render and are SEO-friendly. Out of scope: redesigning the UI, implementing paid multi-tenant billing, or training ML models. Require robust error handling for DB connectivity and domain setup, basic automated integration tests for site rendering and link CRUD, and documentation steps for deployment and upgrades.
How we checked5 sources · 2/2 runs agreed · evidence score 99

How the score was reached

  • Self-host verdict base92
  • An open-source build was found+5
  • 5 cited sources+3
  • 2/2 assessment runs agreed+4
  • Evidence score99

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 2 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded