7 min readComparisons

Self-Hosted URL Shorteners Compared: YOURLS, Shlink, Kutt

Compare self-hosted URL shorteners from their own repos and docs: licence, stack, database and upkeep for YOURLS, Shlink, Kutt, Dub, Polr and Elido

Ana Kowalska
Marketing solutions engineering

If you want to run a URL shortener on your own server, five open-source projects are worth a look: YOURLS, Shlink, Kutt, Dub and Polr. YOURLS, Shlink and Kutt are MIT-licensed and easy to start. Dub is AGPLv3 with a commercial enterprise folder, and its self-hosting guide needs three outside accounts. Polr has been dormant since 2021. Elido isn't on the list of things you can self-host: its repository has no licence file, and we don't sell a self-hosted edition. The facts below come from each project's repository and docs, accessed 2026-10-25.

The Elido vs YOURLS comparison and the Bitly alternatives guide cover the hosted side. This post stays on the question "which one do I run, and what does it cost me to keep it alive?" If you came here hoping to deploy Elido itself, the k3s playbook explains exactly what that chart is and isn't.

What you operate when you self-host

A shortener looks small: a database, a redirect process and a dashboard. In production it splits into four jobs, and self-hosting means you own every one.

The redirect tier comes first. Every click on every short link lands here, so downtime breaks every link you've ever shipped; it has to be quick and it has to be up.

Click analytics is the second job. Recording and querying clicks is a different workload from storing links. Most lightweight projects keep both in one SQL database, which works until the click table gets large.

Third, the dashboard, where people create links, tag them and report on them. This is where open-source projects are closest to hosted products.

Last comes the custom-domain machinery: DNS checks, certificate issuance and renewal. One domain is easy. Fifty customer domains is a project.

Stacked diagram of the four surfaces a self-hosted shortener operator runs: the latency-critical redirect tier, the click analytics pipeline, the dashboard, and the custom-domain ACME machinery

Self-hosted URL shorteners side by side

The table lists what each project states about itself. Releases and activity come from the GitHub repositories on 2026-10-25.

ProjectLicenceStack and storageLatest release / last commit
YOURLSMITPHP scripts, SQL database1.10.6 (2026-08-30) / 2026-10-24
ShlinkMITPHP; SQLite, MySQL, MariaDB, PostgreSQL or SQL Serverv5.1.8 (2026-10-21) / 2026-10-24
KuttMITNode.js 20+; SQLite, Postgres or MySQL/MariaDB; optional Redisv3.2.6 (2026-07-05) / 2026-10-19
DubAGPLv3, enterprise folder under a commercial licenceNext.js app; Tinybird, Upstash and PlanetScale per the guideno tagged release / 2026-10-24
PolrGPL-2.0PHP, SQL database2.3.0b (2021-01-28) / 2023-09-17
ElidoNo licence file; not open sourceNot offered for self-hostingHosted only

Two things stand out. The three MIT projects are all active, and their default databases are cheap to run (SQLite for Shlink and Kutt). The only one with a dedicated analytics store is Dub, and it gets there by depending on three hosted vendors rather than on software you run.

Project by project

Each of these is a different bet, so the notes below say who it fits rather than who wins.

YOURLS

YOURLS calls itself "a set of PHP scripts" that lets you run your own shortener with stats and a plugin system. It has the biggest installed base of the group (about 12,300 GitHub stars) and a long plugin list. It fits one owner, one domain and modest traffic. A team with client domains or heavy reporting will hit its limits early, which the Elido vs YOURLS post linked above covers in detail. Outgrown it? Read YOURLS alternatives.

Shlink is a PHP app built to serve short URLs under your own domain. Its Docker image ships with SQLite, but the docs say plainly that production should use an external database, and list MySQL, MariaDB, PostgreSQL or Microsoft SQL Server as options. It's the most operations-friendly of the PHP projects and was the most recently released of the group (v5.1.8, 2026-10-21). The Elido vs Shlink comparison goes through its redirect rules and what a production install needs.

Kutt

Kutt needs Node.js 20 or newer. It defaults to SQLite and can use Postgres or MySQL/MariaDB, with Redis as an optional cache. The repo ships several Compose files for those combinations, which makes a first deployment quick. It suits teams that live in Node and want something small. Our Elido vs Kutt comparison weighs it against handing the job to a hosted service.

Dub

Dub is the most capable product in the list and the heaviest to run. The repository is AGPLv3 apart from an enterprise folder under a commercial licence, and the maintainers describe the model as open core. The self-hosting guide lists accounts with Tinybird, Upstash and PlanetScale as prerequisites. You're self-hosting the app, not the data stores. The AGPL also matters if you modify the code and offer it over a network, so have someone read it before you build a product on top. We cover the commercial comparison in Elido vs Dub and Dub alternatives.

Polr

