Nonlinear Electrodynamic Power Architecture · Validation Stage TRL 5–6

2.4–24 kW Infrastructure Power System
for Remote and Weak-Grid Environments

VENDOR.Max is an electrical power system operating within classical electrodynamics, implemented as an Armstrong-type nonlinear electrodynamic oscillator (TRL 5–6).

At the complete device boundary, all output remains fully constrained by energy conservation. Inside the operating regime, energy is redistributed across functional paths within the device boundary.

Air and gas serve as the interaction medium — not as an energy source.

The current evidence base sits within a staged technical validation framework: system-level laboratory validation is complete at TRL 5–6. Independent verification is the next planned validation milestone.

A regime-based system operating within classical electrodynamics — not a conventional fuel-burning power source.

TRL 5–6 System-level validation stage
1,000+ hrs Operational data (internal controlled testing)
WO2024209235 PCT patent family
CE / UL Certification pathway defined
Remote weak-grid infrastructure environment for VENDOR.Max deployment

Architecture · Technical Overview

How the Architecture
Is Structured

VENDOR.Max uses a two-contour architecture within classical electrodynamics: an Active Core for regime formation and a Linear Extraction contour for power output via Faraday induction, with no galvanic coupling between them. Boundary logic, measurement framework, and full mechanism details are documented on the dedicated How It Works page.

Engineering Classification · System Boundaries

What VENDOR Is —
And What It Is Not

VENDOR.Max is an open electrodynamic engineering system at TRL 5–6, designed for infrastructure deployment in environments where grid connection is unavailable, unreliable, or economically prohibitive. Implemented as a patented two-contour electrodynamic architecture. A startup impulse initiates the operating regime; device-boundary energy accounting applies throughout operation.

The operating regime structures internal energy transfer within the device boundary.

A VENDOR infrastructure power node is an open electrodynamic engineering system operating in a controlled nonlinear resonant regime. The architecture uses two functional contours within classical electrodynamics: Active Core for regime formation and Linear Extraction for power output (via electromagnetic induction — Faraday’s law, no galvanic coupling).

An externally supplied electrical startup input is required to initiate the operating regime; device-boundary energy accounting remains applicable throughout operation.

The two-contour architecture separates the control function (regime formation in the Active Core) from the delivery function (power output via Linear Extraction — electromagnetic induction per Faraday’s law, with no galvanic coupling to Circuit A). These are distinct architectural roles within a single engineering system evaluated at the device boundary: Pin,boundary = Pload + Plosses + dE/dt

Operating regime: An externally supplied electrical startup input initiates the operating state, in which controlled energy transfer is established and maintained. Feedback and control structure energy transfer between functional paths within the device, with all losses accounted for at the device boundary under defined operating conditions.

The surrounding gas or air functions exclusively as an interaction medium — not as an energy source, not as fuel, and not as a consumable.

Validation stage TRL 5–6 with over 1,000 cumulative operational hours from internal controlled testing. Patent WO2024209235 (PCT). Granted: ES2950176 (Spain).

VENDOR Is

  • An open electrodynamic engineering system operating in a controlled nonlinear resonant regime
  • An infrastructure power node designed for deployment autonomy in weak-grid or off-grid environments
  • A two-contour architecture: Active Core (regime formation) + Linear Extraction (power output via Faraday induction, no galvanic coupling)
  • A system where energy transfer is shaped by internal architectural dynamics, not by a simplified linear source-to-load model
  • A system requiring nonlinear regime analysis for technical evaluation — not a linear Pin → Pout model
  • A patented architecture at TRL 5–6 (pre-commercial validation stage)
  • A system with defined operating limits: BMS prioritises regime stability over load delivery when available power is constrained. The load path receives available surplus after regime-maintenance requirements are satisfied. This is a design principle — not a defect.
    → Full BMS logic

VENDOR Is Not

  • × A closed energy system — energy balance is evaluated at the device boundary, and startup initiation must not be confused with internal regime operation
  • × An air- or gas-powered system — air and gas function only as interaction medium, not as energy source
  • × A battery storage system — no electrochemical storage, no charge cycles
  • × Structurally dependent on solar or wind intermittency as a primary operating condition
  • × A grid-dependent centralised architecture — designed for node-level deployment
  • × A commercially certified product at the present stage — CE/UL certification pathway is defined and milestone-linked
  • × A linear input-output architecture — system evaluation requires both regime-level interpretation and device-boundary accounting
