wildduck VS zitadel

Nodemailer author here. I now publish all my libraries/tools (like Nodemailer) under some permissive license (MIT, MIT-0, ISC). This gives the opportunity to use such a library without issues, and the end user never knows about these tools anyway. For example if I build a OSS software and commercial software that both use such library, then it is easier to manage it under permissive license - I don't want copyleft licenses turning up in my commercial software even if I'm the owner.

For OSS applications, I use EUPL (eg. https://wildduck.email/) or AGPL copyleft licenses. The license does not stop anyone using it as an application, but at the same time people are not free to copy, rename and sell it either.

- https://wildduck.email/ (E-mail)

Even though I have self-hosted things individually (eg: my Ghost blog on a RasPi connected to my home WiFi), something which I've always been concerned about is the separation of all these services, since they must have APIs and access rules. What's an ideal way of setting up a multi-service server like this, and what security policies should I implement. Additionally what are some must haves that you have running on your servers?

I understand self-hosting is a huge labour of love, and I have no qualms in investing time/effort learning :)

The largest WildDuck installation manages 100k+ email accounts with around 300TB of stored emails. So it does not always have to be one of the old and tried softwares. https://wildduck.email/

or install https://wildduck.email or mail in the box type of server, just host it yourself. Wildduck web interface allows you to make unlimited alias already.

I want to create an email service. I want to use MongoDB as a storage option. I want to store every email in a that DB but I can't find an email server technology that supports that. Are there any technologies that support that out there? As far as I could go only wildduck supports that but I don't like their documentation, setup, ecosystem, and more, so I'm looking for an alternative technology.

I use: https://github.com/nodemailer/wildduck for Mails.

I had noticed this/similar feature on wildduck mail server. Checkout the Advanced Security section there, might be what you are looking for.

WildDuck https://wildduck.email/

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.