> Among those features was support for stateful containers and multi-region, something no one else was doing in the container platform world.

Stateful containers? Depending on what you mean by that it seems to me that's a rather bad idea. The idea is that containers don't contain state. Doesn't mean it can't be an application that stores state somewhere else, but the container itself shouldn't be stateful.

If you mean being able to run a database through a container (while still storing the data not in the container) then yes, sure, stateful container. But that's been feasible for a long time. I don't think it's fair to claim that no one else was doing that in the container platform world.