SENSORLOGIX · FORWARD DEPLOYMENT
What runs forward, and what it runs on
A collector beside each sensor, and a forward node where the analysis has to keep going with no link. This is what each one is built from, what it runs, and roughly what it carries.
The forward node runs the whole DataLogiX platform with SensorLogiX, under the same rules as the rear. It installs from media and never calls home.
PDF · 7 pages · hardware, software, models, capacity and standards
THE TIERS
Three tiers, sized to where they go
A vehicle or a mast gets a collector. A ship, a base or a command post gets a forward node, and a larger ship or a headquarters gets two.
Edge collector
WHERE
Vehicles, drone ground stations, masts and aircraft.
WHAT IT DOES
Captures and buffers sensor data through a lost link, with optional detection on the box. It doesn’t run analyses.
HARDWARE
A small sealed rugged box with an NVIDIA Jetson Thor module.
LANGUAGE MODEL
gpt-oss-20b, optional
POWER
About 220 W
Forward node
WHERE
Ships, forward bases and incident command posts.
WHAT IT DOES
The whole platform for one site, fully disconnected for days.
HARDWARE
One short-depth rugged 2U server with an NVIDIA RTX PRO 6000 Blackwell Max-Q, 96 GB.
LANGUAGE MODEL
gpt-oss-120b
POWER
About 1.0–1.2 kW
Forward node, large
WHERE
Larger ships and headquarters elements.
WHAT IT DOES
The whole platform with more video streams, longer retention and failover.
HARDWARE
Two rugged 2U servers, each with one 94–96 GB GPU: NVIDIA H100 NVL or RTX PRO 6000.
LANGUAGE MODEL
gpt-oss-120b
POWER
About 2.5–3 kW
- Sync. Collectors upload to a forward node or the rear. Forward nodes sync both ways with the rear over a network, on removable media or through your cross-domain device.
HARDWARE
The hardware, tier by tier
The chassis and its GPU slots are the parts to check first: they decide what fits. The PDF lists a minimum and a recommended build for each tier.
Why two nodes: one 94–96 GB GPU already runs gpt-oss-120b. The second node adds failover, keeps video work apart from the model and adds capacity.
See the GPUs we build withSee less
WHAT RUNS WHERE
What each tier does, and what waits
Forward, the checks are the cloud’s: the SQL guard, number bindings, recomputation, the verifier, traceability, markings and dissemination run exactly as they do in the rear. A capability that can’t meet its standard on local hardware is switched off, never run in a weaker form.
Connected extras, such as Microsoft 365, Purview, Google Drive and hosted models, run on a forward node only when a link is up and policy allows them.
In FIPS mode, features whose algorithms sit outside FIPS 140-3 are off on every tier: post-quantum signatures, OpenPGP, C2PA content credentials and X25519/Ed25519.
SOFTWARE
The same software everywhere it runs
The forward node runs the same signed build as the rear. It needs no network to install, run or update.
Models
Models ship inside the bundle and are checked by hash before they load. All are open-weight, under permissive licenses such as Apache-2.0. The checker is never from the writer’s model family.
See the DataLogiX services on the nodeSee less
- Platform. The DataLogiX API, web app and workflow engine, webhooks and the relay gateway.
- Documents. Conversion of Office, PDF and older formats; OCR; Word, PDF, PowerPoint and Excel reports; citation styles; XBRL and C-CDA readers; malware scanning with offline signature updates.
- Security. OpenTDF key access, a local prompt screener that fails closed, and a code sandbox with no network.
- Ingest. The relay, which on a collector captures video, splits out KLV metadata and stores and forwards; SFTP drop; watched folders; connectors.
APPROXIMATE CAPACITY
Roughly what each tier carries
All figures here are approximate and meant for sizing. Real numbers depend on the hardware, the questions, the data and how busy the site is, so we size each build with you.
Search, maps, review and dashboards don’t use the GPU; the language model sets the pace. A report takes about 30,000–60,000 generated tokens across the planner, writer and checkers.
Video and tracks
Detections arrive within about 2 minutes of each 30-second video segment closing.
See model speed, documents and storageSee less
Model speed
Documents and data
Storage
Running it
- Install. From media, with no network, in about 30 minutes.
- Disconnected. 72 hours and more with no link at all.
- Cold start. About 5–10 minutes from power to serving, plus the HSM or operator unseal.
- Zeroize. Keys destroyed in seconds, leaving the data unreadable; then the disks are wiped.
- Updates. Signed delta bundles on media, checked before they install, with rollback.
- Sync with the rear. Resumable, by priority and within a bandwidth cap. Every record is checked against markings and release rules on both sides.
STANDARDS
Standards the kit is built to
We don’t certify hardware. The kit is specified to these standards, the hardware vendor’s certification of the chosen model qualifies it, and accreditation stays with you.
SECURITY ON THE BOX
Locked down before it ships
The node keeps the rear’s controls with no link at all, and it’s built to be inspected.
- Encrypted at rest. Self-encrypting drives under LUKS, per-tenant data keys wrapped by the HSM, and sealed columns encrypted just as in the cloud.
- Smart-card sign-in. CAC/PIV, with no shared accounts.
- Audited. Every action is recorded as it is in the cloud, and the audit trail syncs to the rear.
- No outbound network. Egress is denied by default. Connected extras run only by policy, and every attempt to reach out is recorded.
- Signed where it’s made. Reports and traces are signed with the node’s own key and timestamped from GPS time. The rear checks each signature on sync.
- Evidence for your assessor. Software bills of materials, scan results, STIG checklist results and a control mapping come with every build.
Tell us where it has to run
We’ll size the kit with you, from the sensors and links you have to the people who will use it.