zitadel VS docker-registry-ui

Im one of the authors of ZITADEL the open source identity and access management solution.

An other Keycloak alternative would be our (I am one of the founders) project ZITADEL.

You could take a look at https://zitadel.ch/ Or curity https://curity.io/product/

I'm biased since I work for ZITADEL (https://github.com/caos/zitadel). Passwordless with FIDO2 has been baked in since the beginning. I reckon that the major Open Source alternatives provide support as well. FIDO2 should work on all major OS and browsers.

And a bigger project i know is zitadel (https://github.com/caos/zitadel)

https://zitadel.ch/ https://github.com/caos/zitadel/

Full disclosure: My company is building ZITADEL, an open source alternative for Auth0 or Keycloak (both still very good, with some drawbacks). https://github.com/caos/zitadel/

We are building a cloud-native IAM over here https://github.com/caos/zitadel

It is written in Go and built around event sourcing for a great audit trail. We already support OIDC, Passwordless, RBAC and working on more features each day.

For those who want to run it on-prem we have a kubernetes operator ready in the next few weeks who also manages the database (cockroach).

We run our own service here https://zitadel.ch with a free tier as well

Feel free to engage with us on GitHub discussions.

I'm not sure if it makes sense to build your own oauth/oidc server. It's fun to learn all these techniques but you have to maintain much more code. You also have to implement security mechanisms from dev and ops perspectives. There are existing implementations. If you want to check out an existing open source implementation in go you could take a look at the implementaion of my company called zitadel. I would love to answer question if there are any.

If it's only the UX you care about then you can use the docker registry image which supports arm64 and then use a ux like docker-registry-ui and have a nice ui.

I didn't know Fleet. For my own images repos (not Dockerhub hosted) I use Docker Registry UI (on top of registry:2). It's tiny and works perfectly fine.

# required to avoid HTTP 411: see Issue #1486 (https://github.com/moby/moby/issues/1486) chunked_transfer_encoding on; # required for strict SNI checking: see Issue #70 (https://github.com/Joxit/docker-registry-ui/issues/70) proxy_ssl_server_name on; proxy_buffering off; proxy_ignore_headers "X-Accel-Buffering";

I use the default Docker registry container, but with Docker Registry UI.

I’m not familiar with jfrog/artifactory but I self-host a registry on my network. I use joxit/docker-registry-ui for visualization. This is just a frontend on the API provided by the docker registry. AFAIK catalog is the best way to list the images