Congrats on the launch! Glad to see more people working on these kinds of problems.

As someone who hasn't built one of these systems before... What does Razorfish give you that running Socket.io as a separate microservice that talks to your existing API service over an existing message queue doesn't? Is it for people with architectures that don't have an existing queuing or API services already? Or does it handle sharding the Socket.io part easily which usually has to be vertically scaled?

(Sorry if these questions don't make sense, I haven't dug into my requirements for these things yet but I know they're coming up!)

I think a very clear explanation of that would help me (and maybe others) understand its value and how hard it would be to roll your own here.