Note that Kanban requires a certain maturity and self-discipline from the development team and the stakeholders. If that's a given, Kanban can work very well.

Scrum was really invented for situations where management is constantly asking "when do we get X?" and the development always says "we aren't done yet".

In this scenario, the sprint is meant to reassure management that they'll get at least *something (even if not a full X) in a predictable time, and forces the development team to put something out in a given time frame even if not yet perfect / finished / whatever.

If that's not a problem, Kanban can be indeed be a much better fit, and come with far less overhead.