Maybe. Honestly, it's just been the number one source of deployment issues in our stack, by a large margin, so that may be the frustration talking. It basically

Maybe. Honestly, it's just been the number one source of deployment issues in our stack, by a large margin, so that may be the frustration talking. It basically requires us to treat our Salesforce environments very differently from the rest of our technological stack in ways that can be pretty alien to what's pretty standard development best practices in the rest of the industry. To give one specific example, the way some things cannot be expressed through metadata or updated through API makes it very hard to have any kind of repeatability between environments, making things like e2e testing and CD a lot trickier to deal with. As for your specific question, I'll be honest, I'm not familiar enough with what the competition has to offer, because I tend to avoid these behemoth monolithic locked-in platforms like the plague if I can help it, and my experience with Salesforce so far isn't really making it easy for me to change my mind on the subject.