Energy balance: An externally supplied electrical startup input initiates the operating regime, and device-boundary energy accounting remains applicable throughout operation: Pin,boundary = Pload + Plosses + dE/dt  → See Validation Framework
Engineering context: This system operates within nonlinear electrodynamics, with device-boundary energy accounting and validation-stage engineering context. Performance characteristics remain subject to CE/UL certification milestones. Patent: WO2024209235.

Technology Status · Validation Evidence

Validation Data.
Not Marketing Claims.

TRL 5–6

System-Level Validation Stage

System-level validation in a controlled laboratory environment. Pre-commercial stage. CE/UL certification pathway defined.

→ Validation details

1,000+

Operational Hours

Cumulative internal laboratory operational hours including extended operational cycles. Internal metric. Independent verification is the next planned validation milestone.

→ Endurance test

Patents

Granted and In Examination

ES2950176 — Spain (granted) WO2024209235 — PCT publication Regional examination pathways: EU, CN, IN, USA.

→ Patent portfolio

37

EPC Designation States

EP23921569.2 entered the European regional phase, with examination in progress across designated EPC states.

CE / UL

Certification Pathway Defined

Structured roadmap from TRL 5–6 to TRL 8 certification readiness. Independent verification pathways (DNV, TÜV, or equivalent) are being evaluated as part of the roadmap.

→ Roadmap

VENDOR.Max

Deployment System

2.4–24 kW infrastructure-scale deployment architecture validated at system level under controlled laboratory conditions.

→ Product overview

Product Architecture · Infrastructure-Scale Deployment

Infrastructure-Grade
Deployment Architecture

VENDOR is focused on infrastructure-scale deployment for sustained operation under real-world load conditions. The current deployment architecture is centered on VENDOR.Max as the primary deployment system for telecom, AI/edge, and remote critical infrastructure.

VENDOR.Drive refers to the mobility-oriented deployment use of the VENDOR.Max architecture in vehicle and transport-linked infrastructure environments.
Infrastructure-Scale Power · Primary Deployment System

VENDOR.Max

2.4–24 kW

An infrastructure-grade power node designed for sustained operation under infrastructure-relevant load conditions. An externally supplied electrical startup input initiates the operating regime. Engineered for telecom towers, AI/edge infrastructure, and remote systems where uptime and reduced dependency on external logistics are required.

  • Designed output: 2.4–24 kW per node (design target)
  • Sustained operation under infrastructure-relevant load conditions
  • Reduced dependency on refuelling logistics in target deployment environments
  • Solid-state energy conversion architecture
  • Reduced dependency on battery cycling and storage degradation
  • TRL 5–6 · Validation stage
VENDOR.Max infrastructure power node in industrial deployment environment

Target Deployment Environments · TRL 5–6 Validation Stage

Infrastructure Environments
With Limited or Unstable Grid Access

Remote telecom tower infrastructure

Telecom Tower Infrastructure

Remote towers, 5G edge nodes, and base stations. VENDOR.Max is designed for infrastructure deployment where fuel logistics are costly, unreliable, or operationally limiting.

→ Telecom Solutions
Remote off-grid critical infrastructure

Remote & Off-Grid Critical Systems

Mining sites, research stations, emergency power operations, and any mission-critical asset in a weak-grid or no-grid environment where uptime defines operational viability.

→ Off-Grid Critical
AI edge compute infrastructure power
Fastest-growing infrastructure demand segment

AI & Edge Compute Infrastructure

Distributed AI inference nodes, GPU edge clusters, and compute infrastructure requiring reliable, continuous power in grid-constrained environments where infrastructure scalability is limited by energy availability.

→ AI / Edge Solutions
Mobile infrastructure power systems

Mobile Infrastructure Systems

Mobile and vehicle-based infrastructure environments where power availability, fuel logistics, and uptime constraints directly affect operational capability. VENDOR.Drive refers to the mobility-oriented deployment use of the VENDOR.Max architecture in these environments.

→ Mobile Infrastructure
Utility and water infrastructure power

Utility & Water Infrastructure

Water treatment, pumping stations, grid-edge utility systems, and remote distribution infrastructure where continuous power availability determines service delivery and operational safety.

→ Utility & Water
Industrial security monitoring power infrastructure

Industrial & Security Monitoring

Industrial monitoring, perimeter security, access control, and telemetry systems in environments where power infrastructure reliability directly affects operational continuity and safety.

→ Industrial & Security

Frequently Asked Questions · Technical Evaluation

