If you ignore the subjective lines two and three of the comparison table, keycloak looks objectively better. And it has an Apache 2.0 license for the whole product.
Honestly, thanks for putting keycloak on my radar.
I see the supertokens team in this thread doing nothing to make me think that they intend to stop misleading people.
I'm happy with the way I've got Keycloak set up (especially ability to simply throw Apache's OpenID Connect in front of arbitrary paths) but I do recommend also looking into alternatives. Keycloak is great for enterprise SSO setups where you need to authenticate to ten different services on ten different domains, but there are much simpler options out there if all you need is auth for a single website!
I imagine the biggest reason to go for Supertokens is the first-party SaaS support. If you want to outsource auth (like Auth0/Firebase Auth/etc. do) then I think there's something to be said for this project. The open source-ness doesn't add too much value in that use case, though.
Honestly, thanks for putting keycloak on my radar.
I see the supertokens team in this thread doing nothing to make me think that they intend to stop misleading people.