This story is for me a real painful death I have experienced way too many times, absolutely nuts.
But then you find an open source solution which is in general better and can do everything you want (simply tested already with just a docker compose up) but for deployment you get hit hard by compliance who just checks the SOC2 certifications and wants a in-depth due diligence of the code since everyone in the world can theoretically change it.
Then your manager asks how it can be so good if it's for free and open source.
And of course, last but not least, your overloaded team in general not happy to support just another unpredictable piece of software...
So it's the question to rather burn money and nerves with an awful SaaS offering and their endless and useless sales cycles and terrible and super expensive vendor-lock-ins or burn some money and nerves by utilising and running open source inhouse...
So typically I prefer to chose for the open source option and especially if the SaaS option isn't allowing me easy and fast self-onboarding, meaningful testing periods and a predictable and transparent pricing.
And then, if it get's widely adopted, I allocate some budget to support the authors and/or get some support plan (for more complex open source software) in place even though you most likely never need it...
But then you find an open source solution which is in general better and can do everything you want (simply tested already with just a docker compose up) but for deployment you get hit hard by compliance who just checks the SOC2 certifications and wants a in-depth due diligence of the code since everyone in the world can theoretically change it. Then your manager asks how it can be so good if it's for free and open source. And of course, last but not least, your overloaded team in general not happy to support just another unpredictable piece of software...
So it's the question to rather burn money and nerves with an awful SaaS offering and their endless and useless sales cycles and terrible and super expensive vendor-lock-ins or burn some money and nerves by utilising and running open source inhouse...
So typically I prefer to chose for the open source option and especially if the SaaS option isn't allowing me easy and fast self-onboarding, meaningful testing periods and a predictable and transparent pricing.
And then, if it get's widely adopted, I allocate some budget to support the authors and/or get some support plan (for more complex open source software) in place even though you most likely never need it...