Building vaultless.dev — OAuth without the console tour (launching Aug 18)
Hey PH
I'm Oliver, solo-founder building vaultless — going live here Aug 18.
The problem: every time I've added social login to a project, it's the same ritual — separate OAuth apps for Google, GitHub, Discord, whatever the app needs, each with its own console, scopes, redirect URI quirks, and a fresh client secret to keep safe. Multiply that by however many providers your users expect, and "add sign-in with Google" turns into an afternoon of yak-shaving before you write a line of actual app logic.
vaultless is my attempt to collapse that into one integration — no OAuth consoles to configure per-provider, no secrets to manage on your end, and a single normalized user object back regardless of which provider someone signed in with.
Right now I'm looking for a small group of early users to integrate it into a real project before the official launch — in exchange, free Pro access for a while and direct access to me for support/bug fixes. If that's you, drop a comment or DM and I'll get you set up.
Also very open to "why not just use X" pushback — I'd rather hear it now than on launch day.

Replies