Granted, I have little experience with on-prem at this point in time. But I imagine it’s a trade-off -- with SaaS, you have to constantly scale technically to s

Granted, I have little experience with on-prem at this point in time. But I imagine it’s a trade-off -- with SaaS, you have to constantly scale technically to support more and more customers, while on-prem would be more focused on scaling support. And I don’t necessarily think you need to support all versions. You can have a defined support policy and EOL versions just like any open source project. I.e. they’re out of luck if they’re running an EOL version, in terms of support. It would also depend on how you handle upgrades themselves, from the distribution DX to how you design the software itself. For example, my SaaS is an API, so I’m very much used to having a versioning strategy that never introduces breaking changes (I’ve written more on that here [0]). So I guess it depends. I don’t necessarily see it being more difficult. Challenging, absolutely, but in a different yet same kind of way. But I guess time will tell once I cross that chasm. [0]: https://keygen.sh/blog/breaking-things-without-breaking-things/ https://keygen.sh/blog/breaking-things-without-breaking-thin...