Links became infrastructure.
Most shorteners didn’t notice.
So we built the part that was missing: a routing layer, run with the same engineering discipline as the rest of your stack.
A link is a decision. Most tools treat it like a memo.
Somewhere in the last decade, links stopped being pointers and became infrastructure. They get scanned off posters, queried by apps that expect JSON, split by campaign, pinned to brand domains. A link is asked a question — where, on what device, in which language — and something has to answer.
Shorteners kept shipping 2009: one slug, one destination, a counter. The answering part — the routing — never got built. That gap is the company.
rii.link is a routing layer, not a shortener with features.
The care that routes your links drew this page.
Every hairline here sits on a 72px lattice, and the layout system ships with its own drawing layer — append ?grid to any URL on this site to see it. We QA alignment against it before every release.
We didn’t add EU compliance.
We started here.
VISITOR IPS ANONYMISED BEFORE STORAGEWe do not sell click data. Not aggregated, not “anonymized”, not ever.
That isn’t a promise we keep — it’s a business we’re not in. There is no pipeline to turn off.
The architecture that enforces it → /securityFour rules, applied daily.
Written down after the fact — these are the patterns we kept catching ourselves following.
Route, don’t redirect.
A redirect is a hop; a route is a decision. Geo, device, time, language — evaluated on every request, answered from memory.
The default is honest.
Roadmap states say roadmap. In-progress says in progress. If a figure is synthetic, it’s labeled synthetic — on this site too.
One source of truth.
Every change is written once to the database and synced to the routing layer on save — the dashboard, the API and the wire agree.
Leaving is a button.
Export every link and the click history from Settings → Export, then delete a link, or the whole workspace from its settings — links, domains and QR codes go with it.
Built in Berlin.
We’d rather ship than staff up. No growth team, no sales floor — the product is the pitch, and this page is the deck.
routing · dashboard · abuse desk · support — same people answer all fourNo open roles right now — but say hi via /contact.Build on a routing layer you can actually read.
Free tier, EU-first — visitor IPs anonymised before storage. Read the architecture before you trust it — we’d prefer you did.
Read the security architecture →