These are distributed as enterprise binaries. It's common to face _at least_ one or two weird errors in production. Then you have to raise a ticket to support.
Would you like to know how it is discussing a binary-obfuscated error with Customer support? And then after few weeks being assigned to a newly joined fresher? And so on and on, where every person or layer every week says "you're doing it wrong" and you have to restart your proofing and explanation process from scratch?
Hint: After few weeks/months of this (or after 4 times of restarting your proofing process), you start questioning your sanity and life choices.
In those days, all I wished for is just "source-available", so that I can just debug myself what is going on and provide a concise bug report, instead of talking to support.
The weird part is, I'm pretty sure, on the other side, Oracle/IBM also LOST money in that same process. They had to hire an army of people. It was lose-lose on both sides.
Source-available means customers of that software can perform debugging themselves and file pretty good support tickets.
If you are an enterprise today, you would absolutely consider make it source-available to save on your own costs.