Websites and hosting decision

own.page

A competent developer can build a useful, self-hosted link-in-bio replacement (pages, media uploads, custom domains, basic analytics) but reproducing own.page's polish, drag-and-drop editor, and full product UX/support is nontrivial; consider self-hosting the simpler open-source alternatives first.

Visit website
You pay

$6.65/mo

$80/yr

Read off the official pricing page.

You’d pay instead

$100one-off44 h to build

$60/mo6 h/mo upkeep

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

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 own.page alternatives, with the arithmetic →

What a replacement has to do

  • Create a page, add links/media/widgets, customize layout and theme, publish to an own.page subdomain or custom domain, and view simple analytics.

What it still won’t have

  • Polished drag-and-drop visual editor and curated templates
  • Priority support and SLA
  • Built-in advanced analytics and growth tooling
  • Branding, polish, and community/network benefits

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 11 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 minimal link-in-bio website builder using Next.js for the frontend, Node/Express (or Next API routes) and Supabase (Postgres) for the backend, and S3-compatible storage + Cloudflare/Vercel for hosting/CDN. In scope: user signup, create up to 5 pages per account, store page configs (links, text blocks, widgets), a simple template system, media upload (signed S3 uploads), publish to an own.page-style subdomain, custom domain verification + automated TLS, collect basic analytics (page views and link clicks) and a small dashboard, and embedding widgets (YouTube, Spotify) via iframes. Out of scope: full drag-and-drop visual canvas, multi-tenant billing, team accounts, advanced growth integrations. Include error handling, input validation, and automated tests for the API and key UI flows.
How we checked3 sources · 2/3 runs agreed · evidence score 63

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Evidence score63

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

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