Questions About the Technology
and VENDOR.Max Architecture

Direct answers for engineers, investors, and technical reviewers. Every answer is precise and verifiable.

Does VENDOR.Max require external electrical input?

Yes. VENDOR.Max is an open electrodynamic engineering system, not a closed one. A startup impulse initiates the operating regime, and device-boundary energy accounting applies throughout operation:

Pin,boundary = Pload + Plosses + dE/dt

Sustained operation remains subject to complete device-boundary accounting under conservation of energy. System efficiency does not exceed unity: η ≤ 1 for steady-state averaged power. The system does not generate energy and does not extract energy from air or gas.

Is VENDOR.Max consistent with classical physics and boundary-level energy accounting?

VENDOR.Max operates entirely within classical electrodynamics. It is an open electrodynamic engineering system in a controlled nonlinear resonant regime, with all energy transfer subject to conservation laws at the device boundary.

A startup impulse initiates the regime; throughout operation, the complete device-boundary energy balance remains applicable. At the complete device boundary η ≤ 1. The system remains within classical conservation constraints.

Energy accounting in VENDOR.Max is two-level: device-boundary accounting governs the complete system, and regime-level accounting describes how energy is redistributed across internal functional paths inside that boundary. Both descriptions are consistent with each other and with conservation of energy. See the dedicated question below for the full multi-level explanation.

Classification: open electrodynamic system  ·  regime-based power architecture  ·  controlled nonlinear discharge  ·  classical physics throughout
Why is the system described as two-contour when the patent has three transformer windings?

The architectural and patent descriptions refer to one physical system at two levels of granularity — both fully consistent with each other.

Architectural description (functional grouping): Circuit A performs regime formation; Circuit B performs power extraction. A BMS coordinates between them.

Patent description (ES2950176): three windings of transformer (5), each with its own resonant capacitor, forming three independent resonant circuits. The secondary and tertiary windings are functionally grouped under Circuit B because both extract from the same shared field and are managed by the same BMS.

The two descriptions are complementary views of the same hardware. The architectural view is suited to system-level explanation; the patent view is suited to claim-level disclosure.

How does the system prioritize regime stability over load delivery under varying conditions?

VENDOR.Max is designed around a hard priority hierarchy that protects the operating regime first and delivers surplus power to the load second. This is an architectural design principle, not a fault-mode behaviour.

Priority 1

Regime maintenance (secondary winding → storage capacitors C2.1–C2.3): the regime is the system’s operating state and must be preserved for the architecture to function at all.

Priority 2

Load delivery (tertiary winding → load): receives the surplus available after Priority 1 has been fully satisfied.

Under conditions where available power cannot satisfy both, the BMS automatically prioritizes Priority 1 and curtails load output. The patent describes the tertiary winding as the path through which surplus power is routed to the load. In other words, the load path receives available surplus after regime-maintenance requirements are satisfied.

How does VENDOR.Max differ from a battery storage system (BESS)?

VENDOR.Max is not a storage system. It is a regime-based electrodynamic power layer with no electrochemical storage and no charge/discharge cycle.

BESS stores electrical energy electrochemically and delivers it during discharge. Service life is typically 7–15 years before replacement at 70–80% residual capacity. BESS does not address grid connection queues or voltage instability at the source.

VENDOR.Max uses a regime-based electrodynamic architecture: no electrochemical cells, no charge/discharge cycling, no storage degradation curve, and no fuel logistics dependency. The two technologies serve different functions in an infrastructure power stack and are not direct substitutes.

What is the current development stage of VENDOR.Max?

VENDOR.Max is at TRL 5–6 — system-level validation in a controlled laboratory environment. The system is at a pre-commercial stage; no commercial deployment is currently in field.

Over 1,000 cumulative operational hours have been recorded under internal controlled testing (internal metric, not independently audited). The CE/UL certification pathway is defined, with target stage TRL 8. A first field deployment milestone is planned for Q3 2026 and remains contingent on successful completion of TRL 6 verification milestones. All performance figures cited on this site are design targets, not certified specifications.

What patents protect the VENDOR.Max architecture?

The VENDOR.Max architecture is protected by a multi-jurisdiction patent family covering the two-contour electrodynamic configuration:

  • ES2950176 — granted in Spain (OEPM), 14 March 2024
  • WO2024209235 — PCT publication, all national phases complete
  • EP23921569.2 — EU regional phase, examination in progress
  • CN202380015725.5 — China, examination in progress
  • IN202547010911 — India, examination in progress
  • USA — national phase, examination in progress
