AGGX
Technology

From silicon to served tokens

AGGX hardens GPU virtualization, parallelism, and attestation into a programmable substrate for AI. Five layers turn a fleet of heterogeneous GPUs into one elastic, verifiable, and measurable compute grid.

Not a rental marketplace with a dashboard on top — a control plane that decides where every workload runs, proves it ran correctly, and prices it by the second.

NVIDIA Blackwell GPU cluster
Blackwell · Hopper · Ampere — one grid
1–7
Slices per GPU
1.8 TB/s
NVLink per GPU
< 50 ms
Slice cold start
99.5%
Monthly uptime target
Architecture

Five layers, one control plane

Each layer depends only on the one beneath it. That is what makes the grid portable across hardware generations — new silicon slots in at layer 01 without rewriting anything above it.

01

Hardware Fabric

NVLink / NVSwitchInfiniBandHGX / NVL72Multi-region

Heterogeneous GPU fleets — Blackwell, Hopper, and Ampere — wired with NVLink inside the node and InfiniBand or 800 GbE between them. Nodes are pooled into a single logical grid rather than managed as isolated clusters.

02

Slicing & Virtualization

MIG-class isolationvGPUMemory partitioningQoS floors

Adaptive GPU Grid Xlicing partitions each physical GPU into hardware-isolated units with their own memory ceiling, compute share, and bandwidth floor. Slices are the unit of scheduling, metering, and QoS enforcement.

03

Orchestration & Scheduling

Topology-aware placementPolicy engineKubernetes-nativeBin-packing

A telemetry-driven control plane places work across the grid in near real time, matching each job to the topology that fits it. A policy engine enforces reservations, quotas, tenancy rules, and chargeback across teams.

04

Verification & Attestation

TEE attestationSigned usage recordsExecution auditTamper evidence

Trusted execution environments produce cryptographic proof that work ran as scheduled at full precision. Every slice emits a signed usage record you can reconcile against your own telemetry.

05

Workload & Serving

Continuous batchingPaged KV cacheAutoscaled endpointsBatch inference

Optimized runtimes for training and inference sit on top: continuous batching, paged attention, quantized weights, and autoscaled endpoints — with ephemeral slices that spin up in milliseconds for bursty traffic.

Core Technologies

What we actually build

Six engineering problems sit between a rack of GPUs and a workload that runs fast, cheaply, and provably. These are the ones we work on.

01

Adaptive GPU Grid Xlicing

Partitioning that adapts to the workload, not the other way around.

Static GPU allocation wastes capacity: a 7B inference model pinned to an 80 GB card leaves most of the silicon idle. AGGX slices each GPU into hardware-isolated partitions sized to the job, then resizes the partition map as demand shifts — without evicting running work.

  • Memory, SM share, and interconnect bandwidth allocated per slice
  • Hardware-level isolation, not time-slicing — noisy neighbours cannot steal cycles
  • Partition maps recomputed continuously as jobs enter and leave
  • Per-slice QoS floors enforced at the scheduler and the driver
02

Telemetry-Driven Scheduling

Placement decisions informed by what the hardware is actually doing.

Every node streams continuous telemetry — VRAM pressure, SM occupancy, thermal headroom, NVLink and fabric saturation, matrix-multiplication throughput, and network jitter. The router trains on that stream to predict where a given job will run fastest and cheapest, then places it there.

  • Microsecond-level task partitioning across heterogeneous hardware
  • Topology-aware placement for tensor, pipeline, and data parallelism
  • Pre-emptive migration away from thermally throttled or degraded nodes
  • Reinforcement-learned routing over a Mixture-of-Experts gating network
03

Verifiable Execution

Proof that the work you paid for actually ran.

In a distributed grid, trust cannot be assumed. AGGX audits distributed workers to confirm they executed full-precision matrix operations as scheduled — catching silent downgrade to lower precision, spoofed results, and partial execution before those results reach you.

  • Trusted execution environments (TEEs) for attested compute
  • Lightweight verifier models auditing worker output at high throughput
  • Signed, immutable usage records per slice and per billing period
  • Precision-downgrade and result-manipulation detection
