Please describe what your service is for. I had to click on the Google Elevation API on your „What is Open Elevation“ page to finally understand what your service is for.
I developed Authorizer to have a cross-platform solution without any server/cloud-service.
It is an offline hardware password manager based on PasswdSafe for Android. The concept is to use an old Android phone as your password manager. It can type the password over USB and Bluetooth on your target device. Supports OTP.
I think offline hardware password managers are the most secure.
Including offline backup.
For this, I developed Authorizer to use your old Android phone as your password manager. It can type the password over USB on your target device.
Supports OTP.
Smartcard and WebAuthn support are on the roadmap.
Doing also a lot of modernization on the next weeks.
Still planning to add further things like passkeys (when CTAP 2.2 spec is published) and smartcards. But at first, I have to modernize it a little bit.
Or you directly build the images like GitHub or Azure DevOps so you have your „reproducibility“ again, as everything is inside the images as the hosted ones:
I’m happy to collaborate on Authorizer - a hardware password manager based on old Android phones.
Next milestone: smartcard integration over USB.
I would like to build a lib to abstract USB Gadgets on Linux. This is necessary for adding smartcard support (e.g., to store your GPG keys in Authorizer). I already did a lot of research about it, but more on an amateur level as I’m not a kernel dev.
One further milestone on Authorizer is finding a next device (cheap, not too old Android, smaller, …) to base the development on.
It seems that the use-cases of de-identified authentication are very limited and apply mostly for situations where you don‘t need authentication at all by just stopping the data collection?!
I have unfortunately not yet developed any mouse/keyboard app for this. I only use it for https://github.com/tejado/Authorizer