> Opening a raw socket from a worker combined with a basic HTTP implementation could let you create a dynamic proxy Yep, see: https://github.com/zizifn/edgetun

> Opening a raw socket from a worker combined with a basic HTTP implementation could let you create a dynamic proxy Yep, see: https://github.com/zizifn/edgetunnel https://github.com/zizifn/edgetunnel > Related, does waiting for I/O count as "cpu time"? No. > but most of that will be waiting for packets to flow back and forth. If you don't await on the contents but simply pipe the streams in and out, you should be well within CPU-related limits.