I'd think 100x before deploying this pattern to external customers. The use case shared by fly.io is for internal tooling. If you have a small team that most l

I'd think 100x before deploying this pattern to external customers. The use case shared by fly.io is for internal tooling. If you have a small team that most likely won't grow to more than a few dozen devs, maybe you can get away with it. Shipping it to several external customers will be a horrible nightmare in maintenance and dev productivity. I'd switch jobs if I was working in a project that started applying this. Paying for the HTTP API upfront is a cheap price to avoid the costs of not having it down the road.