They claim that they don't use the JSON type in order to save on storage and I/O, but they don't show any data to back up the I/O savings part of it. They don't

They claim that they don't use the JSON type in order to save on storage and I/O, but they don't show any data to back up the I/O savings part of it. They don't provide any evidence of improved performance over the JSON type, in fact. Storage has become so cheap that Toro's savings are negligible considering you now must maintain their service layer on top of your normal Postgres configuration. I don't see how a bit of storage savings warrants any of those tradeoffs unless they can show a significant performance improvement as well. And if silence tells me anything, it is that this is probably slower than Postgres' JSON type.