[btreecat]

> I disagree. If you're a heavy Traefik user you're eventually going to need a feature that has been carefully omitted from the F/OSS projects.

Ok, I use it at home as part of my K8s cluster. I haven't once come close to needing a feature I don't have because it largely does what I need as a proxy and gets out of the way.

What features do you feel a more average of the target audience is likely to need or want to pay for eventually?

[miiiiiike]

> What features do you feel a more average of the target audience

Auth and middleware packages that are essential for a production site.

> I use it at home as part of my K8s cluster.

That's not heavy use.

[btreecat]

> > What features do you feel a more average of the target audience > > Auth and middleware packages that are essential for a production site. > > > I use it at home as part of my K8s cluster. > > That's not heavy use.

Didn't claim it was heavy use, I explicitly stated the context of the use and why I might not have run into the same issues being alluded to.

The question stands, with something like keycloak why would someone pay for an auth layer?

[nickstinemates]

Running it in production for free and complaining about the offering is a choice.

[fisf]

They are not complaining about the price, but about the closed source nature of the product.

[miiiiiike]

I'm not running Traefik in production. The features that I need are all closed source so I moved on.

[stackskipton]

Sure, it's a choice but I think it's more that don't pretend you are open source when your carefully hide things behind closed sourced paid licenses. Be like Microsoft, we have eval version but if you want to use our Windows Server, you will be paying up. Cool, I can make a decision about your software with that in mind.

[bigyabai]

A choice is a far cry from the "standard" the title purports.