4 ms·
You might want to have a look on zitadel [1] If you are intrigued into the differences, you can read some of them here [2] Oh and judging from your username:
by ffo 4y ago
You might want to have a look on zitadel [1]
If you are intrigued into the differences, you can read some of them here [2]
Oh and judging from your username: it could be interesting to you... because we use eventsourcing and cqrs ;-)
Disclaimer: I am one of the authors
1. https://github.com/zitadel/zitadel/ https://github.com/zitadel/zitadel/
2. https://zitadel.ch/blog/zitadel-vs-keycloak https://zitadel.ch/blog/zitadel-vs-keycloak
- sebmellen 4y agoWhat is your opinion on ORY, specifically ORY Kratos? We have been building on Kratos for some time now and find that it is not super well documented, but it is still a very pleasant experience and their ORY Cloud project is backed by support from their team. How does Zitadel differ/compare? Do you have similar goals as an organization?
- ffo 4y agoWell to keep it brief, we see it the following way. Use: - ZITADEL: If you want turnkey solution built for the cloud with a great support for B2B, a strong audit trail and self-hosting, but also the option for SaaS - Ory: If you want flexibility to customize all the stuff but are aware that it is not as turnkey as ZITADEL and Keycloak - Keycloak: If you want turnkey with a high maturity and a lot of features but some lack in regard to B2B, cloud native and support This more or less reflects my opinion about Ory. I like the way they built their suite because its totally flexible. But it dislike the fact that it does not feel like a turnkey solution and needs some more work than plugin in a OIDC client. So what we think and aim for is that ZITADEL combines the best of Auth0 and Keycloak [1] while bringing some unique features to the table. For example an unlimited audit trail (built with event sourcing), great self-service capabilities for B2B and B2C cases (customers can manage their own org, user, federation, access) and the possibility to soon run "serverless" (well at least as serverless container). With our cloud service we also allow customer soon to move their data around (see data location [2]). And all of this while being totally open source. 1. Funny image for this https://twitter.com/ffo_sesp/status/1519655412752162818?s=20&t=9RKg_pqBj5PD8gGaYKsejQ https://twitter.com/ffo_sesp/status/1519655412752162818?s=20... 2. https://zitadel.ch/pricing/v2 https://zitadel.ch/pricing/v2
- sebmellen 4y agoMake sense, thank you for the answer! I do think the turnkey solution middleground is badly needed and I'm excited to see where ZITADEL goes. We've already committed heavily to Ory on this project, but maybe on the next one we'll be able to explore ZITADEL!
- ffo 4y agoThank you too. Feel free to join our chat and ask questions any time https://zitadel.ch/chat https://zitadel.ch/chat (discord)
- collegeburner 4y agoLooks nice, but the CockroachDB dependency is kinda a pain for people not already using that. Any plans for alternative db support, like Maria or Postgres?
- doctor_eval 4y agoIf CockroachDB supports the PG wire protocol and appears to be a functional subset of PG then in theory we might be able to just point it at a PG database and it might work :) I too would prefer to use PG than Cockroach, if only because I have ops experience with PG. But Cockroach is certainly intriguing.
- ffo 4y agoThank, we hear you! Currently we are discussing two things for this subject. 1) We think providing an embedded DB of some kind for easy to use cases with ZITADEL might be favourable to some of you (think Sqlite or an embedded CockroachDB ) 2) To allow plain Postgresql besides CockroachDB should be an easy thing to do since we already make use of PG wire protocol. We plan to address this in a 2.X release What do you think of this? Or what DB would on your Wishlist?
- doctor_eval 4y ago
- joekrill 4y agoThat's really surprising to me. I've been building some things with Ory Kratos myself and I find the documentation pretty good. There's definitely room for improvement but I'm typically able to find what I need pretty easily. I certainly find it much more usable than the Keycloak docs.
- jordemort 4y agoI was interested in Zitadel, but because it requires Kubernetes, it can't replace Keycloak in my docker-compose managed homelab setup. If you could just run it as a standalone container, I'd give it a shot.
- stebenz 4y agoSounds like you would be interested in v2 (https://zitadel.ch/v2 https://zitadel.ch/v2) as in it will be provided as single binary, which you should be able to use in our homelab setup. There are a lot of other improvements, but if that's the only dealbreaker, v2 should take care of it.
- jordemort 4y agoYep, that's the only dealbreaker for me - I'll keep an eye out for v2!
- ffo 4y agoLove it, we will definitely create a post here in the next 2-4 weeks.
- getcrunk 4y agoYour v2 pricing model is lame. I was literally pulling out my credit card when I saw the original pricing.
- ffo 4y agoThanks for the feedback. What do you not like of the new pricing? The pay-as-you-go approach? The background to this is, that we got many customers asking for features on the lower tiers and that many of them wanted to have a more linear scaling in their business cases. On the other hand we wanted to make sure, that even from the start you get all security features without paywalling them. The 25K request roughly translate to 10K user per Month and you will be able to get that without a credit card :-)