We are continuously developing and improving SystoLOCK
Here is a list of upcoming updates. You can also suggest your own ideas using the form on this page
What we are working on
The below list is not a firm plan, but rather a set of ideas that are constantly evaluated, based on the needs, market and competition.
Authentication
..Q2 2025
..Q2 2025
NFC/RFID token support
Authenticate with any proximity token or card, be it DESFire, Legic, or anything else. If you have a reader that can read the card, we can work with it. Using cards to enter the building? You will be able to use the same card to login.
Authentication
..Q4 2025
..Q4 2025
FIDO support
Everyone wants to use FIDO tokens, and so do we. FIDO authentication will be seamlessly integrated into SystoLOCK as once were the smart cards. No Azure required.
Authentication
..Q4 2025
..Q4 2025
Fast Login (and ECDH) support for VPN, Offline, etc.
Want to use Fast Login in remote or disconnected scenarios? This feature will provide you the same seamless experience you know from online authentications.
Management
..2026
..2026
Companion policies
Always wanted to control Companion from the console? Good idea! This will allow central policing of various app aspects directly from the server-side.
Authentication
..H1 2026
..H1 2026
PassKeys support
Actually is SystoLOCK Companion superior to a possible passkeys functionality. Once FIDO is implemented, we will re-evaluate the need for smartphone-based passkeys in SystoLOCK.
Management
..2026
..2026
Offline login policies
Offline login policies should control how and when offline-enabled computers are allowed to accept an offline login.
Management
..2026
..2026
OATH policies
OATH policies are all about lifetime and behavior of TOTP/HOTP tokens and self-configuration options.
Cryptography
..2026
..2026
OPAQUE/PAKE implementation for PIN storage
This feature is there to make PIN storage more secure by making use of modern cryptography.
Self-service
..2026
..2026
Recovery options for forgotten devices and PINs
We reduced help-desk calls by eliminating passwords. But now users might loose or forget their authentication devices. Let us help them by introducing recovery.
Authentication
..2026
..2026
Integration with LAPS
Now that LAPS is part of Windows, we can allow administrators to use its infrastructure and login as local users.
Authentication
..Future
..Future
Smartwatch controlled login
If we can use smartphones for logins, why don't extend this to smartwatches? Is there a demand for this?
Infrastructure
..Future
..Future
ARM64-based Windows client
As ARM is making its advances into the Windows (think Surface), we might need to port SystoLOCK client to ARM.
Infrastructure
..Future
..Future
Mac Client (for domain-joined Macs)
Only an idea so far, with not enough market demand, this might change in the future. What do you think?
Authentication
..Future
..Future
More second factors support: biometric sensors?
Any detached identification can serve as an authentication factor. Which one is on your wish list?
Infrastructure
..Future
..Future
More remote clients support
Mac RDP client is currently NLA-exempt for SystoLOCK. And so are Linux clients. Once there is a bigger need for those, as well as for native Citrix receiver, we might roll them out.
Internals
..Future
..Future
.NET Core support
Many SystoLOCK components run on .Net Framework due to many Windows-induced dependencies. The future surely wants us to migrate to Core one day.
Management
..Future
..Future
Windows Admin Center support (if it stays alive)
Do you like SystoLOCK MMC? We do. But Microsoft wants everyone to write management shells for Admin Center. Wo don't. Not completely impossible, but an unlikely development we might undertake if necessary.
Would you like to suggest an update?
Fill in the form below and we will be right with you!
Get in touch