Passlock roadmap
Please note, this roadmap is subject to change
👩💻 - In progress
✅ - Done
Passkey authentication
Section titled “Passkey authentication”- Passkey registration & authentication ✅
- Management console ✅
- REST API to manage passkeys ✅
- Client library (TypeScript) ✅
- Server library (TypeScript/Node JS) ✅
- Local device credential management (signals) ✅
- Related origin requests (domain migration) ✅
Developer console
Section titled “Developer console”- Realtime logs ✅
- Server library (TypeScript/Bun) 👩💻
- Other DX improvements 👩💻
One time codes
Section titled “One time codes”- Email based one time verification codes ✅
- SMS based one time verification codes
Google Sign In
Section titled “Google Sign In”- Social login using Google Sign In / One Tap
Apple Sign In
Section titled “Apple Sign In”- Social login using Apple Sign In
- TOTP authentication e.g. Google Authenticator
- One-time codes via Email (TBC)
- One-time codes via SMS (TBC)
User management
Section titled “User management”- List user authenticators (passkeys & social logins)
- List user activity e.g. successful and failed logins
- Custom security events
Client libraries
Section titled “Client libraries”Passlock is designed to be language and framework agnostic. We support any backend capable of making REST calls. Our browser library works with most, if not all frontend and fullstack frameworks.
To make life easier for developers, we’ll be adding some lightweight framework specific libraries over the coming months. However, we are very clear that the core framework itself will always remain framework agnostic.