Passlock roadmap
Please note, this roadmap is subject to change
v2.0 (Passkey authentication)
Section titled “v2.0 (Passkey authentication)”- Passkey registration & authentication
- Management console
- REST API to manage passkeys
- Client library (TypeScript)
- Server library (TypeScript/Node JS)
- Local credential management (signals)
- Related origin requests (cross-domain passkeys)
v2.1 (Developer console)
Section titled “v2.1 (Developer console)”- Developer console
- Realtime logs
- Server library (TypeScript/Bun)
- Other DX improvements
v2.2 (Google Sign In)
Section titled “v2.2 (Google Sign In)”- Social login using Google Sign In / One Tap
v2.3 (Apple Sign In)
Section titled “v2.3 (Apple Sign In)”- Social login using Apple Sign In
v2.4 (TOTP+)
Section titled “v2.4 (TOTP+)”- TOTP authentication e.g. Google Authenticator
- One-time codes via Email (TBC)
- One-time codes via SMS (TBC)
v2.5 (User management)
Section titled “v2.5 (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 client 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.