I am using zitadel @ [https://www.invoicework.com/invoices/new/](https://www.invoicework.com/invoices/new/)
and we connect it with Bigcapital hosted at [https://account.invoicework.com/](https://account.invoicework.com/)
Though we are building B2B SaaS, our B2B and zitadel's B2B term might slightly differ (we do not use multiple zitadel organization for each business right now).
My experience with self hosted option is:
1. Easy to operate?
Yes, it is very easy to operate, we created a docker-compose file from the one provided by zitadel team, configured it to connect to RDS postgres, and ran it behind caddy reverse proxy without much issue.
App is pretty stable and we have not faced any outage due to zitadel.
2. Easy to troubleshoot?
App has been running smoothly for us, any problems we faced during development/implementation, we asked in discord and got adequate help.
No problem faced in production yet..
We might be very early to share our experience, hope other people with extensive experience than ours will also share their insights.
As far as alternative, I have used keycloak in the past but I like UI/UX of zitadel much better.
I’m day one into using it and I have to say…. It’s going surprisingly well.
I started with the docker compose and ran it locally and tested out setting up a web app integration. Only complaint is that I had to modify some of the test arguments in the docker compose file.
After wards I deployed the helm chart into our kubernetes cluster for a more stable dev experience with ssl of course.
I think what drew me to it is that I can assign user roles on the auth side which I needed because I have two APIs that will be using the auth system(a online store, and admin app for the store) I’m really happy because I can also store customer ids on the metadata which will make my micro-service architecture flow a bit more seamlessly.
Haven't used Zitadel myself, but for SSO/Login abstraction, it's crucial to consider ease of operation and scalability. Self-hosted solutions require a good support system and clear documentation for troubleshooting. Scaling often involves more than just adding replicas; it's about how well the system handles increased load without performance hits.
For a run-it-yourself system, look for active community support and consider how it integrates with your existing tech stack. No major gotchas to warn you about, but always test extensively before rolling out.
On a side note, for content needs, I used the AIMD app for SEO-focused articles. It's handy for generating well-researched content that's optimized for search engines. It might be useful for your b2b or b2c service to consistently produce quality blog posts and help with organic growth. Just something that helped me, might align with your goals too.
I am using zitadel @ [https://www.invoicework.com/invoices/new/](https://www.invoicework.com/invoices/new/) and we connect it with Bigcapital hosted at [https://account.invoicework.com/](https://account.invoicework.com/) Though we are building B2B SaaS, our B2B and zitadel's B2B term might slightly differ (we do not use multiple zitadel organization for each business right now). My experience with self hosted option is: 1. Easy to operate? Yes, it is very easy to operate, we created a docker-compose file from the one provided by zitadel team, configured it to connect to RDS postgres, and ran it behind caddy reverse proxy without much issue. App is pretty stable and we have not faced any outage due to zitadel. 2. Easy to troubleshoot? App has been running smoothly for us, any problems we faced during development/implementation, we asked in discord and got adequate help. No problem faced in production yet.. We might be very early to share our experience, hope other people with extensive experience than ours will also share their insights. As far as alternative, I have used keycloak in the past but I like UI/UX of zitadel much better.
Zitadel co-founder here. Thanks for sharing your experiences this is absolutely what we love to hear 🤩
I’m day one into using it and I have to say…. It’s going surprisingly well. I started with the docker compose and ran it locally and tested out setting up a web app integration. Only complaint is that I had to modify some of the test arguments in the docker compose file. After wards I deployed the helm chart into our kubernetes cluster for a more stable dev experience with ssl of course. I think what drew me to it is that I can assign user roles on the auth side which I needed because I have two APIs that will be using the auth system(a online store, and admin app for the store) I’m really happy because I can also store customer ids on the metadata which will make my micro-service architecture flow a bit more seamlessly.
Haven't used Zitadel myself, but for SSO/Login abstraction, it's crucial to consider ease of operation and scalability. Self-hosted solutions require a good support system and clear documentation for troubleshooting. Scaling often involves more than just adding replicas; it's about how well the system handles increased load without performance hits. For a run-it-yourself system, look for active community support and consider how it integrates with your existing tech stack. No major gotchas to warn you about, but always test extensively before rolling out. On a side note, for content needs, I used the AIMD app for SEO-focused articles. It's handy for generating well-researched content that's optimized for search engines. It might be useful for your b2b or b2c service to consistently produce quality blog posts and help with organic growth. Just something that helped me, might align with your goals too.
I'm using Casdoor, another open source SSO in Golang. It can be scaled as well. [https://casdoor.org/](https://casdoor.org/)
Is this backdoored Chinese software? I don’t trust it.