A developer platform replaced home-grown auth in two sprints
After years of maintaining bespoke session and SSO code, a developer-platform team consolidated onto Qeet ID — and deleted the legacy service.
At a glance
The challenge
The platform team had built its own session store, SSO bridge, and MFA enrollment over several years. It worked, but every compliance cycle meant weeks of evidence-gathering, and auth incidents were the on-call rotation's least favourite page.
Maintaining the bespoke stack also blocked the roadmap: every new factor or federation request became a quarter of plumbing nobody wanted to own.
The solution
They scoped a migration to Qeet ID in a single planning week. Passkeys, SAML, and TOTP were configured from the dashboard with no new deploys, and a dual-write cutover moved existing users without a maintenance window.
Because Qeet ID self-hosts as a single Go binary, the team kept user data inside their own boundary while inheriting the platform's controls.
The results
Two sprints later the legacy auth service was switched off and deleted. The team reclaimed a meaningful slice of its roadmap, and the next audit inherited Qeet ID's controls wholesale.
“We ripped out our home-grown auth in two sprints. Passkeys, SAML, and MFA were all working in the first week.”
25,000 monthly active users on the house. Production-grade auth, no credit card, no time limit.
- No credit card
- 25,000 MAU free
- SOC 2 · GDPR ready