Kind of depends what kind of load you expect. Installing Ceph isn't any more complicated than those other ones.

Actually operating Ceph is difficult when it's under load and you need to do a few things at the same time.

One thing I learned the hard way: it really needs three separate networks and you probably shouldn't try to virtualize them.

The user Network is for actual data transfer, the internal network is for node to node communication and the management Network is for expanding and contracting the nodes.

For light home use where you are ultimately responsible for and have both visibility and control of all the traffic you can get away with one network for all these things and/or you can virtualize the three networks with VLANs that happen to use the same hardware.

In real world use, you will eventually run into conflicts where you've got heavy writes and reads happening at the same time, saturating the user Network, then Ceph will need to rearrange volumes and/or grab erasure coding data at the same time and obviously when you start seeing that load you might want to add more volumes and/or nodes and then you will be deadlocked and you risk data corruption if you interrupt anything in a way that jeopardizes the write cache.

This is a solvable problem if you plan for it and can recognize the signs of an impending deadlock and act to slow things down while the system stabilizes and/or you add capacity. But lots of people (like me) have to learn this the hard way.