Every link-in-bio tool does the same thing: one page, a list of links, some styling, and click statistics. The comparison articles rank them on features that barely differ. The decision that actually matters is whether that page lives on your domain or someone else’s.
Because a link-in-bio page is genuinely one of the simplest things on the web — a heading, an image, a list of links — and the hosted tools are charging a subscription for something you can own outright. That is not an argument against them, but it should be a conscious trade rather than a default.
Table of contents
- What these tools actually provide
- What you give up by renting
- Hosting it yourself is genuinely small
- Which to choose
- Setting up your own, end to end
- How this fits the rest of the stack
- FAQ
What these tools actually provide
Stripped of the marketing, the feature set across the whole category is narrow.
- A single page with your avatar, a name, a short bio and a stack of buttons.
- Styling — themes, colours, fonts, a background.
- Analytics — clicks per link, sometimes referrer and rough geography.
- A subdomain on their platform, with your own domain usually available on a paid tier.
- Extras on higher tiers — email capture, embedded video or music, scheduling, payment or tip buttons, sometimes a small store.
The extras are where the tiers differentiate, and where a self-hosted page genuinely does less without additional work. Email capture and payments are real functionality, not styling.
But the core — a page with links and click tracking — is not a hard technical problem. It is one HTML file. The value the hosted tools sell is that you do not have to think about it, and for many people that is worth paying for. The question is what you are giving up in exchange.
What you give up by renting
Four things, in order of how much they end up mattering.
- The URL. Your link-in-bio address is on their domain unless you pay for the custom-domain tier. That URL is on every social profile, every business card, every video description. Changing it later means updating all of them, and some you will never find.
- The dependency. Your entire link infrastructure sits behind one third party’s uptime, terms and business model. The category has seen tools shut down, get acquired, or change their free tier substantially. When that happens, every link you have distributed points at their decision.
- The data. Click statistics live in their dashboard. Export varies from limited to nonexistent, and it is rarely in a form you can join with anything else.
- The look. You get their themes. Fine for most people, and a real constraint if the page is meant to represent a brand with its own identity.
The first one is the important one. A page you can rebuild in an afternoon is not the asset — the URL that everyone already has is. If that URL is on a domain you own, you can change everything behind it whenever you like and nothing breaks.
Hosting it yourself is genuinely small
Worth being concrete about the scale of the task, because people assume it is larger than it is.
A link-in-bio page is one HTML file with some CSS. No database, no server-side code, no build step required if you do not want one. It is the smallest possible website.
<!-- The entire structure, roughly -->
<main>
<img src="/avatar.jpg" alt="" width="96" height="96">
<h1>Your Name</h1>
<p>One line about what you do.</p>
<nav>
<a href="https://...">Newsletter</a>
<a href="https://...">Latest video</a>
<a href="https://...">Shop</a>
</nav>
</main>
Style it, put it on a domain you own, done. Because it is static it loads almost instantly, costs essentially nothing to serve, and cannot break in the ways a database-backed page can.
The two things you have to solve yourself:
- Analytics. A lightweight privacy-respecting analytics script, or simply reading which outbound links get clicked via your existing analytics. This is a small amount of setup, not an ongoing burden.
- Editing. Updating a link means editing a file. Fine if you are comfortable with that; a Git-backed editor or a small CMS closes the gap if you are not, and there are self-hostable link-in-bio projects that provide an admin panel if you want one.
There are also open-source link-in-bio applications you can run yourself, which give you the dashboard and the analytics with the ownership. That is a middle path — more capable than a static file, and now a service you operate rather than a file you serve.
Which to choose
The honest split, rather than a recommendation to self-host everything.
Use a hosted tool if you want it working in five minutes, you value the extras — email capture, payments, scheduling — and you are content to pay a subscription. This is the right answer for a lot of creators, and there is no shame in it. Do pay for the custom-domain tier though, because that removes the worst of the lock-in for a small amount of money.
Host it yourself if you already have a domain, the page is a brand asset rather than a convenience, or the idea of your primary link living on someone else’s subdomain bothers you. The running cost is close to nothing and the page will outlive several generations of link-in-bio startups.
Consider whether you need one at all. If you have a website, a /links page on it does the same job, on the domain you already own, with the analytics you already have. A surprising number of people pay a subscription for a page that could be a route on a site they already run.
Whichever way, use your own domain. That single decision makes every other part of this reversible.
Setting up your own, end to end
- Pick a hostname. A subdomain like
links.yourdomain.com, or a path on your existing site. A path is simpler and shares the domain’s existing authority. - Write the page. One HTML file. Keep the avatar small and give every image explicit dimensions.
- Add analytics, or tag the outbound links so your existing analytics records them.
- Deploy it as a static site, which is the cheapest and fastest way to serve one file.
- Point the domain, and let the certificate be issued automatically.
- Update your profiles to the new URL — and this is the last time you will need to do that, which is the entire point.
One practical detail: keep the page genuinely light. Link-in-bio pages are opened almost exclusively from mobile apps on mobile data, often on a poor connection. A page carrying three web fonts and an animation library defeats its own purpose. This should be a few kilobytes.
How this fits the rest of the stack
A link page is the smallest possible website — one file, no database, no runtime — which makes it close to free to serve on a domain you own. The RunxBuild hosting calculator shows what that costs against anything heavier you might add later, like email capture that needs somewhere to store submissions. RunxBuild builds static sites from a repository with the custom domain and certificate handled at deploy and 120GB of bandwidth included, and runs a service beside it if the page ever needs a backend.
Useful related references:
- WordPress Alternatives, Sorted by What You Are Actually Escaping
- WooCommerce Alternatives: What You Are Actually Trying to Escape
- Squarespace Alternatives: What You Are Actually Trading Away
- Services on RunxBuild
FAQ
What is the best Linktree alternative?
They are all closely comparable on the core feature — a page with links and click tracking — so the differentiator is the extras like email capture and payments, and whether a custom domain is included. The more consequential choice is whether to rent the page at all or host one on your own domain.
Can I host my own link-in-bio page?
Yes, and it is one of the simplest possible websites — a single HTML file with an avatar, a name and a list of links. No database and no server-side code. You solve analytics and editing yourself, and there are open-source link-in-bio applications with admin panels if you want the dashboard too.
Why does a custom domain matter for a link-in-bio page?
Because the URL is what you distribute — it ends up on every social profile, business card and video description. If it is on someone else’s domain, changing tools means updating all of those, and you will never find them all. On your own domain you can change everything behind it and nothing breaks.
Do I need a link-in-bio tool if I already have a website?
Often not. A /links page on your existing site does the same job, on a domain you already own, with analytics you already have. A number of people pay a subscription for a page that could be a route on a site they already run.
How light should a link-in-bio page be?
A few kilobytes. These pages are opened almost exclusively from mobile apps on mobile data, frequently on a poor connection. A page loading three web fonts and an animation library defeats the purpose of being a fast jumping-off point.