keyring.sh
pre-launch — this is a survey, not a product. yet.

Your authorized_keys files are a crime scene.

Keys for people who left in 2024. Keys nobody can identify. Keys copied to servers you forgot exist. KeyRing is one central database of users and their keys — add someone once, they're everywhere they should be. Revoke them once, they're gone. Actually gone.

$ take the 60-second survey 3 questions. no spam.
you, last tuesday, 23:47
$ ssh-copy-id -i dave.pub web-07 $ ssh-copy-id -i dave.pub web-08 $ ssh-copy-id -i dave.pub web-09 # wait. did I do web-04? $ ssh-copy-id -i dave.pub web-04 # dave quit 3 months ago. # his key is still on 41 servers. probably. $
[1] ADD ONCE $ keyring add dave --group prod

User and key land in one central database. Not in 41 scattered files.

[2] SYNC EVERYWHERE ✓ 41 servers in sync

Servers pull the current truth. Groups decide who goes where. No loops over servers.txt.

[3] REVOKE INSTANTLY $ keyring revoke dave

Offboarding takes one command, not one afternoon and a prayer.

MCP SERVER INCLUDED

Or just tell your AI to do it.

KeyRing ships an MCP server. Manage access from the dashboard, the CLI — or by asking your assistant in plain English while you do literally anything else.

assistant session
offboard dave — revoke everything except the staging boxes
⚙ keyring.revoke_user { "user": "dave", "exclude": ["staging-*"] }
✓ Done. Dave's key removed from 38 servers in 4.2s. Kept: staging-01, staging-02, staging-03.

Help us build it. (Or tell us it's a dumb idea.)

Three questions, one email, zero newsletters about "synergy".