You can run Steampipe CLI in "service mode", getting access to a Postgres endpoint and a dashboard web server [1]. Other users leverage docker / kubernetes to run it [2]. We also have a cloud hosted option with dashboard hosting, multi-user support, etc [3].
What this is proving is that consumer behaviour is shifting rapidly with us wanting eye catching food with that ow so fuzzy feeling of something being delivered to you without the need to talk to anyone.
Consumers have a higher perceptual need to satisfy their food desires knowing that cooking for themselves might not make the mark.
And with the rise of evergrowing distractions cooking for yourself is a chore now easily avoidable.
Albeit I'll skip trying to rationalise our habits of overindulgence with something that's convenient and satisfying even if it's short-lived...
I've used it for small projects and it's okay. Rq is quite simple and limited in a sense.
I guess what I'd recommend to Mozilla, although fantastic work, is that's it worth trying to compute certain features (data points) upfront to simplify the main model. These calculated features can be used as inputs to the main model possibly reducing the response time.