It was just what I had on hand. I was also using it for another project. It simply had the least amount of danger or cost for hosting a public demo. The bandwi

It was just what I had on hand. I was also using it for another project. It simply had the least amount of danger or cost for hosting a public demo. The bandwidth costs that the Big cloud providers like AWS, Azure, and GCP have simply wasn't there. It also deploys in milliseconds, which was a great developer experience. Copied and pasted from https://github.com/nelsonjchen/gtr-proxy https://github.com/nelsonjchen/gtr-proxy * Cloudflare does not charge for incoming or outgoing data. No egress or ingress charges. * Cloudflare does not charge for CPU/Memory used while the request has finished processing, the response headers are sent, and the worker is just shoveling bytes between two sockets. * Cloudflare has the peering, compute, and scalability to handle the massive transfer from Google Takeout to Azure Storage. Many of its peering points are peered with Azure and Google with high capacity links. * Cloudflare Workers are serverless. * Cloudflare's free tier is generous. * Cloudflare allows fetching and streaming of data from other URLs programmatically. * Cloudflare Worker endpoints are HTTP/3 compatible and can comfortably connect to HTTP 1.1 endpoints. * Cloudflare Workers are globally deployed. If you transfer from Google in the EU to Azure in the EU, the worker proxy is also in the EU and your data stays in the EU for the whole time. Same for Australia, US, and so on.