Not sure if you have considered it, or if there are other posts on this, but consider building a native Windows app for R20 vs. browser. Also, move backend to cloud, so you have much better application instance scaling (on-demand). Maybe Lambda (AWS) for simpler, quick on-demand service calls. The native desktop app would enable asynchronous character sheet and other updating, vs, having character sheets that never populate during peak user activity. The native app experience would also enable you to have much more significant product differentiation too, as a whole new set of dynamic features and effects would be far more accessible to GMs and game designers. Sure it takes money to do it, and I have no idea how R20 is constrained by revenue, but at some point you will lose the market if you can't realistically scale and make people wait for screens that never populate during peak times. Think deeply on your product strategy and spend, as there are competitors that will do this....Just my 2 cents. And yes, I'm from the technology/IT world. It would be interesting to read your thoughts on what I wrote above.
