Reference architecture
Six layers, and the six configurations institutions deploy them in. What we own, what we integrate, and where the boundary sits.
The layer that does the real work is the third one.
Most capability programs fail somewhere between the sensors and the analysts. The equipment works, the applications work, and nothing in between reconciles a decade of procurement into something an analyst can reason over or an inspector can audit.
The integration and normalization layer is where S32 Technologies earns its place. It carries adapters for named systems, a canonical model for signals, events, assets and evidence, and the provenance, custody and policy metadata that has to travel with all of it. Without that layer the rest is a collection of tools.
What we own, and what we integrate
Workforce and sustainment
Training, exercises, certification, support, local delivery and the transition path to independent operation.
Mission applications
Magen, Genesis, InterceptPlus, NetDefense and restricted modules where eligibility permits, all reading the same governed record.
Platform
Identity, entitlement, tenancy, governance, deployment, operations and the customer and staff experiences over all of it.
Integration and normalization
Adapters, normalization, tasking, health monitoring, replay, provenance, policy and audit. The layer that makes mixed equipment behave as one governed source.
Edge and transport
Rugged compute, storage, synchronisation, secure backhaul, and operation that survives intermittent or disconnected links.
Collection and monitoring
Receivers, antennas, direction finding, timing, fixed and mobile sites, and the legacy systems you already operate. We integrate these. We do not manufacture them.
S32 Technologies does not manufacture specializt RF receivers, antennas, direction-finding arrays, timing systems, vehicles or shelters. We own the software, integration, deployment, workflow, training and lifecycle layer, and we work with the equipment you have or the partner you choose.
Configurations institutions actually run
Central operations center
One primary site carrying the full capability, usually the first thing stood up and the reference for everything after it.
Regional mission node
A subordinate site with its own operating tempo, federating to the center without depending on it to function.
Mobile or temporary field kit
Deployable capability for a defined operation, synchronising back when a link exists and working when it does not.
Customer cloud or on-premises
Deployed into infrastructure you already run, in the jurisdiction you have chosen, with keys you hold.
Disconnected or air-gapped
No outbound path. The same capability as any other model, with updates by signed package and controlled media.
Coalition or federated
Sharing with partners under compartmentation, where what is shared is a policy decision, not an architectural accident.
Most national programs end up running several of these at once. The architecture is the same in each, which is what makes a regional node or a field kit an extension of the capability, not a second system to govern separately.