Admiral
Enforce
Admiral turns trailers, tractors, chassis, and containers into assets that verify whether access or movement is authorized, enforce that decision locally, and record what physically happened. Let's look at how it works, then discover all it can do.
Admiral decides what is allowed, enforces that decision on the asset itself, and keeps the record of what physically happened. Rules are evaluated onboard, so an asset keeps working through a dead zone, an unattended yard or a closed gate.
The asset checks tractor identity, location, time, operating plan and the authority behind the request before anything moves or opens.
Doors stay locked, parking brakes stay applied and the air line stays unavailable until those conditions are met.
Every authorization, seal and physical event is attributed to who did it, where and when, and travels with the asset.
The Hub provides the onboard intelligence for Admiral. Mounted on the asset, it understands where the asset is and what it is doing, applies authorization rules, and coordinates the Lock and Immobilizer.
Authorized users, or the systems they already use, tell Admiral what should be allowed. Rules can be created in advance, sent to the Hub and carried with the asset.
One brain, three jobs: verify the situation, enforce the authorization, and prove the outcome.
An electromechanical interior lock mounted inside a trailer or container door, where it cannot be accessed from outside. It secures the door, senses its physical state and provides a digitally attributable seal.
The Lock turns authorization into an automatic door workflow. It decides when access can begin, verifies what happens at the door, and secures it again when the workflow is complete.
Know the state. Know who changed it. Know where and when.
A pneumatic enforcement device installed in the trailer or tractor parking-brake line. Controlled by the Hub, it prevents the parking brakes from being released unless movement is authorized.
The Hub turns movement authorization into physical control of the brakes. The Immobilizer executes that decision.
No authorization, no release. A mechanical fact, not a deterrent.
A compact, badge-sized device mounted on the tractor that identifies it to any Admiral-equipped asset it approaches.
Before a trailer or chassis will release, its Hub checks the Fob's identity against an authorized list. Set only by the asset's owner.
One Fob per tractor. One authorized list per pickup, set by the owner and never by the driver.
A gladhand with integrated physical access control, designed for compliance and coupling workflows. It keeps the trailer or chassis air-line connection unavailable until Admiral determines that the required conditions have been met.
The Electronic Gladhand turns authorization into a physical coupling workflow: verify the tractor and operating conditions first, then make the air connection available.
The asset makes the air connection available only when the next step is authorized.
Admiral Resolve verifies the people and permissions behind freight decisions at the moment they are made. A company can be legitimate while the person using its name is not. A driver can be real while the instruction that sent them originated from someone who was never authorized. Resolve checks the individual request rather than assuming that a valid company, document or account makes the action legitimate.
For each pickup, access request, routing change or handoff, Resolve answers three questions:
Verify that the request came from the real person, equipment or system, not someone impersonating them.
Confirm that they are actually acting for the carrier, shipper, broker or other organization they claim to represent.
Verify that the identified party is authorized for this specific action, for this load, at this point in the operation.
The result travels with the operation. Downstream participants can see whether the authorization chain remains verified, and each approval or denial becomes part of the record.
When used with Admiral Enforce, that decision does not stop at a screen. Authorization propagates to the asset, where the Hub, Lock, Immobilizer or Electronic Gladhand can enforce the approved conditions physically.
Verify the request. Verify the permission. Carry the decision to the asset.
The Admiral Console is where you teach Admiral how your operation should run. Define what should be allowed, required or prevented, connect the information Admiral needs, and manage exceptions when the operating plan changes.
There are three ways to do it:
Whichever approach you use, the result is the same: the operating plan reaches the asset, where the Hub can evaluate it locally and the Lock, Immobilizer or Electronic Gladhand can enforce it physically.
The Console also lets authorized users see asset state, review physical events, manage exceptions and intervene when needed.
Admiral watches its own equipment as closely as it watches the asset. Every lock, unlock and release is measured, compared with the rest of the deployed fleet and with that device's own history, and used to predict mechanical failure before it happens.
Every activation is also a health check.
The Hub, Lock and Immobilizer work together on the trailer as one system for sensing, authorization and physical enforcement.
| Scenario | Admiral Solution |
|---|---|
| Trailer disconnects from its tractor | Doors lock, brakes engage |
| Unauthorized entry is attempted | Tamper and motion sensors trigger, alert sent |
| An authorized tractor connects | Doors unlock, brakes release |
| Trailer is moving with its doors unlocked | Alert sent, trailer doors lock automatically |
| Trailer is due for inspection | Lock the trailer down so only the maintenance team can move it |
| Driver resetting hours | Lock the doors and brakes automatically |
| Yard closed for the night | Automatically lock all trailer doors and brakes within the geofenced yard until next opening hours |
| Yard has a yard tractor | Allow all trailers within the geofenced yard to automatically unlock when connecting with the yard tractor |
| Trailer being pulled by a third party | Allow the third-party driver to unlock the brakes but not the doors |
Set the conditions once. The trailer manages its own access and movement from there.
The Hub and Electronic Gladhand work together on the chassis as one system for sensing, authorization and physical control of the air-line connection.
| Scenario | Admiral Solution |
|---|---|
| Driver requests empty chassis pickup | Server checks pool limits and grants access |
| Driver picking up the wrong chassis for return | Chassis denies hookup access |
| Empty chassis dropped | Lock automatically engages |
| Yard is unsecured or unmanned | Driver presents credentials; chassis unlocks |
Set the pickup conditions in advance. The chassis enforces them at hookup without daily intervention.
The container uses the same Admiral Hub and Lock as a trailer, adapted to manage container access, custody and handling events.
| Scenario | Admiral Solution |
|---|---|
| Container leaves the shipper | Doors lock and digital seal engages automatically; custody starts here |
| Container reaches its authorized destination | Access is enabled automatically under the delivery rules |
| Container loaded onto the wrong chassis | Pairing mismatch detected; Admiral-equipped chassis remains immobilized |
| Container lifted and set in a stack | Detects the lift and set-down and reports its estimated position in the stack |
| Digital seal is set or broken | Records who performed the action, where it occurred and when |
| Seal is broken outside the authorized workflow | Custody exception is recorded and the appropriate operations or inspection workflow can be triggered |
| Container arrives with its digital seal intact since a trusted origin | Authorized gate or enforcement systems can verify the uninterrupted seal history locally or remotely |
The container remembers its custody, verifies its pairing, knows how it was handled, and carries the evidence with it.
The Hub, Immobilizer and Fob work together on the tractor as one system for sensing, movement authorization and trusted vehicle identity.
| Scenario | Admiral Solution |
|---|---|
| Tractor parks | Hub automatically immobilizes it according to the operating rules |
| Authorized movement conditions are met | Hub releases the Immobilizer and the tractor can move without a separate unlock step |
| Someone attempts to move the tractor without authorization | Tractor remains immobilized and the attempted movement is recorded |
| Tractor approaches an Admiral-equipped trailer or chassis | Fob presents the tractor's identity so the other asset can verify whether the pairing or pickup is authorized |
The tractor carries a trusted identity to every Admiral trailer it approaches.
There has been a shortage of truck parking for years. Drivers routinely end up in unsecured lots, road shoulders, or gravel yards just to legally take required rest. There simply aren't enough safe spaces to go around.
An idle rig sitting unattended overnight is the easiest theft target there is, and independents rarely have the buffer to absorb a loss. A stolen tractor doesn't just cost money. It can end a one-truck business outright, mid-load, with no fleet safety net behind it.
Admiral protects the one asset an independent can't afford to lose, without adding a second job to the driver's day. The rig locks itself down every time it's parked. No separate step, no extra equipment to manage.
Cargo theft continues to rise in frequency and severity. For a fleet running dozens or hundreds of trailers, that risk isn't a one-off; it's a recurring exposure on every lane with drop-and-hook operations.
Reefer loads add a second exposure: high-value, temperature-controlled freight can be compromised even if the trailer itself never moves. An unauthorized door opening can create a cargo-integrity question that is costly to investigate and difficult to resolve after the fact.
Admiral turns trailer security from a per-incident insurance claim into a fleet-wide rule dispatch sets once and stops thinking about. Every trailer enforces the same rules, the same way, without a driver or dispatcher remembering to do anything.
Once a trailer leaves the lot, a lessor gives up much of the physical control it had at the yard. Pickup and return often depend on staffed locations, operating hours and manual handoffs, while unauthorized movement, delinquency and recovery become expensive exceptions to manage.
At the same time, the trailer itself is largely a commodity. To a renter comparing assets, one bare trailer can look much like another.
Admiral lets the trailer enforce who may access or move it, while making authorized pickup and return far more self-service.
Admiral turns the trailer from an asset that must be supervised at every handoff into one that can manage much of its own pickup, return and protection.
Authorize the customer, not the yard hours. The trailer can manage its own pickup, return and protection.
Drop and hook lets a carrier keep tractors moving by leaving trailers at customer and remote yards. But every unattended handoff creates another coordination point: the right tractor has to take the right trailer, at the right time, and only after the trailer is ready to move.
That gets harder as carriers use multiple yards, outside capacity and operations that run beyond staffed hours.
Admiral lets the trailer carry the pickup conditions with it and enforce them at the asset, so routine drop and hook can run without dispatch supervising each handoff.
A shared pool is designed so customers can take whichever available unit meets their needs. But that flexibility still has limits: a customer may be entitled to one asset class but not another, may have a maximum number of units outstanding, or may not have access to a premium pool.
Today, those limits are often enforced through yard processes, system checks and after-the-fact reconciliation rather than by the asset itself.
Admiral lets the pool operator extend customer entitlements to the physical assets. Drivers remain free to select any eligible unit, while the chassis or trailer prevents pickup when the transaction falls outside the customer's permitted use.
The pool system continues deciding what each customer is entitled to. Admiral makes those limits enforceable at the asset while preserving the flexibility that makes a pool useful.
The customer picks the unit. The asset knows whether they are entitled to take it.
Shippers increasingly want more than visibility for high-value, theft-sensitive or tightly controlled cargo. They want to know not only where the container is, but who can open it, whether it followed the authorized movement, and what physically happened along the way.
Ocean carriers already offer customers value-added services around visibility, monitoring and cargo protection. Admiral adds something new to that portfolio: physical control and verifiable execution at the container itself.
Admiral can turn an equipped container fleet into a differentiated security and control service that carriers can offer shipment by shipment.
You already sell visibility and protection. Now sell control of what can physically happen to the container.
Every container moving through a terminal creates physical events that matter beyond the terminal: when it arrived, what chassis it was paired with, where it was placed, when it was lifted again, and when custody changed.
Today, those facts can be spread across gate transactions, asset systems, driver records and the systems of other parties. The physical asset itself carries very little of that history forward.
Admiral lets containers and chassis recognize and record their own physical interchange events, creating information that can follow the asset across terminals, rail ramps, depots and drayage operations.
Admiral does not replace the TOS. It gives the terminal and the parties around it a physical source of truth generated by the assets themselves.
Underwriters can require good operating practices, but they often have limited evidence that those controls were actually in force on a specific trailer or load.
That matters most for theft-sensitive freight, higher cargo limits and other risks where the difference between an acceptable risk and a declined one may come down to how the load is physically controlled.
Admiral gives underwriting a way to specify how a risk is controlled, enforce it physically and verify it was followed.
Admiral can turn security and operating requirements into enforceable underwriting conditions, and provide evidence that those conditions were followed.
After a cargo loss, investigators often have to reconstruct what happened from system records, driver accounts, police reports and the records of multiple parties.
The critical questions are physical: Was the asset secured as required? Who was authorized to access or move it? Was that authorization actually used? When and where did custody or asset state change?
Admiral preserves a physical record of the controls, authorization and events surrounding the loss, giving claims teams evidence from the asset itself rather than relying only on accounts assembled afterward.
The same controls that help an underwriter decide which risks to accept before a shipment create the evidence needed to understand what happened when a loss occurs.
Strategic theft takes many forms: carrier impersonation, compromised accounts, fraudulent re-brokering, forged instructions and deceptive pickups. The tactics change, but they share a common exploit.
Somewhere between the original instruction and physical execution, authority passes through a person or system whose identity and right to act were never actually verified.
That gap can exist even when nearly everything else about the transaction is legitimate. Consider a load legitimately tendered by a shipper to a real broker. An attacker compromises or impersonates someone at that broker and tenders the load onward to a real carrier. The carrier is legitimate. Its driver is legitimate, works for that carrier and has genuinely been dispatched to collect the freight.
At the gate, almost every check can return yes:
The driver may be entirely innocent. Yet one unverified link remains in the authorization chain, and everything downstream depends on it.
Admiral Resolve makes that missing link visible. At each operational touchpoint, Resolve verifies not only the organization involved, but the identity of the person or system acting for it and whether that identity is authorized to perform the action. Each verified touch becomes part of the authorization chain carried forward with the operation.
The ship clerk can therefore see whether the authority behind the pickup remains verified from end to end, and whether any required link is not confirmed.
More importantly, the protection does not stop at the gate. Admiral propagates that authorization state to the asset itself. If the owner's rules require every handoff to be verified, one not confirmed link is enough for the trailer to refuse the operation.
The driver can be exactly who they claim to be and fully authorized by the real carrier. The trailer can still say no, because the authority reaching that carrier passed through an unverified link.
Driverless trucks have begun hauling freight on public highways, and they are built to be cautious. When the road ahead is blocked, a driverless truck stops. That is the right behavior for safety, and it hands thieves a new playbook.
Box the truck in with a few vehicles and it stops where the thieves choose, on a quiet stretch of highway with no driver aboard to resist or delay them. The remote operations center sees the stop and alerts the authorities, but on a rural interstate help can be many minutes away. The thieves only need the doors open before it arrives.
A driverless truck removes the driver. Admiral makes sure it doesn't remove the protection.
Admiral does not rely on a driver to protect the load. The trailer enforces the plan itself, wherever it stops.
Three parts, one platform. Seven pieces of equipment, four types of asset, eleven businesses built around them, all one connected system.
Bring us one lane, one asset type, or one operating rule. We'll configure it in Admiral and show how the asset would enforce it before anything is installed.
