keep

Writing you own.

A newsletter is one of the most valuable things a person can make: years of thought under one name, and a list of readers who asked to hear more. On every major platform, all of that lives in someone else's building. The name is a subdomain they issue, the list is a row in their database, the archive is theirs to serve. You make the thing; you rent the shelf it sits on.

Keep is a writing network where the shelf is yours too. Every writer on Keep gets a personal server — a small, permanent machine on Urbit with a cryptographic name that belongs to you the way a signature does. Your posts live there. Your subscriber list lives there. Your address on the web points there. We run the machine so you never think about it, but running it is all we do: the writing, the readers, and the name are yours.

Readers follow you directly, server to server, and your email list is exactly that — yours. The addresses live on your machine, not in a platform's database, and mail goes out under your own domain, from a server you control. There is no feed between you and your readers, no ranking deciding who sees what, no company sitting between you and the people who already said yes. When you publish, it arrives — because they asked for it, and nothing else gets a vote.

You don't have to move your life to start. Keep your Substack; Keep mirrors it as you publish, so your archive and your list accumulate on your own machine from day one. Write there, own here — until one day you notice the copy you own is the real one.

And if you ever want to leave, you take everything — the archive, the list, the name — in one export, and the network follows you to wherever it runs next. That isn't a feature we added. It's what owning means, built in at the bottom.

sign in connect your own ship