A machine that stays on — a NAS, a home server, a spare Mac. Docker and a Postgres. A markdown corpus you already keep, ideally in git.
Install
Self-hosting is not a preference here, it is the architecture — it is why there is no second tenant to leak to and why your files never move. It is also genuine work, so it belongs on the page rather than in a welcome email.
A machine that stays on — a NAS, a home server, a spare Mac. Docker and a Postgres. A markdown corpus you already keep, ideally in git.
The server and its index, a macOS desktop build and an Android build, and an MCP endpoint your agents can point at.
Backups. The vault's markdown is git-mirrored, but annotations and review state live in Postgres — if you do not back that up, they are not backed up.
A compose file, a database, a token, and the indexer pointed at your vault. Then the client, told where the server is. If that sentence reads as a normal evening, you are the person this beta is for.
Right now this is not a one-command install. It is the single highest-leverage thing to fix, and it is the thing most likely to decide whether the beta works at all — if nobody completes the install, the funnel is the product and the annotation model was never the question.
So the beta is small and hand-held on purpose. You will get the artifact, the compose file, and me on the other end of a message while you stand it up.
Before you ask
That is genuinely the right reaction to have after reading this page rather than before.