GlīderM
Driver-operated · diesel
Glīd's commercially deployable diesel baseline. A crewed cab, dual-mode across road and standard-gauge rail. EZRA-1SIX routes, prices, and clears every one of its moves before the wheels turn.
EZRA-1SIX Logistics Orchestration Platform
The decision layer for multimodal freight
Meet the new software brain powering your fleet.
EZRA-1SIX decides your next move across road\\rail, whether you’re moving commercial freight or mission-critical defense cargo.
It routes only over rail you hold the rights to run, prices every lane the same way every time, and clears every pre-dispatch gate before anything moves. One system from quote to cleared dispatch, audited end-to-end. For civilian logistics, EZRA-1SIX turns fragmented freight decisions into one controlled operating layer. For defense, it adds the rigor required for restricted routes, mission constraints, authorization, and readiness.
1 price
Per lane — the same figure every time, traceable to the contract line
1 : 1
One database per customer, never shared, never pooled
6
Cost objectives every routed mile is optimized against, not one heuristic
48
Gates are evaluated on every dispatch
Road-to-rail, synchronized
One decision layer.
Two Glīd vehicle classes.
Glīd’s patented dual-mode vehicles move freight across road and standard-gauge rail. This means fewer machines, fewer people, fewer transfer points to complete your first-mile moves. EZRA-1SIX is the layer that commands them, at the control depth each one supports: whether a driver is at the wheel of a GlīderM or a Rāden is running itself, the routing, pricing, and clearance engine is the same.
Rāden
Autonomous · supervised
Hybrid-electric, autonomous capability for defense and contested logistics. GPS-denied, zero-crew, low-infrastructure. EZRA-1SIX is in command, from a supervised-autonomy console down to a confidence-gated E-STOP.
Inside the software
Your new logistics
command center.
Road to rail to road
One shipment, one plan. The built-in map draws the road legs, the rail legs, and shows the transition points between them. Each segment is timed and attributed. You can see at a glance where the vehicle leaves the highway for the rail and where it returns.
The go\\no-go
Stage a vehicle and the route comes back segment by segment (road, transition, rail). Each rail leg contains a rights verdict and the railroad contact to resolve it. Choose the objective, from fastest to max rail. And every pre-dispatch gate — authority, insurance, permits, documents, autonomy — must clear before the Dispatch button will fire.
The fleet, one screen
The whole road-to-rail fleet at a glance (driver-operated GlīderM and autonomous Rāden alike) with each streaming position, link, and fault state, one click from its command console.
Command Console
The console adapts to the vehicle class. A crewed GlīderM surfaces what a driver and a dispatcher actually act on, for example ground speed and heading, fuel and DEF, starting-battery health, MGRS position, hours of service, powertrain and CAN faults, and every camera on the unit, streamed live from the telematics provider. An autonomous Rāden runs the same stack and extends it into supervised autonomy, such as perception, confidence-gated motion, and an armed E-STOP.
The platform
Deterministic and defensible decision-making.
Everyone else shows you where your freight is. Their AI “acts” by cleaning up an exception after the fact. EZRA-1SIX makes decisions before the vehicle moves: with the next move already priced, rights-cleared, and compliance-checked, gated to a hard go\\no-go.
01
Route
A rights-aware engine
The routing engine treats un-permissioned rail as infeasible, a hard gate without a cost penalty. It optimizes only over track you legally hold rights to run. Incumbents structurally cannot copy this: they hold no rights.
02
Price
Deterministic quotes
Versioned rate cards feed a pure, auditable price calculator. Each lane returns the same number every time, traceable line-by-line back to the contract. No screen ever invents a figure.
03
Clearance
No vehicle moves uncleared
Before a vehicle is dispatched, every pre-departure gate runs live. Carrier authority, insurance, hazmat, vehicle permits, and rail rights, and more generate a verdict: Pass, Warn, or an unfaked Unknown. A gate that can't clear blocks the move.
04
Command
One command surface, multiple vehicle classes
One console commands the whole fleet at the depth each vehicle supports. A driver-operated GlīderM runs on dispatch, live telemetry, and clearance status; an autonomous Rāden extends into the supervised-autonomy console. This includes perception, confidence-gated motion, and a hardware-honest E-STOP. One decision layer, multiple vehicles.
05
Prove
Isolation and audit you can defend
A separate database per customer and a tamper-evident audit chain pinpoints any altered record. The control model is built to the dual gate: SOC 2 and CMMC, with an audit path underway. Your full operational record exports in open formats on demand. No lock-in.
Contested logistics
Draw the fence.
The engine will not cross it.
On contested ground the binding constraint is not cost or time; it is where a vehicle must not go. No-Go Zones is the app surface where a watch officer draws that ground, publishes it as a signed threat picture, and makes it the thing every routed mile is answered against. Keep-out is not advice the router weighs against fuel. It is a hard gate.
One area of operations, mid-authoring. A keep-out polygon and a standoff swept along a line, each carrying its threat category, source grading, and enforced distance, over an MGRS grid beside the published picture’s chain of custody. And the module blocking its own Publish button, naming the keep-in corridor that would otherwise fail the engine closed across the whole theater.
01
Author
Draw the ground you will not cross
Picture keep-out polygons, standoff buffers swept along a line, and keep-in corridors. The map features a named area of operations. Each zone carries what the threat actually is: indirect fire, direct fire, an IED belt, a minefield, unexploded ordnance, a forward-line standoff, or a political closure. The category pre-fills a default standoff; the distance the watch officer accepts is the only number ever enforced. The label carries no math.
02
Publish
Drawing a fence does not raise it
A drawn zone changes nothing until the theater is fused and published as a signed threat picture. This picture is hashed, key-signed, version-stamped, and carries its own validity window. The routing engine consumes that picture, not the raw drawings. Publish an empty theater and the system refuses rather than signing it: an all-clear nobody authored is not an all-clear.
03
Enforce
No picture, no route
Every route request is answered against the current signed picture. If that picture is missing, unsigned, stale, or cannot be read, the engine returns no route at all. None of those refusals can be overridden. An engine that cannot vouch for an answer does not offer one.
04
Hold
A refusal that is a decision
When every road-to-rail transition point on a corridor stands inside a no-go zone, the engine does not quietly hand back a road-only route. It holds, declining to move at all. Because there is no rail refuge anywhere on that corridor. That is the one refusal a commander can override, and only with an audited grant, minted against the exact route it was issued for.
What it deliberately will not do
Every zone records how good the reporting behind it is (unevaluated, possible, probable, confirmed). That grading is provenance: it is displayed, signed into the picture, and audited. It never softens a fence. A possible threat and a confirmed one hold a vehicle off by exactly the same distance, because the alternative is a system that quietly shaves a standoff on the strength of a label. Confidence tells you how much to trust the report. It is never allowed to move the line.
Commercial & defense, one codebase
Built for defense-grade security from day one.
Classification markers travel end-to-end. Every tenant runs in its own isolated store, physically separated from commercial workloads, never pooled. The same platform can support both commercial shipping and defense missions, with a separate, isolated defense instance deployed on a secure network when required—preserving mission separation while maintaining a tamper-evident audit trail and a control model engineered to satisfy both SOC 2 and CMMC requirements.
EZRA-1SIX
The quote, the clearance, and the vehicle.
in one place
700+ automated tests · Isolated database per customer · Pre-dispatch clearance gates · Built to the SOC 2 & CMMC control set
© Glīd Technologies Corporation. Screenshots depict demo/simulation telemetry — not a live vehicle feed.