How does this compare (use cases?) to Webdis?
maybe i'm being a downer, but i feel like the latency of an HTTP request defeats the purpose of using redis in 99% of use cases.
While this may be somewhat useful (particularly due to more fine-grained auth), I believe Redis is already being mostly-RESTful as REST is not about transporting data using HTTP. It's - going by Wikipedia list on REST constraitns - client-server (check), mostly stateless (check; states are only for pubsub and transactions), cacheable (uhm... partially), layered (check), and even has code-on-demand features.
what would the benefit of this instead of rolling out your own REST api on Flask?
This is just adding an extra layer between your data and redis, which defeats redis' purpose of being fast for particular use cases.