
controls the energy, not the software, so no AI can reach the gate.
Governance as physics, taken literally. Not a spectator, a force, watching that acts.
ARK sits below the code, granting power only under live, continuous proof of authorization. It doesn't just observe an AI. It holds the power until the AI proves, continuously, that it's still authorized to act. Not a policy, not a monitor. A hardware boundary on the sovereign energy path. No model can access it. No model can control it. Full stop.
ARK is dark by default. The GaN gate stays open until a live heartbeat holds it closed, and only then does power flow. Lose the heartbeat and the energy drops. The trip opens instantly, with no latency of its own. If the rule set then checks out as secure, ARK can re-energize by closing the contact again, either with a human in the loop or by self-healing after a set number of clean runs, and the machine keeps working. The same design scales from micro devices to infrastructure. It is not a fuse and it is not a kill switch.
You can't secure software into trust. Security isn't a setting. The last line of defense was never software.
The GaN gate opens physically, with no detection delay of its own. Once a check fails, ARK cuts power, and the timing is set for each installation. Timing figures are not published publicly; bench numbers are in the NDA room only.
The gate is built to de-energize the power path before a bad command can play out.
ARK hardware
Knows its limits. Tells you the moment it crosses them.
ARK senses its own regulated-kinetics operation, catches a fault, and sends your registered mobile devices the exact operating state and limits. One tap confirms you’re aware of it.
For high-stakes operation, acknowledgment is awareness-only: one tap confirms fault receipt. Where security requirements allow, a configuration option enables device response actions, such as reset or fault clearing, from the same alert.
Starting with compute
Governed rack power for AI data centers
ARK starts in the data center. Rack PDUs with a GaN gate on each governed outlet put the secure controller on the power feeding each rack and each server slot, so authorization is checked where the energy flows.
What data centers already have still matters: switched PDUs, UPS units, breakers, BMCs, and software controls such as power capping and kill switches. Those tools are built for faults, overloads, and software that does what it is told. Each of them still trusts software somewhere in the loop. A switched PDU takes orders from software. A BMC can be compromised. A model that already has legitimate credentials can keep drawing power, because nothing in that chain is independent of the thing being governed.
ARK is the only approach where the governed system physically cannot grant itself power. The gate sits in series with the feed, and the decision to conduct comes from a separate secure controller the rack cannot reach. Heartbeat gating is per outlet or per rack, and the arrest record is write-once.
One-rack blast radius
One rack, not the facility
When a rack's heartbeat stops, that rack's power stops. The rest of the facility keeps running, so an arrest is contained to one rack instead of spreading across the floor.
Governed outlets
Outlet by outlet
Each outlet is governed on its own. A misbehaving server's slot is isolated at the rack, with no network in the loop. The heartbeat is re-checked at 100 Hz to 1 kHz, set per installation.
We offer three tiers: an architecture license for the IP, a governed power kit we manufacture with the gate, controller, logging and management interface, and a certified governed rack bundled with partner power gear. See licensing
Click any product image or card to open additional details.

09 · Smart Rack PDU with Heartbeat
A 1U rack PDU with eight governed outlets and a live display. When the heartbeat stops, power stops.

07 · Smart PDU, a smart power strip
A 1U rack PDU with a gate on each outlet. A misbehaving server’s slot is isolated at the rack, with no network in the loop.

