v0.1 · the first public release
Any agent. Yours to extend.
Connect your life once, on hardware you own — and every agent you admit can read it and act on it. A key and a grant, never a password.
github.com/getpostern/postern · one compose file, one password, docker compose up
FIG. I · ANY AGENT, ONE GATE
Above, the mechanism: three agents, three keys, one gate — each with its own grant, and no per-agent code. The film is the proof, recorded on a running gate.
the loop above runs live — the film is the same gate, recorded
FIG. II · THE SHAPE OF IT
Instead of wiring every agent to every account, you hand each one a key and a grant — over MCP, the protocol agents already speak.
you decide who gets a key
ia small, owner-only door
Run Postern on hardware you control. There is no cloud account, because there is no cloud.
iione credential, sealed once
Connect your calendar, mail, money, health and home to Postern once.
iiigranted · not granted
Grant each agent only the parts you choose. A granted sector is the whole of what it can see.
iv…and the refusal, recorded
Every visit lands in the ledger — reads, actions, and the refusals. Revoke any key, any time.
the gate in section — sources on the left, agents on the right, nothing crosses without a grant
FIG. III · WHY THE GATE, AND NOT GLUE
paste of last month’s calendar… 14 bank statements… the full address book… 3,000 unread emails… a note that says “hopefully the answer is in here somewhere”…
THE OLD WAYThe agent arrives, is handed the index first — then draws just the slice it needs.
The second question costs no more than the first.
The one that left takes nothing with it — the connections were never its to hold. Your context waits at the gate, and one day your agent-written memory will too, handed to the next agent on the day you admit it.
custom glue dies the moment you switch agents · your connections don’t
No second bill and no second setup. Swap the agent next year — keep the context, the grants, and the record.
FIG. IV · THE OWNER’S ROOM
The Console is the owner’s room: every key, every grant, every visit, in one place. Below: a key minted with its grants, in under a minute — drawn with specimen data; yours renders your own.
A KEY AND A GRANT, ~40 SECONDS
nothing is shared until you grant it · untouched sectors stay off
wJ4kT9••••••••••••••••3hQe
shown once — copy it now
The agent’s whole config: your gate’s address plus this key — never a password of yours.
09:14 ledger-keeper read finance
✓ allowed
On the record from its first minute — and revocable in one.
a key and a grant, not new code — minted, granted, recorded
FIG. V · ROADMAP
Giving people their data back has been tried before, and it failed for a simple reason: nothing on the other side wanted to read it. Agents changed that — they’re already paid for, and they’re worse without your real context. What runs today is a working gate. The rest is drawn here, so you can judge it for yourself.
An agent that needs an hour of a colleague’s time presents itself at their gate, and is admitted or refused there. Every owner their own grants; every gate its own record.
Preferences, habits, corrections — today they belong to whichever agent learned them, and die with it. Held at the gate, they’re yours: the next agent starts where the last one stopped.
Every connector today is ours — a ceiling. The fix is a published spec anyone can write against, held to the same grants and the same log as our own.
Someone good at one thing — taxes, sleep, a credit file — publishes an agent and charges for the work. You admit it like any other: a key and a grant, no password handed over, every visit on the record.
When one of these stands, it moves up the page.
FIG. VI · FAQ
How a gate comes up
The gate is open source and the repository is public. There is no list to join. If you can run a container on hardware you own, you can have a gate standing today — sources connected, your first agent carrying a key you issued.
git clone https://github.com/getpostern/postern.git && cd postern echo "POSTGRES_PASSWORD=$(openssl rand -hex 24)" > .env docker compose up -d
Everything after that happens in the Console. Connect a source — a token pasted, an app password, or a consent clicked through, never your account password — then mint a key for your first agent, grant it a sector, and read the record it leaves. The owner’s controls answer on that machine and nowhere else. Agents on the same machine connect at once; for agents that live elsewhere you stand up your own tunnel — Tailscale reaches your other devices, and a public HTTPS address with the gate’s built-in OAuth bridge admits hosted agents like claude.ai. The remote-access guide walks both.
FIELD GUIDES · EVERY PROVIDER, SCREEN BY SCREEN
collected 2026 · specimen № 0001 is reserved for you
If you would rather be told when a release is cut, leave an address.
An email when there is a release worth installing, and nothing else. No newsletter, no sharing, ever.