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.
FRANKFURT AM MAIN · 50.11° N, 8.68° EWe 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 at the edge, answered in 11 ms.
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.
The dashboard, the API and the wire all read the same record. Nothing is a cached copy that can drift.
Your data leaves cleanly.
Everything exports as CSV or JSON the day you ask. Deletion means deleted — not flagged, not archived.
Small on purpose.
A handful of engineers in Frankfurt who’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-resident from the first click. Read the architecture before you trust it — we’d prefer you did.
Read the security architecture →