Riverbed
Trace every API call back to the line that made it
APIs Analytics Paid
Back to leaderboard
Keyring
#5 this weekDrop-in auth that does not own your user table
Auth APIs Auth OAuth Self-hosted Open source
Visit site
keyring.dev
This week
About
Keyring handles sessions, OAuth providers and MFA while your users stay in your own database. No vendor lock-in on the one table you cannot afford to lose.
Where Keyring fits
Keyring sits in the auth corner of most stacks, and is aimed at teams who have outgrown doing this part by hand. It runs on Web and CLI, and is free to start with paid tiers for teams.
The source is public, so the parts you depend on can be read, forked and audited rather than taken on trust.
What you get on day one
Your database, your schema, and 14 oauth providers preconfigured, totp and passkey support, self-host or use the managed edge. The setup is deliberately small: the maker's argument is that a tool you have to schedule a migration for is a tool you will not adopt.
Whether that holds for your team depends on what you already run. The listing below and the feedback from other makers are the fastest way to find out.
What it does
- Your database, your schema
- 14 OAuth providers preconfigured
- TOTP and passkey support
- Self-host or use the managed edge
Feedback 3
Feedback is public and shown to the maker.
Sign in- Mara Ellis @maraellis 2d
Been using this on a 40-table schema all week. The rollback generation alone saved me twice. One request: a dry-run flag that prints the SQL without touching anything.
- Devin Roy @droy 3d
The plain-language summaries are the killer feature. My non-technical PM can review migrations now, which I did not expect to ever type.
- Sana Qureshi @sanaq 4d
Works well with Postgres. MySQL support felt a bit behind, the enum diffing missed a case for me. Filed an issue and got a response the same day.