Defense floors and sustainment depots run on isolated networks. Your operational view has to live there too.
Precision machining beside test rigs, ground-support equipment, and platform maintenance depots — mixed legacy and modern controllers, often on air-gapped or isolated OT networks. Elpis collects from all of it over native protocols, normalizes every signal to one vocabulary, and runs offline-first with no phone-home — without replacing a single machine. Operating across India and the Middle East. Deployed in defense and space-agency programs.
Live integrations: FOCAS2 · MTConnect · Brother HTTP · Modbus TCP · OPC UA Client · Siemens S7. FANUC MT-LINKi REST on the roadmap.
Isolated by design. Still expected to be visible.
Defense work spans two worlds that share a constraint. On the manufacturing side: precision component machining, test rigs, and ground-support equipment, on a mix of legacy and modern controllers. On the sustainment side: vehicle and platform maintenance depots keeping fielded equipment serviceable for years past its original interfaces. The constraint both share is the network. These are security-sensitive environments — OT networks are routinely air-gapped or otherwise isolated, and any tool that needs to phone home, license against a cloud, or open an outbound path is a non-starter before the first conversation.
So the data stays trapped on the floor. A depot learns a hydraulic system is degrading from a failed acceptance test, not from a trend. A rotating assembly on a test rig develops a bearing fault that nobody sees until it is loud. And every change to how the floor is monitored — every threshold, every added sensor — lives in someone's memory or a local spreadsheet, with no defensible record of who changed what and when. In an environment where traceability and chain of custody are the whole point, an unauditable monitoring layer is its own liability.
Replacing the controllers isn't the answer — they are validated for what they run, fielded for the long haul, and isolated for good reason. What needs to modernize is the data layer, inside the isolation boundary. The defense operations that get there put one protocol-agnostic runtime in front of every controller, normalize every signal at the edge, instrument the consequence-heavy hydraulic and rotating equipment, keep every reading and every config change on a tamper-evident record — and never ask the network to reach the internet to do it.
"In an environment where traceability is the whole point, an unauditable monitoring layer is its own liability."
The data layer modernizes — inside the isolation boundary.
The data layer modernizes — inside the isolation boundary.
The outcomes a defense floor reaches for.
Built for floors that can't reach the internet — and shouldn't have to.
Elpis is deployed across defense manufacturing and sustainment operations — isolated floors with consequence-heavy hydraulic and rotating equipment. Operating across India and the Middle East. Deployed in defense and space-agency programs. The platform runs offline-first: the license validates locally with no phone-home, and an isolated-VLAN or air-gapped install behaves exactly as an internet-connected one. Per-route store-and-forward is built to preserve every reading through a network or broker drop — queuing locally and replaying in source order on reconnect. Each gateway carries its own identity, and every configuration change is captured in a hash-chained, tamper-evident audit trail.
Full operational trust posture → /security · Anonymized deployment patterns → /customers
What defense teams ask first.
Does this run fully offline, on an air-gapped network?
Yes. Elpis is offline-first by design. The license validates locally — there is no phone-home, no cloud dependency, and no outbound path required to operate. Installing on an isolated VLAN or a fully air-gapped network behaves exactly the same as an internet-connected one; the network isolation is something we install inside, not something we ask you to relax.
Which controllers and equipment can you actually collect from?
FANUC over FOCAS2, Siemens controllers over S7, older machines and ground-support equipment fronted by a PLC over Modbus TCP, plus MTConnect, Brother HTTP, and OPC UA Client where it's exposed — all shipping today. FANUC MT-LINKi REST integration is on the roadmap. For hydraulic, fluid, and rotating equipment, E-IDOS and VAS read condition directly. Bring the controller and equipment list to the scoping conversation and we confirm the collection path per asset.
Can you monitor our hydraulic and fluid systems and rotating equipment for early failure?
Yes — that's what E-IDOS and VAS are for. E-IDOS reads oil and fluid health (particle contamination, water saturation) on hydraulic and fluid systems; VAS reads vibration signatures on rotating equipment. They give early warning when a signature crosses a threshold your maintenance team defines — a better trigger than a calendar, not a guarantee against every failure. (E-IDOS runs standalone today; streaming into EREMOS V2 is on the roadmap. mDAQ runs VAS.)
How is our change history protected?
Each gateway carries its own per-gateway identity, and every configuration change is captured in a hash-chained, tamper-evident audit trail. The intent is a defensible record of who changed what and when — supporting the traceability and chain-of-custody expectations these environments carry. → /security
Does this replace our existing control system or SCADA?
No. Elpis sits beside them. EdgeConnect reads each controller as a read-only client — it never changes control logic, and no machine comes offline to connect it. Your control system and SCADA keep operator HMIs and control; Elpis modernizes the data layer beside them. → /architecture
Looking for the same thing from another angle?
Bring us your floor — even the part that can't reach the internet.
A controller and equipment list, the hydraulic and rotating equipment that worries you, and your network constraints — that's enough to scope an architecture review. We design for your isolation boundary, not around it.