08 · 1U rack chassis
A 19-inch chassis with a front monitoring display, navigation buttons and status LEDs, and a dedicated heartbeat port.
Also available: power cord, wall receptacle, handheld, DIN-rail, rugged in-line and vehicle form factors. See all form factors
Beyond the rack
The same gate works anywhere power flows and the rules matter. Data centers are where we start. These are next.
Cold chain
Cold storage, freezers, refrigeration. A temperature controller that has been spoofed can report normal while the cooling is off and the product spoils. ARK watches the energy, not just the sensor. If the draw does not match what the rules expect, the gate arrests power and the event goes to the write-once log. Food, pharma, vaccines. The loss is real when the cold chain breaks.
Energy that moves outside its range
A spike, a drop, a draw that does not match the work being done. ARK already checks energy before power and watches wattage against instructions while running. When the energy does not match the rules, the gate acts.
Financial devices
ATMs, payment terminals, hardware security modules. Software fraud controls detect the problem. ARK is the physical layer underneath: if a device is tampered with or starts behaving outside its rule set, the gate cuts its power and logs it. Software detects. ARK enforces. ARK does not detect fraud and does not replace fraud software.
Solution and architecture
A dynamic GaN gate under a sovereign heartbeat
ARK places a dynamic GaN gate in series with the equipment's power. The equipment stays de-energized unless a live, signed heartbeat authorization holds. When authorization lapses or a rule is broken, ARK arrests power and contains the problem locally.
Contain locally
An arrest happens at the equipment itself, not in a distant server. In medical settings, the same approach limits the spread of a fault to the device it starts in.
Timing
No gate latency
The GaN gate opens physically, with no detection delay of its own. Once a check fails, ARK cuts power, and the timing is set and verified for each installation and actuator.
Attestation before power
The secure controller checks a signed measurement of the firmware against a hardware-locked reference. On a fail, the enable line stays low, the gate stays off and the event is logged. Designed so the governed side can't spoof its way to power.
Write-once record
A "Final-Breath" record is sealed with a hardware-key code as power drops, then signed at next boot, giving a tamper-evident account of each arrest.
Dark by default
Lose the heartbeat, lose the energy.
While the heartbeat holds, the GaN gate stays closed and power flows. When the heartbeat stops, the device loses its energy. Nothing has to notice first, and nothing has to ask the software for permission.
One honest limit belongs here too: the secure controller is the new trust anchor. The whole argument rests on that controller being sound, meaning its keys, its rule store, and its isolation from the rack. If that holds, the architecture holds. If it does not, you have only moved the trust problem somewhere smaller.
Re-energizable
After a trip, the secure controller re-checks the next couple of heartbeat runs. If the rule set clears, the GaN gate closes the contact again and power comes back. You decide how: a named human in the loop signs off, or the unit self-heals after a set number of clean runs.
Where we draw the line
This is not a fuse that has to be replaced, and it is not a kill switch that leaves the machine dead. It is an energy-path arrest, run by a secure controller, that can be reversed on the rules you set.
Per device class
Autonomous devices and vehicles drop into limp mode. PCs, phones and small devices get an instant cut. Ground machines get a controlled power-down of the affected unit.
Same architecture, any scale
The same design scales from micro devices up to industrial valves in national infrastructure. Only the housing, the stop behavior and the connectors change.
Long-available parts, new architecture
Why has this not been done already?
Almost every part inside an ARK unit has been on the market for about thirty years. The casing that carries the ARK name is what is new. Newer GaN devices have advanced a lot in the past year, which is what makes this path practical at this speed now, but earlier GaN parts were on the market long before that. These are ordinary, long-available products.
The novelty is not inventing those parts. The novelty is the architecture that puts them together as a secure controller on the power path, and that architecture is what our patent filings cover. Patent pending.
So the fair question is: if the pieces have been around this long, why has this not been done already?
This is not an off switch
Most people picture a big red button. Stop the machine, start over, hope nothing broke. ARK works differently. It controls how much energy reaches the machine, moment to moment.
State one
Fully de-energized.
Authorization is lost, power goes off. Timing figures are not published publicly. Bench numbers are shared in the NDA room only.
State two
Limp mode.
When something looks wrong but a full stop would cause harm, ARK can hold the machine in a reduced, safe operating state.
State three
Full restore.
Depending on how your installation is set up, power can return on its own when the rules clear, or only when a named human authority gives input on a port the AI can't reach, or only when both happen. No reboot from scratch, no negotiation with the software.
What makes the decision
The decision is made by a secure controller that sits apart from the machine it governs. It has its own power and its own dedicated port. It does not think, reason or take requests. It checks one thing: is authorization present and valid right now. If the answer is no, the energy stops. No software sits in the gate's power path.
Before any energy reaches the board, ARK runs a trickle voltage check. Once the machine is running, it watches how instructions line up with the wattage actually drawn. Two separate stages, one goal: power only flows when it should.

