i don't see any other use case for this tool other than simple crud apps. what if my app needs to expose data over web sockets or i need to implement an operation that is not an api request? how does this compare to supabase?
We plan to implement data streams and workflows with Lambda style functions that will cover even the most complex application demands in the near future.
Supabase is a nice service with a lot of functionality but requires that you know advanced features of postgres (rls policies etc ..) to properly setup your data security.
With supabase you are bound to what features can be developed on top of postgres which is a double edge sword in my opinion. in addition, we believe that our simple sql syntax over API is much more intuitive and easy to learn in contrast to postgrest syntax.