Multi-cluster fabric.
HPC, cloud, on-prem.
Three architectural layers. Three deployment models. The same fabric whether you run a single cluster on the public pool or aggregate dozens across your own perimeter.
One control plane. Any clusters underneath.
One job. Multiple clusters. Native distributed training inside each, coordinated across all of them. Inference deployed and served on the same fabric.
- Slurm scheduler
- 8 × H100 · 640 GB
- InfiniBand interconnect
- ◆ training · ◆ inference
- Kubernetes
- 8 × H100 · 640 GB
- Cloud interconnect
- ◆ training · ◆ inference
- Bare metal agent
- 8 × A100 80 GB · 640 GB
- NVLink
- ◆ training · ◆ inference
Public pool. Managed cluster. Private fabric.
Start on shared infrastructure, graduate to dedicated capacity, or run the entire fabric on hardware you own. Same training APIs, same inference APIs, same SDK at every tier.
Public Pool
Shared, multi-tenant GPU pool. Per-minute billing.
- →Pool aggregated from cloud and supplier nodes
- →Multi-tenant with strict workload isolation
- →Ephemeral compute — no persistent state between jobs
- →Fair-share scheduling with priority lanes
- →Single-cluster training and inference
Your workspace is mounted read-only at job start. Outputs are written back to your bucket. The node is wiped after job completion.
Experiments, prototyping, single-cluster training and inference when you don't own GPUs yet.
Have a cluster sitting idle? Plug it into the fabric.
HPC operators, datacenter owners, and teams with reserved cloud capacity can register clusters into the ResonTech supplier network. Jobs and inference replicas route to your nodes when there's a match; you earn from utilization without negotiating contracts.
This is not a consumer-GPU marketplace. We partner specifically with operators of professional clusters (8+ GPUs, fast intra-cluster network) — the kind of capacity that runs real distributed training and serves real production inference.
Register the cluster
Sign up as an operator. Provide cluster specs, location, scheduler (Slurm / K8s / bare metal), and availability windows.
Install the agent
One-line install of the ResonTech node agent. It registers your GPUs and joins them to the routing layer.
Configure availability
Define windows and resource allocation. The fabric factors your capacity into job routing alongside cloud and supplier nodes.
Monitor utilization
Real jobs land on your hardware automatically. Full dashboard visibility into utilization, job history, and resource metrics.
Minimum specs. And what we recommend.
For running jobs on the network and for supplying GPUs to it. Multi-node training prefers NVLink or InfiniBand within each cluster; cross-cluster coordination tolerates standard networking.
Three layers, three deployments,
one fabric.
Start on the public pool today. Talk to engineering when you need multi-cluster or a Private Fabric inside your perimeter.