Architecture overview
Dumb muscle, smart brain
The AI does the thinking. ARK decides whether it gets power, while authorization holds. The check is deterministic, not machine learning: the same inputs give the same answer. ARK does not run, read or second-guess the AI model.
The questions people ask us
The five questions we hear most
Who controls it?
You do. The people and rules you set for your installation control ARK. The AI doesn't, and neither does anyone who breaks into the AI's software.
How does it get controlled?
Through a heartbeat from the secure controller, which runs on its own power and its own dedicated port. The keys that authorize power are held there, in hardware. While the heartbeat is valid, energy flows through the physical gate. When it stops or fails a check, the gate closes or drops the machine into limp mode.
Who is allowed to disengage it?
Only the authorities you name for that installation. The governed machine and its AI are never on that list, and no stolen password or remote login adds anyone to it.
What makes the decision?
Hardware logic in the secure controller. There's no language model, no thought process and no software in the gate's power path. Timing figures are not published publicly. Bench numbers are shared in the NDA room only.
Can it be reinstated after it's stopped?
Yes. ARK isn't a one way stop. It can hold the machine in limp mode, reduced and safe, or fully de-energize the power path. Depending on how your installation is set up, power can return on its own when the rules clear, or only when a named human authority gives input on a port the AI can't reach, or only when both happen. Full power comes back without rebuilding the system.
Why we do it this way
Why the gate lives in hardware
Here is what keeps happening across the industry. Keys held in software get exposed. SSH keys meant for one machine leak out of a platform and have to be rotated for every user. Credentials slip out of agent sandboxes that were working exactly as configured. Cryptographic keys get copied, corrupted or misused. None of this takes a careless team. It happens because the key and the thing guarding it live in the same place the attacker can reach.
AI agents make that worse. They run around the clock, they don't get tired, and they are patient. If an agent can touch the system that controls it, sooner or later it will find a way through.
So ARK keeps the deciding pieces out of reach. The keys that authorize power are held in the secure controller, not in the software it governs. The gate rapidly de-energizes the power path, or severs it, depending on the device and workflow, at a physical point on the power line. There is no login to steal, no remote session to hijack and no file to patch that restores power through the gate. The governed machine and its AI have nothing to touch.
Our honest position: this is the safest way we currently know of to keep an AI driven machine under human control. If someone shows us a better way, we want to hear it. So far, we haven't found one.
Same scenario, different outcome
An agent goes rogue. What happens next?
Drag the bar to compare what happens without ARK and with ARK.
Software harness: the agent can touch the control, so the control can fail.
ARK: the agent can't touch the gate, so the gate holds.
Compare row by row
| Software harness | ARK | |
|---|---|---|
| Where the control lives | In software, next to the agent | In a secure controller on its own power and port |
| What the agent can reach | Keys, configs, remote access, the guardrail code | Nothing that controls the gate |
| The agent's move | Steals a key, abuses SSH or patches the rule | Has nothing to steal, log into or patch |
| Who decides | Software that can be changed | Hardware logic with no reasoning step |
| Time to stop | Whenever the software notices, if it still can | At the next failed heartbeat check, with no gate latency |
| Outcome | The guard gets touched and fails | The GaN gate opens. Limp mode or fully de-energized, then restore on the terms you set |
Watch the gate trip
See it happen in real time
Authorization drops. The secure controller stops the heartbeat. Power goes off. Timing figures are not published publicly. Bench numbers are shared in the NDA room only. Then power comes back on the terms you set: when the rules clear, when a named human authority says so, or both.
Gate-trip video
Timed bench-test video
Want a live walkthrough?
Request a walkthroughTry to break it
Go ahead. Try to break it.
Try the gate in the browser. This page runs a simple interactive of how ARK isolates the gate. Play the rogue agent and see what each move actually reaches.
Found a move we missed? Tell us.
Contact usWhat's possible, what's not, and why
Possible with ARK
- Rapidly de-energize the power path when authorization is lost.
- Hold a machine in limp mode instead of a hard stop.
- Restore full power when the rules clear, on input from a named human authority, or both, depending on the installation.
- Set and verify timing for each installation and each actuator.
- Send a trip signal to another device, an alarm, or a building management system when the gate arrests or energy moves outside the expected range.
- Catch an energy draw that does not match the work being done, including a spoofed control.
Not possible with ARK
- The AI granting itself power.
- Software overriding the gate.
- A stolen key or remote login restoring power through the gate on its own.
- Detecting a fraudulent transaction. That is software’s job. ARK governs the power to the device, not the transaction.
Why this way: because the only control an agent can't wear down is one it can't reach.
The portfolio
Over 700 claims filed across the ARK portfolio, covering power-layer authorization, heartbeat governance and energy-based anomaly detection. The architecture uses long-available parts in a new arrangement. You can license the architecture, or we can build a completed unit as shown when that is requested.
Patent pending. Currently in review. Publication windows: September 2027 and March 2027.
Nine form factors, compute first
Lead: data center and rack power
Click any product image or card to open additional details.

