Would definitely be looking at removing the homespun server aspect and going with a high-performance, low latency paas / serverless setup. Lets you focus on and

Would definitely be looking at removing the homespun server aspect and going with a high-performance, low latency paas / serverless setup. Lets you focus on and deliver the outputs you need (i.e. user interface + data). If I were in your shoes I'd be looking at either: - Firebase (free tier). Probably just using their RTDB for storage. You could conceivably do away with your backend entirely here. - Cloudflare workers + KV storage (~$5 per month?) .. this would give you killer performance and let you write your storage logic in python. You're paying a minimum fee per month here, but in reality that could cover a large number of seperate sites. Both suggestions raise vendor lock-in considerations, but given the use-case it doesn't seem like a major concern. Of course if you're looking forward to the joys of managing a box ...