Websites and hosting decision
Liinks
A single competent developer can build and run a useful Liinks replacement in about a week using existing frameworks and the supplied open-source onelink as prior art; you lose polished templates, integrations, and commercial support.
Visit website↗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 Liinks alternatives, with the arithmetic →
What a replacement has to do
- Edit a small public profile of links and share a single URL that redirects to that profile.
What it still won’t have
- Polished multi-template themes and drag-and-drop editor
- Built-in payments or creator-commerce integrations
- Large-scale analytics dashboards and export features
- Native mobile apps, team/collaboration admin features
- Commercial support, SLAs, and single-tenant enterprise options
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Liinks 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
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
Build a minimal link-in-bio service using Next.js (React) for frontend, a Node/Express or Next API route backend, and PostgreSQL (hosted on Supabase) for storage; deploy on Vercel or Netlify and serve public pages from the CDN. In scope: public profile pages with configurable title, avatar, and an ordered list of links with icons; an authenticated admin UI to CRUD links and reorder them; a backend API with simple JWT/session auth storing profiles and links; lightweight click analytics (per-link counters with date) and an admin view for recent clicks; custom domain support via host DNS instructions. Out of scope: multi-tenant billing, team collaboration roles, complex theme marketplace, mobile native apps. Include input validation, error handling, basic unit/integration tests for API routes, and a README with deploy and DNS setup steps.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 2 cited sources+1
- 3/3 assessment runs agreed+4
- Evidence score88
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 · 2
Every page the run actually retrieved.
- official productLiinks | The Link in Bio Tool for Creators & Businesses
- open sourcefayazara/onelink
Integrity checks
What held up, and what did not.
