Capabilities

Deep in a few places,
rather than thin across many.

A short list. Everything on it is something the people doing it have done before — usually in an environment where getting permission was harder than building the thing.

The Intersection

Most of our clients are trying to do something their commercial peers already take for granted: connect design to manufacturing to sustainment and get a digital thread running end to end. The obstacle is rarely the technology. It is that the data is regulated — CUI, export-controlled, and more sensitive categories still — and most straightforward paths to that outcome turn out to be either not permitted or not accreditable.

The firms that understand a factory floor generally do not do accreditation. The firms that do accreditation have generally never touched a PLC. We work in the intersection: industrial IoT and OT, cloud architecture, and cyber authorization, in industries where all three constraints apply at the same time. Very few firms sit there, which is most of why we are busy.

The intersection of industrial IoT and OT, cloud architecture, and cyber authorization Three overlapping domains of expertise: industrial IoT and OT; cloud architecture; and cyber and authorization. Each is a mature field with many capable vendors. The region where all three overlap, highlighted, is where Stigian works. The entire diagram sits inside a boundary labelled regulated data environments, indicating that every part of the work is constrained by regulation. Regulated data environments Industrial IoT / OT Cloud Cyber & auth

Each domain is mature and well served on its own. The overlap is not, and regulated industries are where the overlap is mandatory rather than optional.

Cloud Authorization & Compliance Strategy

Getting sensitive and controlled data into commercial cloud, legitimately. We work the approval pathway itself — RMF packages, ATO strategy, technical authority engagement, and the security architecture that has to survive review — including for data categories most programs assume are disqualified from cloud entirely.

Industrial IoT, OT & Hybrid Infrastructure

The infrastructure between the shipyard floor and the authorized cloud. Enterprise industrial IoT landing zones, OT network segmentation, edge collection and compute, and the hybrid architecture that industrial environments actually require — because drydocks, machine tools, and production lines do not move to a region.

We are currently building an enterprise IIoT landing zone spanning a U.S. Navy shipyard enterprise, with the same architecture pattern being deployed at commercial shipbuilding primes and defense manufacturers. This is the fastest-growing part of our work, and roughly half of our current pipeline.

That program did not start as a program. It started with a Zero Trust architecture we designed and delivered to collect sensor data from IoT devices across the Navy's public shipyards worldwide — and grew into the enterprise effort once the pattern proved out.

The engineering is unglamorous and the constraints are real: intermittent and disconnected operation, industrial protocols that predate the internet, controlled data moving off a factory floor, and an authorization boundary around all of it.

Reference architecture: one authorization boundary from OT through cloud A left-to-right flow. A single authorization boundary encloses three stages together: the industrial and OT environment containing machine tools and CNC, sensors and PLCs, and SCADA and historian systems, which use legacy protocols and cannot be relocated; the edge, performing local collection, protocol translation, and store-and-forward through intermittent and denied connectivity; and the cloud, containing the industrial IoT landing zone, segmented tenancy, and logging and monitoring. Enclosing all three in one boundary gives a single accreditation scope. Outside that boundary, and under its own separate boundary, sits the enterprise cloud, which consumes the result as a digital thread, analytics, and sustainment records. Single authorization boundary — one accreditation scope Enterprise cloud — separate boundary Industrial / OT Machine tools & CNC Sensors & PLCs SCADA & historians Legacy protocols, no IP stack, cannot be relocated Edge Local collection Protocol translation Store & forward Operates through intermittent and denied connectivity Cloud IIoT landing zone Segmented tenancy Logging & monitoring Controlled data under continuous monitoring Enterprise Digital thread Analytics Sustainment records

Reference pattern, generalized. One boundary spans OT, edge, and cloud rather than several — a single accreditation scope is materially easier to defend and to operate. The enterprise cloud sits outside it, under its own.

Zero Trust & Cloud-Native Architecture

Enterprise architecture for Navy cloud programs and adjacent Department of War environments, from reference architecture through implementation. Landing zones, SCCA-aligned network security stacks, identity federation, and the Zero Trust patterns underneath the Navy's current cloud enterprise direction.

Our Zero Trust work includes the architecture behind globally distributed IoT sensor collection across the Navy's public shipyards — spanning multiple regions, double-encrypted transport, and operation through intermittent and denied connectivity.

AI in Controlled Environments

Deploying AI where the data cannot leave and the environment has to stay authorized. Model and agent architecture inside accredited boundaries, AI-assisted engineering toolchains approved for controlled data, and the security and compliance work that determines whether any of it is allowed to run.

We are heavy users of these tools in our own delivery, which is a meaningful part of why a team this size moves at the pace it does. The customer-facing version is less about model selection than about the same question we have answered for a decade in other forms: what does it take to get this approved, and to keep it approved.

Executive & Board Advisory

Direct advisory for leadership teams making cloud and platform decisions under regulatory, security, or mission constraints — typically where a decision is expensive to reverse and the technical detail actually determines the outcome.

Where We Work

Two verticals anchor the work, and we treat them as distinct: the Navy's cloud and architecture enterprise, and the maritime industrial base — the commercial shipbuilding primes and their suppliers. They overlap constantly, but the buyers, constraints, and pace differ, and we scope accordingly.

In Q4 2026 we extend into Europe through a Dutch entity, targeting the same sectors: the maritime industrial base and ministries of defense. We expect the European work to be weighted similarly toward industrial infrastructure and OT.

More on Stigian Europe →

We take adjacent defense and critical-infrastructure work selectively, where prior work directly applies. We are not building a services menu.

Engagement Model

Engagements run two to three Principal Engineers deep, with delivery augmented throughout by AI-assisted tooling.

Standard rates run $450–500/hr. Government rates, reflecting applicable cost-sharing arrangements, are available on request.