04

Inference Optimization

Serving models at a fraction of the naive cost.

The fastest GPU is the one you do not have to rent. Our engineering work concentrates on making models cheaper to serve — through quantization, compression, kernel-level tuning, and batching strategies that raise throughput without breaking latency targets.

  • Quantization across FP16, BF16, FP8, INT8, and INT4
  • Pruning, distillation, and structured compression pipelines
  • TensorRT, NVIDIA Triton, ONNX Runtime, and vLLM serving paths
  • Continuous batching and paged KV-cache management
05

Distributed & Multi-GPU Execution

Scaling past the memory ceiling of a single card.

Frontier models do not fit on one GPU. AGGX handles the sharding, collective communication, and failure recovery that multi-GPU and multi-node execution demand — so a 200B-parameter model behaves like a single addressable endpoint.

  • Tensor, pipeline, and expert parallelism across node boundaries
  • NCCL collective tuning matched to the physical interconnect
  • Checkpointing and mid-run recovery for long training jobs
  • Distributed inference with cross-node KV-cache coordination
06

Observability & Capacity Intelligence

Every slice is measured, priced, and explainable.

Slice-level instrumentation feeds both your dashboards and our capacity planner. The same telemetry that drives scheduling also models global GPU availability and power-cost curves, pricing capacity in real time rather than on a fixed rate card.

  • Nsight-grade metrics surfaced per slice, per job, per team
  • Bottleneck attribution: compute-bound, memory-bound, or fabric-bound
  • Per-second metering with reconcilable billing records
  • Real-time capacity and yield modelling across regions
Hardware Platform

Four generations, one scheduler

Workloads are matched to the generation that fits them. Long-context training goes to Blackwell; steady inference runs cheaper on Hopper and Ampere slices.

GPUArchitectureMemoryInterconnectNode FormatStatus
NVIDIA B300Blackwell Ultra288 GB HBM3e1.8 TB/s NVLinkHGX B300 NVL8Q4 2026
NVIDIA B200Blackwell180 GB HBM3e1.8 TB/s NVLinkHGX B200 / NVL72Deploying
NVIDIA H100Hopper80 GB HBM3900 GB/s NVLinkHGX H100 SXMAvailable
NVIDIA A100Ampere80 GB HBM2e600 GB/s NVLinkHGX A100 SXMAvailable
High-density data centre with NVIDIA Blackwell nodes
High-Density Co-location
Liquid-cooled racks, redundant power, direct fabric peering
Software & Compatibility

Bring your own stack

Slices present as standard CUDA devices. If your job runs on a normal GPU today, it runs on AGGX without code changes.

Frameworks
PyTorchJAXTensorFlowDeepSpeedMegatron-LMFSDP
Inference Runtimes
TensorRTTensorRT-LLMNVIDIA TritonONNX RuntimevLLMSGLang
Precision Formats
FP32TF32FP16BF16FP8INT8INT4
Orchestration
KubernetesDocker / OCISlurmRayHelmLinux
Profiling & Telemetry
Nsight SystemsNsight ComputeDCGMPrometheusOpenTelemetryGrafana
Networking & Storage
InfiniBandRoCE / 800 GbENCCLGPUDirect RDMANVMe-oFS3-compatible
Isolation & Trust

Multi-tenant without the trade-off

01Hardware isolation
Slices are enforced at the driver and firmware level. Tenants cannot read another tenant's memory, observe their utilization, or contend for their reserved bandwidth.
02Attested execution
Trusted execution environments produce a verifiable record that a workload ran on the hardware and at the precision you requested.
03Tenant-scoped networking
Each deployment runs inside its own network segment with explicit egress policy. Inter-node traffic never traverses the public internet.
04Export-control aware placement
Region and jurisdiction constraints are expressed as scheduling policy, so regulated workloads are never placed on non-compliant hardware.

Benchmark it on your own workload

We would rather show you the numbers than describe them. Send us a model and a throughput target, and we will run it on the grid and share the full profile — including where it bottlenecks.