10 GbE on a budget in 2026: NICs, cables, and switches that actually work

You can put real 10 GbE between an editor and a NAS for under $120 a node if you buy used server cards and ignore the retail copper aisle. The expensive way (brand-new 10GBASE-T everything) costs three to five times that and runs hotter for no extra speed. This is the parts list that actually works in 2026, what each piece costs, and the one tradeoff that decides everything: copper RJ45 versus SFP+ with a DAC or fiber.

I run this gear. The whole point of a self-hosted mount is that the network between your machine and the box is the bottleneck, not a subscription, so it is worth getting right once and forgetting about it. If you are still deciding between a switched network and a single direct cable, read Thunderbolt vs 10 GbE first; this post assumes you want a switched 10 GbE LAN.

The fork in the road: RJ45 copper vs SFP+ #

Every budget decision here flows from one choice, so make it first. 10 GbE comes in two physical flavors. 10GBASE-T uses the familiar RJ45 jack and Cat6a cable, the same connector as your gigabit gear. SFP+ uses a small cage that accepts either a Direct Attach Copper cable (a DAC: two SFP+ ends factory-fused to a fixed length of twinax) or a fiber transceiver plus an optical patch cable. Think of RJ45 as a wall outlet you already own a plug for, and SFP+ as a slightly fussier socket that draws far less power and runs cooler once it is wired.

The numbers are not close. Per the cabling comparisons at FS.com and QSFPTEK (checked Jun 2026), 10GBASE-T burns roughly 2 to 5 watts per port depending on cable length and adds about 2.6 microseconds of latency from its block encoding. SFP+ with a DAC sits near 0.7 watts per port and around 300 nanoseconds, because a DAC is essentially a wire with no PHY chip to power or heat. For a two- or three-person edit bay none of that decides your render times, but it decides how hot your switch gets and how cheap your cards are. Used SFP+ server cards are the budget sweet spot. RJ45 is the convenience tax you pay to reuse existing wall cabling.

My rule: if both machines sit within a few meters of the switch, use SFP+ DAC and stop reading the rest of this paragraph. If you need to cross a room or a wall, run fiber. Use 10GBASE-T only when you genuinely cannot run new cable and have to live on the Cat6 already in the walls.

NICs: buy used server cards, not retail boxes #

This is where the savings live. A retail-boxed consumer 10GBASE-T card runs $80 to $130. A decommissioned enterprise SFP+ card with years of life left runs a fraction of that, because data centers dump them by the pallet when they jump to 25 and 100 GbE.

The Mellanox ConnectX-3 (single-port MCX311A, dual-port MCX312A) is the people's champion: $20 to $30 used on eBay (checked Jun 2026), rock-solid Linux and Windows drivers, SFP+. The Intel X520-DA2 (dual SFP+) sits around $35 to $50 used, with the broadest driver support of anything in this class; I have seen Dell-branded X520-DA2 cards at $44.99 shipped. If you want a forward-looking buy, used Mellanox ConnectX-4 Lx 25GbE cards (MCX4121A) now show up cheaply too, and they negotiate down to 10 GbE happily, so you get a 25 GbE upgrade path on a 10 GbE budget.

One honest caveat for the used route: confirm the card is a standard PCIe model, not an OCP mezzanine or a vendor-locked variant, and budget for a low-profile bracket if your case needs one. The ConnectX-3 and X520 both want a PCIe 3.0 x8 slot, which any desktop board from the last decade has.

The Mac exception #

If your editors are on Macs, the used-PCIe-card trick does not apply, because modern Macs have no slots. You buy a Thunderbolt adapter instead, and the budget math changes. The Sonnet Solo10G and the OWC Thunderbolt 4 10G Ethernet Adapter are both $199.99 (checked Jun 2026), fanless, bus-powered, and recognized by macOS with no driver install because they use the Marvell/Aquantia AQC113 chipset Apple already supports. Both are 10GBASE-T (RJ45). For SFP+ Macs, QNAP's QNA-T310G1S bridges Thunderbolt 3 to a single SFP+ port.