Is there a galvanic connection between Circuit A and Circuit B?

There is no galvanic connection between Circuit A (regime formation) and Circuit B (extraction). The only coupling between them is electromagnetic induction through the shared magnetic field of transformer (5), which is the same physical principle that operates in every conventional transformer.

The extraction efficiency is bounded by Faraday’s law of induction, with the standard transformer relationship:

ηextraction = Poutput,B / Pfield,A ≤ 1

The bound η ≤ 1 holds at the extraction interface and at the device boundary. This is consistent with classical electrodynamics throughout.

How does the system reconcile device-boundary efficiency η ≤ 1 with internal regime dynamics?

At the complete device boundary, steady-state averaged efficiency does not exceed unity: η ≤ 1. This is the global conservation statement and it holds at all times. What changes between descriptions is the level of accounting, not the underlying physics.

VENDOR.Max is not a monolithic black box with a single input and a single output. It is an architecture composed of internal functional paths — regime formation, feedback, load delivery — each with its own local energy account. Two consistent accounting levels apply simultaneously:

Level 1

Device-boundary level — the complete system as a black box. Conservation requires: Pin,boundary = Pload + Plosses + dE/dt. At this level η ≤ 1 for steady-state averaged power.

Level 2

Regime level — internal functional sub-blocks (Circuit A, feedback path, Circuit B). Energy is redistributed between paths within the boundary. Local ratios describe how energy moves between sub-blocks — they do not describe creation of energy.

A familiar analogy: a transformer’s secondary winding can deliver more current than its primary, while voltage drops in the same ratio. The local current ratio is greater than one, the local voltage ratio is less than one, and the device-boundary power balance remains bounded by η ≤ 1. Local ratios describe redistribution; the boundary describes conservation. The same two-level logic applies to VENDOR.Max, with the redistribution occurring across regime, feedback, and load paths rather than between primary and secondary windings.

The regime-level accounting framework, including the event-level bridge equation Eextract,event = Eload,event + Efb,event + Eloss,conv,event and its relation to averaged power Px,avg = Ex,event · f, is documented in full at the regime-level energy model article. The article shows how all internal accounts close back to the device-boundary balance under conservation of energy.

If there is no galvanic connection, what physically drives the electrons in Circuit B?

Electron motion in Circuit B is driven by the electromagnetic field in the shared transformer core, governed by Faraday’s law of induction. This is the same physical mechanism that operates in every conventional transformer — the difference in VENDOR.Max lies in how the field is shaped in time, not in the underlying physics.

Step 1

Circuit A drives the field. The controlled discharge regime in Circuit A produces a rapidly changing magnetic flux Φ in the core of transformer (5).

Step 2

The changing flux induces an EMF in each winding linked by the core, by Faraday’s law: ε = −dΦ/dt. No wire and no charge transfer between Circuit A and Circuit B is required.

Step 3

The induced EMF moves electrons in Circuit B. The secondary and tertiary windings carry currents proportional to that EMF and to their respective load impedances — the same principle that powers every transformer-fed appliance.

The field is the mediator, not the source. The energy carried by the core field is the energy that Circuit A puts into it, and Circuit A draws that energy across the device boundary according to Pin,boundary = Pload + Plosses + dE/dt. What the field does is mediate and structure energy transfer across functional paths inside the device. It does not create energy and does not act as an independent energy source.

What is specific to VENDOR.Max is the regime in which the field is formed: a controlled nonlinear resonant regime at megahertz scale. The physics of induction is the same as in any transformer; the temporal structure of the field is what makes the architecture distinctive. Full mechanism details: How It Works.

Three Entry Points · Choose Your Path

Ready to
Go Deeper?

Technical due diligence, investment evaluation, or pilot program engagement — each path is structured for a different type of access to the VENDOR architecture.

For: Engineers & Technical Due Diligence

Technical Evaluation


Infrastructure-level system evaluation methodology. Patent records. Endurance test data. Structured technical assessment framework and validation context. Controlled technical Q&A within current TRL-stage disclosure limits.

For: Investors & Strategic Partners

Investment Case


Infrastructure-scale market thesis. TRL roadmap to Series A. Deployment-focused positioning for telecom, AI/edge, and remote critical systems. Milestone-linked strategic access.

For: Pilot Partners & Infrastructure Integrators

Pilot Program


Controlled deployment pathway for telecom operators, infrastructure providers, and system integrators. Structured evaluation with defined technical success criteria.