aturi.to is a toolkit for navigating the Atmosphere: the federated network of apps built on the AT Protocol (atproto), the protocol behind Bluesky, Leaflet, Tangled, Grain and dozens of other clients. Its premise is that a record in the Atmosphere belongs to the person who wrote it, not to the app that happened to render it — so any link to that record should be openable anywhere. Everything here follows from that.
What it does
Four surfaces share one catalog of clients and one URI parser, so they never disagree about where a record can be opened:
- Universal links. Drop an
aturi.to/…URL into a DM, a footer or a bio. The recipient lands on a preview of the record and picks which Atmosphere client to open it in. No login, no client lock-in. - The [Atmosphere Explorer](/explore). Browse any account's PDS: every collection, every record, identity history, the PLC audit log, inbound backlinks, trending lexicons, and a live view of the firehose. Sign in with atproto OAuth to edit records in your own repo.
- A [browser extension](/extension) for Chrome, Firefox and Safari. Jump from a post in one client to the same post in another in one click, or flip on auto-redirect and have links rewritten to your preferred client before they load.
- The [waypoints packages](/docs). The same catalog, link builders and URI resolution the other three run on, published to npm as
@aturi.to/waypoints(zero runtime dependencies) and@aturi.to/waypoints-react, both MIT-licensed, so any app can add the same picker.
Who makes it
aturi.to is built and maintained by dame, a solo developer working on atproto tooling. It is not a company, has no investors, and sells nothing. There is no team behind it, which is worth knowing before you depend on it: expect the response times of one person, not of a support desk.
The whole thing is open source under GPL-3.0-or-later (the two npm packages are MIT so they can be embedded anywhere). The source is on GitHub and mirrored to Tangled. You can read every line that runs, file an issue, or fork it and run your own instance on your own domain.
Accounts and data
There is no aturi.to account. Signing in uses standard atproto OAuth against your existing PDS, so there is no password here to leak and no user database to breach. Access tokens are DPoP-bound and stay in your browser.
Your personalization — waypoint groups, ordering, pins, custom waypoints, colour scheme — is written to a to.aturi.actor.preferences/self record in your own repository, not to a server here. Move to a different PDS and it moves with you. The browser extension makes no background network calls at all and keeps its preferences in local storage. The Terms and Privacy Policy spell out what each surface touches.
For developers and agents
The public API is read-only, needs no key and no account, and sends permissive CORS headers on every endpoint. Start at /llms.txt for an overview written for automated clients, /openapi.json for the typed OpenAPI 3.1 specification, or /docs.md for the whole developer guide as one Markdown fetch.