URLs are surprisingly temporary things. Domains change, websites get reorganized, projects get renamed, and /final-v2-really-final/ eventually stops being final.
A rslvr.link address stays put while what happens behind it is free to evolve. Redirect somewhere, show information, group resources, control access, or create an experience with its own rules and lifecycle.
It’s useful for QR codes, printed material, documentation, games, physical spaces, temporary experiences, and anything else where changing what happens behind a link shouldn’t require changing the link itself.
Giving something a permanent address turned out to be the simple part. Once the address stays put, the more interesting question is what should happen when somebody uses it.
A RSLVR identifier can resolve directly, expose resources, apply rules, or become the entry point to a temporary experience.
Print it, bookmark it, embed it, or put it behind a QR code. The identifier stays the same while what happens behind it can change.
Sometimes that means redirecting to a different URL. Sometimes it means something else entirely.
A destination doesn’t have to be a single URL. URLs, notes, locations, challenges and other reusable resources can be assembled into a Scenario.
Change the composition without changing the address people already have.
Not every link needs to work for everyone, everywhere, forever.
Time, location, credentials, challenges and other policies can decide whether something is available — and what happens when it isn’t.
RSLVR becomes the layer between the request and what sits behind it.
A Scenario can become an independent Experience with its own permanent identity, lifecycle and access conditions.
The Scenario can keep evolving while an Experience preserves exactly what was created for that particular use.
One blueprint can therefore become many separate experiences.
Private alpha
I built this for myself. Then it kept growing. At some point, letting other people use it started to seem like a reasonable idea.