Keycloak isn't very nice to work with in short. It's still not very cloud native and is just a big chunk of software that implements god and the world even if you don't need it to. It's weird to customize as well (thinking of theming and the SPIs).
It almost feels like you'd want to do the opposite, given keycloak is a traditional community open source project while zitadel is a startup=project of the type that has been closing up their licensing en masse in the last few years.
Let me assure you the core product will stay open with a permissive open source license.
That said, there will be components that will be closed source who mainly bring value in the area of identity based threat analytics since even we need a way of monetisation.
Happy to share more thoughts on this if you like to discuss this.
A couple of comments from skimming through it. If I'm migrating from Keycloak, I don't need to see how to set it up. I've already got a keycloak instance running if I'm interested in migrating.
I would have imagined if you are a Keycloak alternative, migrating would be easier. I would have imagined some kind of built-in integration. Provide a service token from Keycloak into your importer tool and let it run. This feels complicated and error prone.
I've already gone through the tedious effort of setting up Keycloak. You'll need some amazing value prop to convince me to set up a whole other system.
Additionally, I have more than Users configured on my keycloak. I have auth providers that are setup such as Epic Games, Riot Games, and Steam. I didn't see a way to migrate those values over.
7 comments
[ 4.3 ms ] story [ 29.6 ms ] threadIn the past we only supported bcrypt while Keycloak used PBKDF2 ;-)
[1] https://github.com/zitadel/passwap#algorithms
That said, there will be components that will be closed source who mainly bring value in the area of identity based threat analytics since even we need a way of monetisation.
Happy to share more thoughts on this if you like to discuss this.
I would have imagined if you are a Keycloak alternative, migrating would be easier. I would have imagined some kind of built-in integration. Provide a service token from Keycloak into your importer tool and let it run. This feels complicated and error prone.
I've already gone through the tedious effort of setting up Keycloak. You'll need some amazing value prop to convince me to set up a whole other system.
Additionally, I have more than Users configured on my keycloak. I have auth providers that are setup such as Epic Games, Riot Games, and Steam. I didn't see a way to migrate those values over.