DATACENTERS
THAT THINK™

Mixed x86 and ARM - One Unified Fabric

Mixed architecture becomes one fabric.

STRATUM brings x86 and ARM infrastructure together in a single virtual machine fabric-not just a container platform. Workloads can run natively on either architecture or be emulated across architectures, giving organizations the freedom to balance performance, power efficiency, cost, and hardware availability without creating separate infrastructure silos. It is a game changer because mixed-architecture computing becomes flexible, portable, and practical across both datacenter and edge environments.

Intelligent Memory Deduplication

Run 10 VMs in the same footprint as 1 VM's memory!

Most VM fleets repeat huge amounts of the same RAM. Ten Windows or Linux VMs may load the same operating system, libraries, services, and application binaries into memory again and again while only their live data differs. Without deduplication, the host can store those identical pages 10, 20, or 30 times. STRATUMvisor makes memory deduplication a core platform capability: when eligible VMs contain identical memory pages, STRATUM keeps one shared copy and maps it into every VM that needs it. That can turn repeated gigabytes of identical RAM into a single shared memory footprint, freeing enormous capacity for more workloads. The more similar the VMs, the more dramatic the savings.

STRATUMvisor

The Hypervisor Built Into the Virtual Datacenter

Traditional hypervisors virtualize servers. STRATUMvisor virtualizes everything those servers depend on.

What it is

STRATUMvisor is STRATUM's integrated virtualization engine, delivered in the same portable OCI container image, without a separate hypervisor product, licensing tier, or management stack.

Under the hood

It uses KVM, when available, on Linux across x86 and Arm, with Hyper-V acceleration on supported Windows hosts. STRATUM adds its own orchestration, device models, storage fabric, networking, and virtual datacenter controls.

What makes it different

STRATUMvisor goes beyond VMs. Images are accessed directly through the integrated storage fabric, without host mounts, manual LUN mapping, or separate storage clients. Ports, cables, switches, and connections are first-class virtual objects. Instead of assigning a VM to an abstract network, you wire specific VM ports to specific ports on switches, routers, firewalls, and other systems.

Storage-as-a-Service, Built into the Fabric

Network storage is built into the infrastructure model.

STRATUM eliminates the need to engineer, deploy, and manage a separate SAN or NAS. Every STRATUM instance shares storage through a standards-based fabric protocol built directly into the hypervisor requiring no guest OS configuration, storage accounts, or additional management layer. Virtual machines boot directly from images stored across the network, without host-side mounts, manual LUN mapping, or a separately provisioned shared-block layer. STRATUMvisor accesses each VM image in place and presents it directly to the workload. Because the fabric is based on industry-standard iSCSI protocol, organizations gain established security controls and a cleaner path through STIG and NIST RMF assessment. Storage stops being another infrastructure project and becomes an integrated service available wherever STRATUM runs.

VM Storage, Reimagined for Hyper-Scale

Immutable bases and writable children reduce duplication and speed deployment.

To build a truly modern, hyper-scaling infrastructure platform, STRATUM had to change how virtual machines access storage. Every VM begins with an immutable, read-only template, while each individual workload stores only its unique changes in a lightweight child image. The common operating system and application base is stored once and shared across many VMs-eliminating massive amounts of redundant data without sacrificing isolation. Backing files, copy-on-write, compression, and space-efficient snapshots are not optional add-ons; they are fundamental to the STRATUM architecture. The result is faster VM creation, dramatically lower storage consumption, simpler recovery, and infrastructure that can scale far beyond traditional one-disk-per-VM designs.

Orchestration at Supercomputer Scale

The native Execution Fabric places workloads across heterogeneous infrastructure.

STRATUM builds orchestration directly into its native Execution Fabric. It places compute, memory, GPUs, priorities, resource constraints, accounting, and workload execution across heterogeneous infrastructure without relying on an external scheduler. Workers advertise architecture, CPU, memory, acceleration, site, and other capabilities. STRATUM matches workloads to those resources, maintains execution state and accounting, and continuously reconciles the fabric as infrastructure changes.Workloads can run across mixed x86 and Arm systems, CPU-only nodes, local GPUs, and GPUs delivered through the STRATUM Accelerator Fabric. Architecture and accelerator requirements become placement choices instead of separate infrastructure islands. Authenticated execution channels, health monitoring, worker timeouts, placement constraints, reconciliation, and recovery are built into the platform. The result is resilient orchestration that places each workload on the right resource and scales from a small edge deployment to a distributed compute fabric. STRATUM provides the virtual datacenter-and the execution fabric that operates it at scale.

Federation-ready

Cloud, on-prem, and remote sites stay part of one operating model.

Run across cloud, on-prem, and remote sites without splitting the platform into disconnected islands of control.

Multi-Site Quick Connect

Distributed sites become one virtual infrastructure without a separate control island.

STRATUM connects datacenter, cloud, remote, and edge environments into one unified virtual infrastructure-without the complexity of traditional mesh networking. A lightweight deployment model brings distributed sites together as a single virtual datacenter, making expansion, workload mobility, and remote operations dramatically simpler.

INFRASTRUCTURE IS NO LONGER BACKGROUND

The substrate becomes something operators can see and control.

Missions do not run on intent alone. They run on systems, dependencies, and environments that must be built, understood, and controlled before anything above them can succeed. STRATUM turns that hidden substrate into an operational surface.

The network is the container.

A complete virtual infrastructure, including machines, switches, routers, wiring, and segmentation, can be delivered and scaled through the same operational model as modern software.

Operational visualization before execution.

See the deployment before it ships. Validate topology, templates, and segmentation in an environment built to be understood before it is launched.

The GPU is a first-class citizen.

STRATUM treats GPU-backed workloads as native infrastructure from the ground up, not as a fragile add-on to a legacy virtual stack.

Federation-ready

Run across cloud, on-prem, and remote sites without splitting the platform into disconnected islands of control.

STRATUMOPS: See the Mission, Not Just the Machines

Topology, lineage, health, history, mission context, and blast radius become one operational graph.

STRATUMOPS is infrastructure operations as a living, temporal mission model, not another dashboard full of disconnected metrics. STRATUM scheduler tells STRATUMOPS where computation is running. STRATUMOPS tells it what that computation means. STRATUMOPS fuses scheduler data, VM state, tenants, virtual datacenters (VDC), networks, distributed GPU leases, remote sites, and dependencies into a live operational graph. It does not just show systems connected by lines-it shows ownership, lineage, health, history, mission context, and blast radius. With real-time graph updates, historical topology, mission replay, alerts, workflow automation, and failure-impact analysis, STRATUMOPS can answer the questions traditional infrastructure tools cannot: What is running? Where is it running? What does it depend on? Operational lineage? Who owns it? And what breaks when this asset fails? What systems are affected by this template?