The 800V DC Power Sidecar: Anatomy, Conversion Boundary, and Value Migration
·29 min read·Updated
Physical infrastructure · power sidecar
The 800V DC Power Sidecar: Anatomy, Conversion Boundary, and Where the Value Moves
The power sidecar is a rack-adjacent power-conversion object that moves some or all of the AC/DC and ride-through function out of the compute rack. In the 800V-class architectures examined here, it can hand an 800V DC bus directly to the compute rack or perform an additional DC/DC conversion before distribution. OCP Diablo 400 establishes a ±400V bipolar reference architecture, alongside other 350/700V and unipolar configurations in the broader LVDC work, on a rolling path toward native 800V distribution at the facility. The sidecar exists because compute density has moved past what a compute-plus-power-plus-thermal rack can handle. What follows: the 10-layer BOM, the conversion boundary that decides where the value gets captured, and what changes when 800V goes native.
Reader takeaways
What it is
Rack-adjacent object that converts an existing 480 VAC-class feed to ~800V DC (bipolar or unipolar) and hands it to the compute rack via a busbar drop.
Anchor reference
Delta 660 kW in-row: six 110 kW shelves, each with 80 kW BBU, powered by 18.5 kW AC/DC PSUs. Delta separately ships a 1RU 90 kW 800V→50V DC/DC shelf and 1 MW-class in-row systems.
The conversion boundary
Whether the sidecar hands ~800V DC directly to the rack (Option A, high-voltage direct) or steps down to 48V inside the sidecar (Option B) is the strategic architectural fork. At 1 MW, Option B implies ~20.8 kA between sidecar and rack.
Native 800V spans several topologies
OCP LVDC covers 350/700V bipolar TN-S with distributed midpoint, without distributed midpoint, IT variants, and 700V unipolar TN-S / IT. Grounding, protection, connector requal and SiC device class differ across each.
Value migration
Every conversion arrow that disappears from the stack destroys a conversion market. Every arrow that remains concentrates value into the vendor that owns it. So the question is which vendor owns the surviving stages.
01What a sidecar is, and why now
As an illustrative density progression, this analysis uses ~8-15 kW/rack for pre-AI systems, ~30-60 kW/rack for H100-class dense racks, and 100+ kW rack-scale (GB200/GB300 NVL72 at ~120-140 kW per NVIDIA reference architecture) for the frontier (author's synthesis of published vendor and OCP platform specifications, not an industry census). The rack that used to accommodate compute plus power plus thermal cannot host all three at this density. Something has to move out. The sidecar is the physical answer: pull AC-DC conversion and battery ride-through into a rack-adjacent object so the compute rack is free for silicon.
Figure 1
The power sidecar. Facility AC to DC bus to compute rack
The sidecar is the AC/DC boundary object. AC in from existing switchgear on the left, ~800V DC to the compute rack on the right. Rack DC/DC (Vicor / MPS / Navitas / EPC) does the final drop to GPU rails inside the compute chassis. The dashed panel on the right is the future-state facility architecture that removes the sidecar entirely.
02The concrete anchor. Delta 660 kW
The Delta 660 kW in-row is the useful publicly disclosed commercial reference point in this analysis. It grounds the architecture in an announced product; specification-abstraction framing stays weaker.
Figure 2
Delta 660 kW anatomy. Six 110 kW shelves, 80 kW BBU per shelf, 18.5 kW PSUs. 90 kW DC/DC is a separate Delta product; it does not sit inside the 660 kW sidecar.
Delta 660 kW in-row: six 110 kW shelves stacked, each with six 18.5 kW AC/DC PSUs delivering ~111 kW and integrated 80 kW BBU. Total 480 kW BBU across the rack. The 1RU 90 kW 800V-to-50V DC/DC shelf is a separate product and typically belongs to the compute chassis under HV-direct topologies.
03The 10-layer BOM
Ten functional layers grouped into six functional families. Layer 05 is conditional. Under HV-direct topologies it belongs to the compute chassis; sidecar placement sits elsewhere.
Figure 3
Sidecar BOM (SIDECAR ONLY). Ten layers grouped into six functional families
The 10-layer BOM organised into six functional families. Layer 02 (AC-DC conversion) is the highest-BOM-value slot; Layer 04 (energy storage) is analysed across three time horizons but the sidecar contains only the first two (capacitor and battery); the third (facility BESS) is upstream at facility level. Layer 05 is conditional and typically belongs to the compute chassis; sidecar placement sits elsewhere.
Per-layer semiconductor detail and vendor field:
#
Layer
Semiconductor content
Vendor examples
01
Input + protection
SPD: MOV / TVS / GDT depending on protection architecture; passive elements. TVS or semiconductor protection devices where used.
ABB, Eaton, Schneider, Littelfuse
02
AC-DC conversion
SiC MOSFETs + Schottky (primary path); Si IGBTs on cost-sensitive stages
Illustrative BOM allocation ex-Layer-05. AUTHOR SCENARIO with declared baseline. Sensitivity to BBU duration in Figure 5.
Figure 4
BOM allocation (SIDECAR ONLY, ex-Layer-05). Layer share of estimated equipment-level hardware value at ~660 kW reference. AUTHOR SCENARIO, not disclosed supplier BOM.
Layer 02 (AC-DC) is the single largest BOM slot at 35-45%. Layer 04 (energy storage) is the second-largest at 20-30% under a 60-90 second BBU baseline. Baseline strip below the chart declares the topology, BBU sizing and Layer 05 treatment that anchor the scenario.
05How sensitive is that to BBU duration
At fixed power and chemistry, required stored energy scales approximately with ride-through duration. The resulting Layer 04 BOM share is therefore directionally sensitive to duration, though not necessarily linear in a real implementation.
Figure 5
BBU sensitivity (SIDECAR ONLY). Layer 04 share of estimated hardware value as ride-through duration extends
Required stored energy scales approximately with ride-through duration at fixed power. The resulting Layer 04 BOM share is scenario-dependent and becomes increasingly non-linear as storage dominates the architecture. Fixed components (power electronics, enclosure, thermal design, redundancy, integrator margin) do not scale linearly. Baseline used here is ~60-90 seconds; beyond ~3 minutes, storage hardware starts to squeeze Layer 02 and the other slots.
06The semiconductor map
Layer-by-layer semiconductor content in the sidecar, mapped by device family.
Figure 6
Semiconductor content by layer (SIDECAR ONLY). Where Si, SiC, GaN, sensors and MCUs sit
SiC concentrates in Layer 02 (AC-DC) and Layer 05 (compute-chassis DC-DC). GaN is most relevant to Layer 05 post-regulation in architectures that use a high-frequency GaN stage. Si low-voltage MOSFETs and IGBTs populate cost-sensitive stages, battery switching and DC contactor drivers. Sensors and MCUs recur across protection and control layers. Layers 08 and 10 include no material semiconductor content.
07Semiconductor value by device family
Figure 6 maps presence. Figure 7 maps economic weight. Where the semiconductor dollars concentrate across the sidecar plus the compute-chassis DC/DC that hosts Layer 05.
Figure 7
Semiconductor value per MW by device family (SIDECAR + COMPUTE DC/DC combined). AUTHOR SCENARIO on component economics, not supplier revenue.
SiC MOSFETs capture the largest semiconductor $/MW slot at the sidecar plus compute-chassis boundary. SiC Schottky diodes and Si LV MOSFETs / IGBTs provide baseline content across cost-sensitive stages and battery switching. GaN participates via Layer 05 post-regulation on the compute tray. Sensors and MCUs are numerically many but per-unit small.
08The conversion boundary. Where value is captured
Two architectural options. Which boundary the sidecar implements determines which supplier layer captures the conversion value. Delta, LITEON and Chicony are examples on the sidecar side; Vicor, MPS, Navitas and EPC on the rack side.
Figure 8
The conversion boundary. Option A (HV direct) vs Option B (48V distribution)
At 1 MW, an 800V differential distribution path moves ~1.25 kA; the exact conductor current and sharing arrangement depend on whether the architecture is unipolar or bipolar (see §12). Option A puts the high-ratio conversion problem on the compute tray. Option B pushes DC-DC into the sidecar but exposes the sidecar-to-rack interface to 20.8 kA at 1 MW. The physics decides where the money goes.
09The 20 kA problem, to physical scale
1.25 kA vs 20.8 kA at 1 MW. What the copper looks like.
Figure 9
The busbar physics. 800V DC at 1.25 kA vs 48V DC at 20.8 kA, cross-sections to scale
Moving from 48V distribution (20.8 kA at 1 MW) to 800V distribution (1.25 kA at 1 MW) reduces the current requirement by 16.7×. In a simplified current-density-limited conductor comparison, the required copper cross-section and copper mass per metre can fall by roughly the same factor. Actual busbar and cable design is additionally constrained by temperature rise, insulation, enclosure geometry, fault withstand, mechanical strength, creepage/clearance and installation configuration. That materially expands the practical design space for blind-mate connectors and rack-to-rack interconnects under Option A; Option B moves a much heavier current and conductor burden at the same delivered power.
10Why the sidecar exists
The sidecar survives only if the six pressures below outweigh the penalty of introducing another physical boundary between compute and power. The relative weight of each driver varies by deployment; several can reinforce the case for moving power outside the compute rack.
Figure 10
Six drivers behind the sidecar. Why power moves out of the compute rack
The push-out drivers listed above cover silicon density on the rack, current physics at the rack boundary, dynamic load management, brownfield retrofit compatibility, economic lifecycle decoupling, and interface standardisation via OCP Diablo. Several can reinforce the case for moving power outside the compute rack; the relative weight varies by deployment.
11The transition timeline
Sidecar is the near-term hybrid architecture. The transition to facility-native 800V is happening on a rolling horizon.
Illustrative transition path, not a market forecast. Sidecar deployment expands as hybrid 800V architectures enter volume, while facility-native 800V architectures develop in parallel as SST and associated protection ecosystems mature. AUTHOR SCENARIO: sidecar volume could concentrate in the late 2020s before facility-native architectures take a larger share; the exact rollover stays unestablished.
12What changes with native 800V
"800V" is used throughout this piece as the nominal architecture class; the OCP LVDC documents specify several lower nominal distribution configurations within that class, including 350/700V bipolar and 700V unipolar variants. Grounding, protection and device class differ across each.
Figure 12
Native 800V spans several architectures. Five OCP LVDC configurations, five delta profiles
Five OCP LVDC configurations, each with distinct grounding, protection and connector implications. Only architectures with a distributed midpoint retain a midpoint-related monitoring/protection requirement. IT variants use insulation monitoring as part of the protection architecture; grounded-midpoint fault-detection arrangements sit elsewhere. Rectifier topology simplifies at unipolar; SiC voltage class migrates upward.
SO WHAT FOR UNDERWRITERS
Sidecar vendor: ask which of the five topologies the vendor supports today. Multi-topology support reduces dependence on any single architecture; single-topology exposure is a more concentrated architectural bet.
SiC device vendor: verify 1200V-class MOSFET and Schottky product roadmap plus fab capacity. Wolfspeed, onsemi, STMicro and Infineon each run different mixes.
Connector / busbar vendor: ask about 700V continuous requalification status. IT-topology insulation qualification is a separate workstream.
Hyperscaler infrastructure plan: ask which topology the hyperscaler's published architecture and procurement programme align with. Google, Microsoft and NVIDIA are actively collaborating through OCP on the 800V architecture and MVAC-to-800V workstream.
13Who captures the value
Three stacks. Conversion arrows that disappear destroy a market; arrows that remain concentrate value into whoever owns them.
Figure 13
Where conversion value migrates across legacy, sidecar and native 800V stacks
Three stacks side by side. Legacy: rack-integrated AC/DC + ~48/54V distribution. Sidecar today: 480 VAC to sidecar AC/DC to ~800V DC bus to rack DC/DC to GPU. Native 800V tomorrow: MV AC to facility SST to 800V distribution to rack DC/DC to GPU. Each transition removes or resets a conversion market and concentrates value in the stages that remain.
14The vendor field
Sidecar vendors map on two axes: native-sidecar vs extending from an adjacent category, and merchant vs hyperscaler-integrated.
Figure 14
Sidecar vendor field. Native vs extended, merchant vs hyperscaler-integrated
Illustrative sidecar vendor field on two axes. Positioning reflects publicly disclosed product scope and current programme participation, not market share. Vendor classifications ("800V product", "sidecar-form", "OCP participation") should be verified against each vendor's current specification and shipping status before use in diligence; product announcements, reference designs and shipping commercial products are distinct categories. Hyperscaler internal programmes set the specification that merchant vendors deliver against.
15What could kill the sidecar
The sidecar depends on two conditions holding: native-800V facility SST arriving slower than sidecar deployment, and rack thermodynamics staying air-plus-DTC; mass-immersion sits elsewhere. If either changes materially, the sidecar's addressable role could shrink or its form factor could need to change (see Q3 for the redesign case).
Figure 15
Risk quadrant. What could displace the sidecar architecture
Four scenarios on two axes. Top-left is the current thesis path where the sidecar remains important. Top-right compresses sidecar volume as facility-native 800V arrives. Bottom-left forces sidecar redesign around immersion form factors. Bottom-right eliminates the sidecar layer entirely. The quadrant mix determines which parts of the sidecar vendor's technology stack remain valuable.
OBSERVABLE DILIGENCE TESTS FOR SIDECAR-VENDOR UNDERWRITING
Watch: hyperscaler facility-SST procurement. Meta, Google, Microsoft or other hyperscaler tenders for MV-AC-to-800V facility SST at production volume are the leading signal for Q2/Q4 arriving faster than the base case. Contract awards, not press releases.
Watch: immersion deployment at >100 kW rack-equivalent density. Two-phase or single-phase immersion moving into production AI infrastructure at scale is the leading signal for Q3/Q4. Distinguish demonstration deployments from committed capex.
Vendor durability check. Ask whether the sidecar vendor's technology stack survives the top-right and bottom-left scenarios. Native-topology-agnostic AC/DC content survives top-right; immersion-compatible mechanical design survives bottom-left. Single-topology exposure is a more concentrated architectural bet.
16Topology per risk scenario
Each Fig 15 quadrant has a distinct physical topology. Power path, cooling, grounding, and 10-layer BOM impact for each.
The current thesis path. 480 VAC in from grey-space, sidecar rack does the AC-DC + BBU + DC bus, ~800V DC drops into the compute rack, on-tray DC-DC to GPU. Cooling stays DTC. All ten sidecar BOM layers are active.
Figure 16a
Q1 detailed topology. Sidecar remains important · full 10-layer BOM active
Full Q1 topology. Facility 480 VAC → 660 kW sidecar rack (6 × 110 kW shelves, each 6 × 18.5 kW AC/DC PSUs + 80 kW BBU with aluminum-capacitor energy storage) → ±400 VDC bipolar bus at midpoint TN-S → OCP Diablo blind-mate busbar drop (1.25 kA at 1 MW across the 800 V differential) → compute rack with 90 kW rack DC-DC → GPU trays. DTC cooling via row CDU and cold plates; sidecar itself air-cooled per Diablo 400. All ten functional layers are represented in the overall architecture; Layer 05 remains in the compute chassis; sidecar placement falls away.
Q2 · Sidecar bypassed by facility SST. Fast 800V + low immersion
Facility SST arrives fast. MV AC to 800V DC at facility level; row-level busway to compute rack. Sidecar disappears from the physical path. Layers 02/04/06 migrate to facility scope; the rest eliminate at the sidecar.
Full Q2 topology. Facility MV AC feed → multi-MW facility SST (illustrative stack: MV rectification → HF isolation → 800V conversion → protection/BESS interface) → 800V DC hall busway → compute rack (unchanged Layer 05 DC-DC → GPU trays). Cooling stack unchanged from Q1. Sidecar-level BOM: Layer 02 migrates to facility SST, Layer 04 migrates to facility BESS, Layer 06 migrates to facility protection scope, Layer 05 unchanged. Remaining layers are eliminated from the sidecar BOM (they remain at the system level, picked up elsewhere).
Q3 · Sidecar redesigned for immersion. Slow 800V + high immersion
Native 800V slow; immersion mainstream. Sidecar retained but Layers 08, 09, 10 redesigned. Compute moves from conventional liquid-cooled rack infrastructure into an immersion-qualified enclosure or tank architecture.
Figure 16c
Q3 detailed topology. Sidecar retained but redesigned · compute in immersion tanks
Full Q3 topology. Sidecar rack retained. Layers 01-07 remain broadly in scope, while Layers 08-10 are the most visibly redesigned: Layer 08 (busbar drop) requires an immersion-compatible electrical interface, Layer 09 (thermal) may migrate into the immersion heat-rejection system, Layer 10 (cabinet) changes with the enclosure form factor. Compute moves from conventional liquid-cooled infrastructure into an immersion-qualified enclosure or tank architecture; on-tray DC-DC (Layer 05) requires immersion-qualified variants. Cooling may shift to an immersion-based heat-rejection architecture, potentially eliminating or materially changing the CDU function depending on the specific implementation.
Q4 · Sidecar eliminated. Fast 800V + high immersion
Both drivers flip. Facility SST + immersion-qualified compute enclosure replace the sidecar path in this scenario. Ride-through migrates to facility BESS; DC-DC migrates to immersion-qualified on-tray modules.
Full Q4 topology. Facility MV AC → multi-MW facility SST (unchanged from Q2) → 800V DC hall busway → immersion-qualified compute enclosure directly (no sidecar intermediate). Immersion can change the thermal interface and may reset or remove the conventional rack CDU depending on the heat-rejection architecture; higher supply temperature enables more free-cooling hours. Sidecar 10-layer BOM: Layers 02, 04, 06 migrate to facility SST/BESS/protection; Layer 05 redesigned for immersion; Layers 01, 03, 07, 08, 09, 10 are eliminated from the sidecar BOM (they remain at the system level, picked up elsewhere). The conventional vertical rack may cease to be the dominant physical form.
WHAT CHANGES BETWEEN QUADRANTS
Power path: Q1 uses 480 VAC + sidecar AC/DC. Q2 and Q4 use MV AC + facility SST. Q3 keeps 480 VAC + sidecar AC/DC but with a redesigned tank interface.
Rack form: Q1 and Q2 use vertical compute racks. Q3 and Q4 use immersion-qualified compute enclosures; the physical form factor may differ from the conventional vertical rack.
Cooling architecture: Q1 and Q2 use DTC liquid + facility CDU. Q3 and Q4 use immersion (two-phase or single-phase) with dielectric fluid connecting to facility heat rejection; the CDU role may be reset or removed depending on the specific implementation.
Sidecar role: Q1 all 10 layers active. Q2 mostly eliminated, Layers 02/04/06 migrate to facility. Q3 all layers present, Layers 05/08/09/10 redesigned. Q4 all layers displaced. Sidecar-vendor durability tracks how many quadrants the vendor's product survives.
Method + sources. Anchor references from Delta Americas (660 kW / 6×110 kW shelf / 80 kW BBU per shelf / 18.5 kW AC/DC PSUs / 1RU 90 kW 800V→50V DC/DC shelf), Open Compute Project (Diablo 400 v0.5.2 ±400V midpoint architecture; DCF Power Distribution LVDC white paper covering 350/700V bipolar TN-S with and without distributed midpoint, IT variants, and 700V unipolar TN-S / IT), and NVIDIA 800 VDC architecture material. Vendor examples across LITEON, Chicony, Flex, Vertiv, Vicor, MPS, Navitas, EPC, Wolfspeed, onsemi, STMicro, Infineon, Bender, LEM, Allegro, TI, ADI, Renesas.
BOM value definition. "BOM value" throughout this piece means estimated equipment-level hardware value at the sidecar boundary, before installation, engineering, integrator margin and site costs. It excludes manufactured BOM, component cost, installed equipment cost and supplier revenue. BOM allocation ranges in Figure 4 and the sensitivity in Figure 5 are AUTHOR SCENARIO illustrative estimates. Supplier quotations and disclosed product BOMs are outside the source set. BBU baseline is ~60-90 seconds ride-through (author scenario, not an OCP or Delta specification) and should be verified against product-specific implementation before use. Layer 05 is excluded from the total to prevent double-counting with compute-tray DC/DC. Transition timeline in Figure 11 is directional; adoption pace depends on hyperscaler procurement volume, SST maturity, and immersion cooling deployment.
No advisory relationship with any named party. Nothing here is investment advice.