Polr is a GPL-2.0 PHP project whose last release was 2.3.0b in January 2021. Forks exist, but for a new deployment there is no reason to pick it over Shlink or YOURLS. If you still run one, Elido vs Polr covers its maintenance status and a safe migration order.

Where Elido fits

This is the part we'd rather state exactly than let you infer. The Elido repository contains no licence file. That means Elido is not open source, and nobody outside the company has a licence to run or modify the code.

Any copy that says Apache 2.0 for Elido is wrong.

The repository does include a Helm chart and a self-host runbook. They are deployment tooling we use and keep. They aren't a published product: there is no self-hosted plan on our pricing page, no support terms and no public release channel. If your data must sit on your own infrastructure, ask us what's possible and treat the answer as a custom arrangement. The k3s playbook mentioned at the top goes through the chart and states which parts of a production setup it doesn't cover.

For teams that only need data kept in the EU, the hosted service already does that for its primary data. The EU residency guide lists which parts of the processing sit outside the EU, such as edge locations that see visitor IPs.

The costs that show up later

Start with click storage. One link with 100 clicks a day makes about 36,500 rows a year, which any database handles. A link with 100,000 clicks a day makes 36.5 million, and counting them by day over a month in the same database that serves redirects starts to hurt. Analytics systems usually split this workload off for exactly that reason. Dub avoids it by outsourcing to Tinybird. The others don't, so plan to export or archive.

Latency is the next bill. A single server answers from one place. Visitors on another continent add a couple of hundred milliseconds of network time to every redirect. Fixes exist (geo DNS, a CDN, one node per region), each with its own cache-invalidation problem when a destination changes. The edge vs DNS routing post walks through the trade-off.

Then certificates. One domain on a reverse proxy takes minutes. Issuing certificates for domains your customers add yourself needs an allow-list so strangers can't point arbitrary domains at you and burn your certificate rate limits.

How to choose

Decision tree of five questions on data sovereignty, click volume, custom-domain count, on-call maturity, and strategic importance, each branching toward self-host or a hosted vendor

Start from the constraint, not the feature list. If policy requires data on your own hardware, self-host, and pick Shlink or YOURLS for small internal use, Kutt if you run Node, or Dub if you can accept its outside services. If you need many regions, heavy analytics or many customer domains and have nobody on call, a hosted product costs less than the hours you'd spend. Default to hosted unless one of the hard constraints applies.

Whichever you choose, write down the backup and upgrade routine before the first link goes into a printed brochure.

A shortener that loses its database breaks every link it ever issued.

Frequently asked questions

What is the best self-hosted URL shortener?

For a small team that wants the least upkeep, Shlink or YOURLS. Both are MIT-licensed PHP apps that run on a single server. Kutt suits teams that already run Node.js. Dub gives the most polished product but needs three outside accounts (Tinybird, Upstash and PlanetScale) per its self-hosting guide. None of them replaces a hosted service once you need multi-region redirects.

Is Elido open source or self-hostable?

No to both, as far as we publish today. The Elido repository has no licence file, so no one outside Elido has a licence to run or modify the code, and the self-hosting chart is not sold or supported as a customer product. If you need data on your own infrastructure, write to us and we will tell you what is possible. Our hosted service keeps its primary data in the EU.

Which self-hosted shortener has the best analytics?

Dub, because its self-hosting guide puts click events in Tinybird, a dedicated analytics store. Shlink records per-visit data (location, referrer, device) in its main SQL database, which is fine at modest volume. YOURLS keeps basic click stats in MySQL. Past a few million clicks a month, a relational database holding both links and clicks becomes the bottleneck.

Is YOURLS still maintained?

Yes. The YOURLS repository shipped release 1.10.6 on 2026-08-30 and had commits as recently as 2026-10-24 (GitHub, accessed 2026-10-25). Polr is the one to avoid for new projects: its last release was 2.3.0b in January 2021 and its last commit to any branch was in September 2023.

Can I self-host a URL shortener with my own domain and HTTPS?

Yes, with all of them, but you wire it yourself. Point your domain at the server and put a reverse proxy or load balancer in front to terminate TLS. Shlink supports multiple domains in one install. Issuing certificates on demand for many customer domains is a separate piece of work that none of the lightweight options solve for you.

When does a hosted shortener beat self-hosting?

When you need redirects served from several regions, click analytics beyond a few million events a month, certificates for many customer domains, or you have no one on call. Self-hosting wins when policy forces data onto your own infrastructure or when links are a small internal utility.

Try Elido

Paste a URL, get a working short link

No signup. Link lives for 30 days. Sign up to keep it forever.

Free account required. The free plan includes 25 links in total. Already have an account? Log in

Try Elido

EU-hosted URL shortener with custom domains, deep analytics, and an open API. Free tier - no credit card.

Tags
self hosted url shortener
open source url shortener
yourls alternative
shlink vs kutt
dub self hosting
self host link shortener

Continue reading