Product Family

VENDOR.Energy Products

One architecture, different deployment environments. VENDOR.Max is a continuity layer built around a fixed site. VENDOR.Drive carries the same architecture onto mobile platforms and is designed to supply external loads at the point of deployment.

Page scope

This page routes between product configurations. The definition of the solid-state power category and its boundaries belong to Solid-State Power Systems.

Platform

One architecture, two deployment form factors

VENDOR.Energy develops a single power architecture implemented through stationary and mobile form factors.

At the product-family level, the choice between VENDOR.Max and VENDOR.Drive is determined by the deployment environment and integration requirements, not by a comparison of technical ratings.

The load interface is defined by the deployment itself. The engineering sequence behind that choice is set out in How It Works.

Choosing a configuration

Max or Drive

Routing by deployment conditions. Technical characteristics are not the subject of this table.
VENDOR.Max VENDOR.Drive
Primary context Fixed, remote and weak-grid infrastructure Mobile, field and rapidly deployed infrastructure
Typical deployments Telecom nodes, AI edge and distributed compute, remote utility assets, water and process infrastructure Vehicle-integrated systems, mobile command posts, field-portable equipment, relocatable process nodes
Deployment Installed at the site Integrated into a movable or rapidly deployed platform
Role in the infrastructure Continuity layer around a fixed site Mobile power layer designed for the host platform and external loads
Architectural basis VENDOR architecture The same VENDOR architecture
Load interface Determined by the site and its load Determined by the host platform and deployment task; external-load power export is part of the design scope
First project question What has to stay powered? Does the power system need to move with the platform or between deployment locations?

The difference between Max and Drive does not begin with a different architecture. It begins with a different deployment environment.

Find the deployment route

A fixed, remote or weak-grid site — start with VENDOR.Max.

A movable, field or rapidly deployed system — look at VENDOR.Drive.

To assess whether a specific deployment is ready for a pilot, the next step is a Pilot Readiness Assessment.

Infrastructure first. Interface second. Product configuration third.