A hobbyist developer has turned NVENC into a networked GPU bridge that splits FLUX 2 image models across consumer cards over ordinary Ethernet and Wi‑Fi, cutting the need for expensive NVLink hardware and making distributed local inference far more accessible.
The experiment first surfaced on r/StableDiffusion where the author, posting under the handle shootthesound, described a custom NVENC encoder bridge that distributes FLUX 2 model layers across two machines , an RTX 5090 desktop and a laptop 4090 , connected over a standard Ethernet LAN and Wi‑Fi 6, claiming a 4.4 second per image throughput and viral attention on the subreddit within hours.
The developer wrapped NVENC into a transport layer, effectively encoding model activations and sending them over the local network so different GPUs can process different model layers without a physical NVLink connection, while supporting multi‑GPU setups inside one PC and over standard network links including Wi‑Fi 6 and even mobile tethering using Tailscale for routing.
The post says the bridge now supports Flux 2 Dev and Klein 9b models, and that the author has a README and intends to release a version for splitting large transformers across machines soon. Technical discussion on NVENC usage and multi‑NVENC setups has precedent in developer forums, where NVENC chips are treated as independent encoders on each GPU and must be orchestrated at software level.
Why this matters for indie builders
Specialized interconnects like NVLink trade cost for latency and bandwidth, but they are expensive and largely confined to data center or workstation markets where budgets permit. A working Ethernet/Wi‑Fi bridge flips that trade, letting resource constrained builders stitch together consumer hardware for inference without buying proprietary interconnects.
That matters because many startups and indie teams choose between buying a single high‑end server with NVLink or renting cloud GPUs. A reliable peer‑to‑peer bridge lowers the hardware entry cost and keeps data local, which can be important for confidentiality and predictable costs.
How peer‑to‑peer stacks up economically
NVLink and PCIe are engineered for extremely low latency and high bandwidth, essential for synchronous multi‑GPU training and large distributed training workloads, while Ethernet is higher latency and lower per‑link bandwidth but ubiquitous and cheap.
For inference, especially when you can partition a model at layer boundaries, the latency penalty of Ethernet can be tolerated and amortized across batch processing and compression tricks, making peer‑to‑peer bridges a pragmatic economic win for many image and smaller LLM workloads.
Put simply, if you do inference where per‑image latency in single‑digit seconds is acceptable, commodity networking plus NVENC encoding can deliver performance that is close enough to justify avoiding NVLink costs entirely.
Distributed local AI versus cloud renting
Renting cloud GPUs removes ops friction but brings recurring cost and potential data egress and privacy concerns. Local distributed setups keep costs mostly upfront and predictable, and the new bridge shows those setups can now include mixed hardware across machines on ordinary networks, widening the pool of usable devices for a single workload.
This pattern is increasingly visible in hobbyist and small‑team forums where people try to combine 4090s and other consumer cards to reach capacities that previously required workstation gear, and the community has long experimented with offloading components like text encoders to CPU or another GPU to save VRAM.
Limits and open questions
Practical constraints remain. Ethernet and Wi‑Fi add latency and are more sensitive to packet loss and congestion than NVLink, so predictability under load, synchronization, and error handling will be critical for reliable production use.
There are also unanswered questions about generality beyond the tested models, how the approach scales to many‑node topologies, and whether encoding/decoding overheads will erase benefits for different model classes, all of which will require broader tests and community validation beyond the original Reddit demonstration.
The thread has already drawn attention and early ports will likely appear quickly. If the community confirms consistent, repeatable gains, expect tooling improvements that automate partitioning, handle robustness, and add scheduling so small teams can spin up distributed inference clusters over existing office networks.
For founders, the takeaway is concrete. A cheap, networked bridge changes the unit economics for on‑prem inference. You still lose NVLink latency and raw bandwidth, but you gain flexibility and lower capital expenditure, and you keep sensitive data local unless you choose otherwise.
That combination will not replace cloud for every workload, but it opens a new tier of hybrid deployments where startups can iterate locally and only burst to cloud for scale, saving cash and preserving control while still delivering competitive inference performance.
Also read: THORChain's halt turns a $10.8 million exploit into a DeFi test • Monad and Rain are testing stablecoin cards as real payment rails • Strategy is testing its Bitcoin doctrine with a discounted debt buyback
