Menu

Post image 1
Post image 2
Post image 3
Post image 4
Post image 5
1 / 5
0

Your auth server shouldn't cost more RAM than your entire app. So I wrote my own in Rust.

DEV Community·Luis·about 1 month ago
#mphOHDIF
Reading 0:00
15s threshold

I've been using Keycloak for almost 1 year across freelance projects — large-scale enterprise apps and small side projects alike. The appeal was always the same: it's free, battle-tested, and it works. Until it doesn't. The documentation is a labyrinth. Pages and pages of concepts and configurations that make sense if you already know Keycloak, but are genuinely hostile if you're just trying to get started. But the real breaking point was the math. A DigitalOcean droplet with enough RAM to run Keycloak comfortably costs more than most small projects can justify. And SaaS alternatives like Clerk or Auth0 aren't much better — you're paying per seat, per month, forever, while handing your users' credentials to a third party. So two weeks ago I started building my own. Written in Rust. Running in under 20MB of RAM. This is what I learned. The Landscape Problem Let's talk about numbers.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More