Skip to content
Passlock
LoginSignupDocs

Passlock roadmap

Please note, this roadmap is subject to change

👩‍💻 - In progress
✅ - Done

Passkeys

Section titled “Passkeys”
  • Passkey registration & authentication ✅
  • Local device credential management (signals) ✅
  • Related origin requests (domain migration) ✅

Hardware security tokens

Section titled “Hardware security tokens”

Libraries

Section titled “Libraries”
  • Client library (TypeScript/Bundler) ✅
  • Server library (TypeScript/Node) ✅
  • Server library (TypeScript/Deno) ✅
  • Server library (TypeScript/Bun) ✅

REST

Section titled “REST”
  • REST API (can be used instead of server libraries) ✅

Developer console

Section titled “Developer console”
  • Management console ✅
  • Realtime logs ✅
  • Other DX improvements 👩‍💻

One time codes

Section titled “One time codes”
  • One time codes (via email) ✅
  • One time codes (via SMS) 👩‍💻

TOTP

Section titled “TOTP”
  • TOTP authentication e.g. Google Authenticator

Sign In with Google

Section titled “Sign In with Google”
  • Social login using Google Sign In / One Tap

Sign In with Apple

Section titled “Sign In with Apple”
  • Social login using Apple Sign In

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.