RE price. I found the "plans" where you pay for things you didn't need rather off-putting from other services, especially in our pay-for-what-you-eat CPU/bandwi

RE price. I found the "plans" where you pay for things you didn't need rather off-putting from other services, especially in our pay-for-what-you-eat CPU/bandwidth/etc "cloud" (cringe) world. Higher price -> trust is a tricky one. RE network & dashboard: Good plan. It does seem silly not to show we are using it too. RE go; go is really not experimental anymore, and has been an excellent choice for this kind of concurrent problem. We had something similar in Erlang (internally) and this has been so much faster to build and is much simpler. I get your point and wouldn't normally mention it, but if anyone would be interested it's here :) Thanks for your feedback.