Pattern 1
Useful for small local workloads where power, cooling, loading, fire, and maintenance fit the workspace.
Resources / Reference Architectures
Three physical patterns, one evidence discipline
Secure compute does not require one physical form. The mission, power density, cooling, maintenance, network, and approval boundary determine whether compute sits inside, adjacent to, or remote from the secure workspace.
Concept architectures
Pattern 1inside workspace
Pattern 2paired module
Pattern 3remote site
Evidence matrix
Pattern comparison
| Criterion | Inside secure workspace | Paired workspace + module | Remote secure site |
|---|---|---|---|
| Mission proximity | Highest | High | Network dependent |
| Compute density | Low | Medium to high | High |
| Maintenance separation | Difficult | Strong | Strongest |
| Site mobility | High | High to medium | Low to medium |
| Approval complexity | Integrated facility and system | Paired boundary and interface | Facility, system, network, and remote access |
| Best initial use | Edge analytics | Modular secure node | Regional shared capacity |
Capability set
Reference preference
Pattern 2
Preferred first modular pattern: separate people and sensitive discussions from heat-generating infrastructure while preserving a short controlled link.
Pattern 3
Scale pattern when a sponsor or customer authorizes remote access to a larger secure compute site.
Next decision
Every pattern needs a site delta
The reusable baseline accelerates review only when local threat, climate, utilities, access, construction, configuration, and operating differences are documented.