So the picture is lopsided: a Linux or Windows tower joins 10 GbE for $20 to $50, a Mac for about $200. That is not anyone overcharging, it is the cost of going through Thunderbolt instead of a slot. Plan your switch around it: if the Macs are RJ45 adapters and your tower NAS is SFP+, you want a switch with both, which is the next section.

The switch: where MikroTik wins #

For a small post setup, one switch dominates the budget tier. The MikroTik CRS305-1G-4S+IN gives you four SFP+ ports plus a gigabit uplink, fanless and silent, managed, for about $140 (ServeTheHome buyers guide, checked Jun 2026). Four 10 GbE ports is exactly a NAS plus three editors. When you outgrow it, the CRS309-1G-8S+IN doubles you to eight SFP+ ports at roughly $230, still fanless.

The cheaper-still outlier is the XikeStor SKS8300-8X, eight SFP+ ports, managed, at around $99. It is genuinely inexpensive; the catch is less mature firmware and a smaller support community than MikroTik, so I steer first-timers to the CRS305 and let tinkerers chase the XikeStor. If you have mixed gear and need native RJ45 ports, the MikroTik CRS312-4C+8XG-RM mixes combo and 10GBASE-T ports for about $500, and the unmanaged TP-Link TL-ST1008F gives eight pure SFP+ ports for $166. I have kept a deeper switch breakdown out of this piece on purpose; for the 2.5, 10, and 25 GbE switch landscape see the best switches for a post studio.

Cables: DAC for the rack, fiber for the room, copper as a last resort #

Cabling is the easiest place to overspend on the wrong thing. Here is the order I reach for them.

DAC first. A passive SFP+ DAC is the cheapest, lowest-power, most reliable short link there is: $20 or less per port, no transceivers to seat, nothing to power. The limit is distance and rigidity. Passive DACs top out around 1 to 7 meters and come in fixed lengths, so they are for a NAS and an editor that sit near the same switch. Buy the exact length you need; you cannot trim a DAC.

Fiber when you cross a wall. Once you are past ~7 meters, run multimode OM3 fiber with a 10GBASE-SR transceiver on each end. That reaches roughly 300 meters, easily a whole studio, for about $25 to $40 per port all in. Fiber is also immune to electrical noise, which matters if your cable run shares conduit with power. The fuss is that you are buying two transceivers and a patch cable, and you must match the transceiver coding to your switch and NIC.

Copper RJ45 only when you must. 10GBASE-T over Cat6a reaches 100 meters (only 55 meters on older Cat6, per the IEEE distance specs FS.com cites), and it reuses RJ45 wall jacks you may already have. That convenience is the entire argument for it. You pay with 2 to 5 watts per port, more heat, ~2.6 microseconds more latency, and pricier cards. If your walls are already wired with Cat6a and re-pulling cable is impractical, copper is the pragmatic answer. Otherwise SFP+ wins on cost and heat every time.

A reference build under $400 #

Here is a concrete three-editor-plus-NAS setup, all SFP+, using the prices above (checked Jun 2026). One CRS305 switch at $140. Four used ConnectX-3 cards at roughly $25 each is $100 (one for the NAS, three for the towers). Four 2- to 3-meter DACs at $18 each is $72. That is about $312 for a fully switched 10 GbE bay, four nodes, fanless and silent.

Swap any Mac editors to a $200 Sonnet Solo10G and one RJ45 port on a combo switch, and the build is still well under what a single year of a per-seat cloud plan costs. This is the part that makes self-hosting pencil out: the network is a one-time purchase, and once your NAS speaks 10 GbE the limiting factor becomes your drives and your mount layer, not your wire. A mount like JuiceMount streams blocks over exactly this link and caches hot media on local SSD, so the 10 GbE fabric you just built is doing real work rather than re-downloading whole files; that said, if all your editors are remote across the public internet, no LAN switch helps and a different architecture applies. For the throughput math on what a tuned link actually delivers to a timeline, see the slow-NAS diagnosis checklist.