As a developer, I would be happy to pay you instead of having to develop and maintain a close cousin of your product for an obscene amount of time investment.
However, I often encounter these roadblocks :
1) The product is not opensource and I can't tweak the 2 line of code I need to make it work with - for example - a different OIDC provider without opening a feature request that will take forever to ship.
2) The product is a SAAS one. Company policies, network security and common sense prohibit me from sending any data to an external provider that is not vetted. Sorry.
3) It's difficult to ship (enterprise) software that would require acquisition of a commercial license from a dependency in order to work as expected. It's doable for a critical piece that you can't replace, but it's really cumbersome when every single piece start asking for a license in order to work. As someone setting up some infrastructure, I don't like to depend on batches of commercial software either because renewals are a pain.
Comments
As a developer, I would be happy to pay you instead of having to develop and maintain a close cousin of your product for an obscene amount of time investment.
However, I often encounter these roadblocks :
1) The product is not opensource and I can't tweak the 2 line of code I need to make it work with - for example - a different OIDC provider without opening a feature request that will take forever to ship.
2) The product is a SAAS one. Company policies, network security and common sense prohibit me from sending any data to an external provider that is not vetted. Sorry.
3) It's difficult to ship (enterprise) software that would require acquisition of a commercial license from a dependency in order to work as expected. It's doable for a critical piece that you can't replace, but it's really cumbersome when every single piece start asking for a license in order to work. As someone setting up some infrastructure, I don't like to depend on batches of commercial software either because renewals are a pain.