Websockets

1

Hi! Please confirm how billing works for long-lived connections.

Do you charge anything per open TCP/WebSocket connection (or per concurrent sockets) separately from standard charges for CPU/RAM, bandwidth, storage, and IPs?

If yes, what is the unit and how is it metered?

If no, are there any limits or quotas at the proxy or machine level we should be aware of (e.g., caps on concurrent connections, idle timeouts)?

Does an idle WebSocket (no traffic for minutes/hours) incur any additional billing beyond the allocated compute and actual data transfer?

2

we don’t charge for open connections, or beyond the list items we explicitly charge for. there isn’t a limit of concurrent open connections, other than whatever is in your fly.toml (or a default of 1000 I believe).
please note that long-running especially idle connections over the internet are likely to be broken due to the nature of the internet, so you should implement pings (which you will be charged for) and implement reconnection logic in your clients.