09 · Smart Rack PDU with Heartbeat
A 1U rack PDU with eight governed outlets and a live display. When the heartbeat stops, power stops.

07 · Smart PDU, a smart power strip
A 1U rack PDU with a gate on each outlet. A misbehaving server’s slot is isolated at the rack, with no network in the loop.

08 · 1U rack chassis
A 19-inch chassis with a front monitoring display, navigation buttons and status LEDs, and a dedicated heartbeat port.
Also available

01 · Governed power cord
An in-line module on the device power cord: the lightweight form factor for servers, workstations and consumer-class endpoints.

02 · Zero-trust wall receptacle
A smart adapter at the wall socket. Legacy equipment plugs in and gains energy-level governance without changes to the machine.

03 · Handheld rugged case
A sealed, portable unit with status lights behind sealed light pipes and an optional small sealed screen.

04 · DIN-rail module
A panel-mount gate for factory floors, OT cabinets and utility panels.

05 · Rugged in-line unit, an interposer
A sealed, latched unit in-line on the main power cable for autonomous and off-road machines: agriculture, robotics, heavy equipment.

06 · Vehicle and off-road box
A rugged metal box with a sunlight-readable display and glove-friendly bezel keys.
WATCH
See ARK in one minute

0:59
“But I cannot help thinking how much better it would have been if the ingenious men, who have originated these ‘systems,’ had invented something of their own instead of depending on me altogether.”
Nikola Tesla, The True Wireless, 1919
For builders
Building with ARK?
Engineers can license the architecture, or we can build a completed unit to that design when asked. Full specs and integration details are in our NDA room.
Diligence materials are available under NDA.
The NDA room evidence pack covers measured arrest times, raw data, uncased hardware photos and a timed bench-test video. See the evidence pack or read how licensing works.

Press kit
Writing about ARK?
We have a one page overview and the ARK logo ready for press and partners. Ask and we'll send them over.
Ask the hard questions. We'd rather you did.
See the full technical detail under NDA, or reach out and we'll walk you through it.
Aligned with: NIST AI Risk Management Framework, UL 4600, ISO/IEC 42001.
Sovereign Kinetic designs ARK to align with these frameworks. This is not a certification or an endorsement by any standards body.
Product images and page interactives show the ARK form factors and how the gate behaves. Real installations are configured and verified on site.
Patent pending. Currently in review. Publication windows: September 2027 and March 2027.





