Deployable infrastructure for field operations.
Evaluate portable compute for field locations, disaster response, and environments with constrained connectivity. Configuration planning addresses power, cooling, physical access, networking, and the security requirements of the deployment.
Why mission data must be processed on site
Deployable infrastructure is not a reduced version of our platform. It exists because some workloads originate in locations where network connectivity is the least reliable resource available.
Three form factors, one baseline
Every configuration runs the same software, verification, and monitoring as a server in any of our twelve facilities. Only the capacity and the method of transport differ.
Two-person lift
A single sealed server in a shock-mounted transit case, with local storage and full verification capability. It travels as checked baggage, runs on standard or generator power, and gives a small team a secure server that operates independently of any network connection. Suited to assessment teams, exercises, and program pilots.
- Compute
- 1 host, up to 32 cores
- Storage
- Up to 30.72TB NVMe
- Power
- 700W, 100 to 240V
- Transport
- Checked baggage or vehicle
Palletized
A shock-mounted, eight-unit rack with integrated networking, power conditioning, and independent management, in a frame rated for air and ground transport. Suited to command posts, mobile operations centers, and program offices that require more than a single server but less than a full facility.
- Compute
- Up to 4 hosts, 128 cores
- Storage
- Up to 123TB NVMe
- Power
- 3.5kW, single or dual feed
- Transport
- 463L pallet or vehicle
Self-contained
A complete, sealed data center within a shipping container, including computing, storage, networking, power conditioning, and cooling, with generator connection and intrusion monitoring. It is installed on a prepared pad, runs on utility or generator power, and operates as a full part of our authorized environment.
- Compute
- Up to 20 hosts, 640 cores
- Storage
- Up to 600TB NVMe
- Power
- 40kW, shore or generator
- Transport
- Road, rail, or sea
Each configuration is built to order under a signed agreement. Computing, storage, and networking are sized for each deployment, as with our permanent facilities. The figures above reflect current maximums per unit rather than fixed specifications.
Capabilities beyond a conventional server
The value of a deployable unit lies in how it protects evidence, encryption keys, and data while it is in transit and in the field.
The processor encrypts workload memory using keys the virtualization software never holds, exactly as in our permanent facilities. A deployed unit provides the same level of security.
When first powered on at its destination, the unit produces a signed report confirming it matches the state recorded when it was sealed. We recommend verifying this report before loading any data.
Each deployment is planned with a defined period of offline operation. During that period, the unit continues to operate, record activity, and enforce security policy without any connection to our central systems.
When connectivity is restored, data synchronizes in a defined order, following rules agreed during planning. No data is merged or discarded without a record.
Units ship under numbered seals with a chain-of-custody record. Seals are inspected and logged on receipt, and any broken seal is treated as a security incident.
An authorized operator can destroy encryption keys locally, without a network connection, rendering stored data unrecoverable and producing the required documentation.
How our authorization extends to the field
This is typically the first question an authorizing official asks, so we address it directly.
A deployable unit operates as part of the ServLogi Inc. authorized environment, not as a separate system. Each configuration is documented in our system security plan as a defined deployment pattern with its own control allocation. The pattern is approved once, rather than each individual shipment.
Your authorizing official approves the pattern
We provide the deployment pattern, control allocation, and boundary diagram for review before the first unit ships. Later deployments under the same pattern require only notification rather than a new authorization package.
Physical security responsibilities are defined
Because we do not operate the destination site, physical and environmental controls there are documented as the customer’s responsibility, with each control identified, so there is no ambiguity about what is inherited.
Evidence is collected offline
Audit records, access reviews, and scan results are stored locally while offline and delivered once connectivity is restored. Any gaps are clearly recorded rather than filled in afterward, as assessors require.
Impact levels are set during planning
Units supporting Impact Level 5 or 6 work are built, sealed, and handled under the personnel and handling requirements for that level. A unit does not acquire an impact level simply by connecting to a network that has one.
From planning to deployment in six steps
The process is the same for a single case or a full container. Only the build time differs.
- Scope and pattern reviewWe agree on the configuration, the offline period, the synchronization rules, and the physical security responsibilities at the destination. Your authorizing official reviews the deployment pattern and its control allocation.
- Build and baselineHardware is procured and prepared through our own supply chain, configured to the same baseline as our permanent facilities, and its firmware recorded. This record is what the unit is verified against on arrival.
- Seal and shipThe unit is sealed with numbered tamper-evident seals and released to the carrier, or to your own logistics team, with a chain-of-custody record.
- Receipt and field verificationAt the destination, seals are inspected and logged, the unit is powered on, and it produces a signed verification report. We recommend confirming this report before any data is loaded.
- Operate online or offlineThe unit operates under the same security policy, monitoring, and incident response plan as the rest of your deployment. Throughout the agreed offline period, it continues to enforce that policy independently.
- Return, synchronize, and sanitizeOn return, the unit synchronizes in the agreed order, and its storage is sanitized in accordance with NIST SP 800-88, with a certificate filed for your engagement. No unit returns to inventory with your data on it.
What the hardware is built to survive
The figures below reflect the design specifications for the SLD-1 and SLD-8 configurations. Containerized sites are climate controlled and specified according to the installation site.
- Operating temperature
- 0°C to 40°C ambient
- Non-operating temperature
- -30°C to 60°C
- Relative humidity
- 5% to 90%, non-condensing
- Operating altitude
- Up to 10,000 ft
- Shock and vibration
- Tested against MIL-STD-810H methods 514.8 and 516.8
- Enclosure
- Sealed case, IP54 closed, with pressure relief
- Input power
- 100 to 240V AC, 50/60Hz, generator tolerant
- Transport case
- ATA 300 Category I rated
Test reports for the specific configuration under consideration, including the methods and profiles used, are provided to verified agencies and cleared contractors under a mutual non-disclosure agreement.
Deployments this is built for
These examples illustrate typical use and do not represent a list of customers. Because agency and cleared contractor engagements restrict public attribution, we describe the type of deployment instead.
Forward and expeditionary sites
Computing capacity at locations with intermittent connectivity, where operations must continue uninterrupted when the network is unavailable.
Disaster response and emergency communications
Rapid deployment of dispatch, records, and coordination systems at an incident site when local facilities are unavailable.
Border, port, and inspection
On-site processing for screening and inspection, where transmitting raw data is neither fast nor economical enough to be practical.
Mobile command posts
Command units that relocate on short notice and require their secure servers to move with them under a single, continuous authorization.
Exercises and training ranges
Temporary environments that require full security controls throughout and a documented, secure decommissioning at the end.
Program surge
Additional capacity at a program site for a defined period, without building a facility or seeking a new authorization for a temporary deployment.
Lead times and allocation
Deployable units draw on the same hardware supply as our permanent facilities and follow the same capacity schedule. We recommend planning around the date you need the unit on site rather than your preferred order date.
Plan a deployment
Every deployable engagement begins with a location and a date. We recommend starting with one of the following.
Scope a deployment
A working session to review the site, the offline operating period, the right configuration, and the security responsibilities your authorizing official will need to review.
Learn about our permanent facilities
Deployable units run the same baseline as our twelve facilities. The hardware, network, and monitoring behind them are fully documented.
Verify a server report yourself
The verification performed on arrival follows the same procedure as for any other server. Review it to confirm it meets your requirements.