I’ll obviously disagree with your point that Kee Vault offers nothing new - if it didn’t I wouldn’t have spent a year developing it
However, I’ll leave the info on the website and other topics here to cover all the benefits and just ask specifically about this Trezor system you would like to use.
What makes it immune to malware running on your local system? I get that various hardware enclaves in a system might offer some protection from user and kernel resident malware (the jury is out on whether any have actually achieved this yet but let’s assume for a moment that they have). What I don’t get is how this offers protection to the encryption keys that a password manager utilises to protect the database.
Perhaps you could explain how this Trezor device protects the key material?
And in what way does this differ from the typical KeePass key file which simply adds material from a different part of the infected local system that you’re trying to defend against?
To be clear, I’m all for adding other types of authentication material to Kee Vault in future but right now I don’t see any security benefit in doing so and hence such development work doesn’t have the highest of priorities. Happy to adjust priorities if I’m missing a trick here though!