No, it uses the WebView that comes with the operating system to minimize memory usage.

Telling tall tales about your height? Not a sign of greatness

I am very happy with Netcup. https://www.netcup.com/en/server/vps

German soldiers can refuse orders under certain conditions (e.g. if they against human dignity)

This is exciting. My only request here is: whenever it works please release a standalone wasm file somewhere (anywhere). So many projects either require building the wasm themselves, or instead of releasing a .wasm, they release a JS wrapper that auto-loads the wasm/wasm-imports. Its a pain to try to extract the wasm out of those projects.

What I am doing is to create a omnikee-lib crate within the project that will get compiled to WASM, not just plain keepass, because I need additional adapter methods to interface with the web part of the application. I don’t have the bandwidth to turn keepass into a general WASM package that could be npm installed at the moment. As I am dogfooding the crate, I might get to a point where I know what a good JS interface for it would be, though, and the omnikee-lib crate could become the official WASM interface for keepass.

Since it doesn’t come installed by default on a fresh system, my guess would be that you won’t break anything fundamental, but this is pure speculation.

I think the Google as an identity provider example is misleading. The more common use case will be medium to small companies where several admins/developers need to login to various servers and where manually adding and revoking keys across these servers will be cumbersome.

As the other commenter said, in those cases, the organization would also deploy its own IDP.

I have been using it for the last 3 months to expose services from my home internet (plex, wireguard, etc.) through a VPS and I’m pretty happy with it. It’s relatively simple to set up, I haven’t had any outages so far, and it’s nice that it supports UDP port forwarding as well as TCP (for wireguard).