Currently we're looking very hard at Critic (https://critic-review.org/ is a demo site, code's on github) because it looks to offer the closest workflow to what we use.
We're specifically looking for something sorta similar to Gerrit as far as how reviews work, but while actually supporting a feature-branch-heavy workflow where we tend to review branches rather than individual commits, and frequently rebuild/rebase feature branches.
Obviously, if your workflow is different then your needs for a review tool may differ wildly.
Other than that, I took a quick look at your product and it's feature-wise close to something I would want to use. Only comments I would make would be that non GitHub projects generally want the review tool to handle the branch management (a.k.a storing pull requests, flagging their status, etc.): of course only focusing on GitHub lets you not worry about that and get a product running much sooner... You should spend some serious time looking at your page load times as well - I'm 10msec away from your server and the demo code review at https://reviewable.io/reviews/Reviewable/demo/1 took nearly three full seconds to load, even with most static assets already cached since I didn't timeline it on the first attempt.
Developing against the GitHub API does carry some non-trivial advantages: among other things, I never actually clone any repos. This wouldn't be possible with a raw git repo. I'm considering adapting the tool to AWS CodeCommit, though, which might be a decent middle ground. Making my own equivalent of pull requests is actually the least of the changes I'd need to make, though.
And yeah, performance is a never-ending battle... But considering that all the work is done in the browser (fetching sources, diffing, formatting, etc.) I think it's actually not too bad. Again, like running in the cloud, it's a trade-off of in favor of flexibility and development speed.
Upsource also looks very interesting, is that also something you have used? We don't really have a good tool for doing code review at the moment. Also, the VCS browsing capabilities look to be miles ahead of what our current setup offers (almost completely unusable, hijacks the browser back button, no searching, definitely no chance of static analysis, links sent out in email notifications constantly pointed at the wrong thing, etc.).