One uses low pricing, is likable, and provides a fine list of enterprise features. The HN crowd will realise that these features are really different ways of describing a very small amount of code. But if you want to spend your employer's money and don't care to spoil that by telling your managers too much, the list is fine. Engineers who like the likable make money be spent.
One writes per-customer code on top of largely the same body of code, and charges very high prices, largely because they clearly know how to get stuff done using that code. They have the references to prove it, and they wrote the code, and the customers accept that they invoice customers for improvements to the free base too.
One uses a technique I don't understand at all. It's different from the other three, and it works. I mention it to say that the other three aren't an exhaustive list.
The fourth targets nontechnical customers and sell SaaS, I don't know the price level. You can git-clone the code and selfhost if you want, they'll be friendly but not helpful. If you make a PR on github they'll at least look at it.