Workers billing / Best practice question

[full grove]

Hi, I have a question about cloudflare workers billing and im not really sure where to ask. For refrence I have cloudflare tunnels running on one of my servers and im wanting to expose a http server using tunnels and cloudflared. I have both a websocket server and a http stream running. This is all secured using cloudflare access. What I want to do is have all the requests go through a worker and have my own authentication, and have the worker proxy the requests to the tunnel.

My question is if there is a way where I can proxy the http stream and websocket without incuring a large cost and having the worker use cpu and run for the entire duration of the websocket and stream running. I only care about the very begining of the request when I check the auth headers, after that I basically just want to hand it off to tunnels, and as this is a service multiple people will be using I don't want to just give them all access to tunnels but build my own auth method using workers.

Thank you in advance

[swift prism]

That sounds a lot like AI espec with the Overall, you're on the right track bit, and it's totally wrong

[burnt barn]

also no real person uses emdashes — vs -

[swift prism]

Just return the request
https://blog.cloudflare.com/workers-optimization-reduces-your-bill/
This blog is older and mentions the old duration based billing, but if you just do return fetch(request), your worker is done and can be evicted by the system, etc

Unless you're using Durable Objects you're only billed for cpu time and requests nowadays anyway

[swift prism]

ah yea good point

[full grove]

Awesome, Thank you so much!

[proud sundial]

Guess I’m an AI

[supple badge]

Sorry.