dockd a reader Join the beta
Why Dockd · a founder's note

We didn't have a reading problem.
We had a noise problem.

A note on why we built a reader for people who still believe a thing worth reading is worth finishing — and a thing worth finishing is worth keeping.

The idea for Dockd started in a tab graveyard. One of us had 312 open across three browser windows. The other had a Notes app titled "to read" with 1,800 lines in it, none of them ever read. Between us, a Slack DM where we'd been swapping articles for four years — most of which the other had never opened.

There was no shortage of things to read. There was a shortage of things we'd finished reading. The pile was not the problem; the pile was the symptom. The problem was the absence of a place that took reading seriously — a quiet room with good light and a chair, and a way to keep what we found.

A page a day is a book a month.

We did the math on a Sunday. Three pages a day, for a year, is more than most smart people read in any given year. The thing standing between us and that number wasn't time — it was friction. The save that never happened. The link that lived in a thread we couldn't find. The article opened on the bus and closed at the office, never reopened.

Dockd is the place that fixes the save. One tap, anywhere — share sheet, extension, paste-a-URL. Stored cleanly, ready when you have a minute, never lost in another tab. We wanted the page to actually happen.

What a reader actually does.

A feed shows you everything. A reader shows you what matters. The difference is editorial, not algorithmic — though we use both. Each morning Dockd produces your Daily Signal: seven reads ranked from your saves, your subscribed feeds, and the things your team has surfaced. Not seventy. Not seven hundred. Seven.

A reader is a knife. The point is to cut.

The picks come with a why — a one-line case for the read. The rest stays in your library, patient, until you want it. There is no infinite scroll. You can finish.

Reading is not a solo act.

The wiki was supposed to hold institutional memory. It holds onboarding docs and a twelve-step instruction for booking a conference room. The reading your team does — the deck someone sent on a Tuesday, the postmortem your favorite engineer linked at 11pm — is the actual memory.

So we built Dockd to be shareable from the start. A team can save into a shared library, annotate together, and read the same morning Signal, ranked from what the team has been reading. A team that reads together compounds together.

Lists are arguments.

A good list is a thesis. Here is the canon. Here are the contrarians. Here is the piece nobody read but should have. Dockd's lists are first-class — nestable, shareable, public if you want, private if you don't. The Discover tool aggregates lists, articles, and verticals into a single place to find your next thing — without ever opening another tab to a feed-shaped distraction.

Audience finds the curators.

The internet is full of writers; it is short on readers worth following. Claim your @handle on Dockd and your reading becomes a public artifact: curated lists, the things you marked up, a profile page that reads like a small editorial publication. Bring an audience or grow one — your reading is the work.

That's the why. The beta is free. We hope you'll read more.