Run batch HPC and the full AI lifecycle on infrastructure you control
Fuzzball is the orchestration platform that runs and secures AI and HPC workloads. Describe the work once in provider-agnostic YAML and it runs the same way on-premises, in the cloud, or across both. Each job routes to wherever it runs best on cost, performance, and data locality, so models and data stay on infrastructure you control.
Fuzzball runs and secures AI and HPC workloads on infrastructure you control. Describe the work once in provider-agnostic YAML and it runs the same way on-premises, in the cloud, or across both. Your own AI agents drive it over MCP, with every write and run waiting on your approval.
Get the solution brief
From the creators of Apptainer and the founding sponsor of Rocky Linux.
Runs anywhere you control
Secures every job the same way
Works on the first day and grows with the estate
1
Platform
Batch HPC and the full AI lifecycle, in one workflow file.
5
Clouds, plus on-premises
AWS, Google Cloud, Oracle Cloud, CoreWeave, and Azure, federated with your data center and managed from one control plane.
0
Data leaves
Models, weights, and data stay on infrastructure you control.
0
Rip and replace
Slurm, PBS, Lustre, and GPFS all stay exactly where they are.
Compare Fuzzball to a traditional HPC environment
Intersect360 Research on what a container-first, API-driven approach changes about running an HPC environment, and what it removes from your team’s week.
Built for teams facing this
- A sovereign-AI mandate with no plan for training and inference
- Sensitive data leaving for third-party AI services
- HPC and AI on separate platforms: queues on one side, idle capacity on the other
- GPUs you already own sitting idle while you rent more
From the team that created Apptainer and Singularity at Lawrence Berkeley National Laboratory, and the founding sponsor of Rocky Linux. National labs, federal programs, and the largest enterprises run production on CIQ.
Compare Fuzzball to a traditional HPC environment
Intersect360 Research examined what a container-first, API-driven approach changes about running an HPC environment. The white paper covers where the model holds up, what it removes from your team’s week, and what it means for a fleet that now carries both batch and AI work.
Built for teams facing this
- A sovereign-AI mandate from above, and no plan for how training and inference will actually meet it
- Researchers pushing sensitive data into third-party AI services before anyone checks whether the data-use agreements allow it
- HPC and AI on separate platforms, so users queue on one side while capacity sits free on the other
- Researchers who will not touch a command-line-only cluster, so the work leaks to laptops and shadow cloud accounts
- Every new environment arrives with its own identity model, its own credentials, and its own security review
- Capacity you already own sitting idle while the same work runs on rented GPUs
- Jobs break the moment the infrastructure underneath them changes
- An inference bill nobody can forecast for next quarter
One
Platform for batch HPC and the full AI lifecycle
One workflow definition covers train, fine-tune, validate, and serve, with the model served from an autoscaled pool behind one stable endpoint, or started from the catalog by name.
Sovereign AI
The whole lifecycle on infrastructure you control
Train, fine-tune, validate, and serve in your own data center or your own cloud accounts. Models, weights, and data never move to a third-party AI service.
100x
Throughput potential at FYR Diagnostics
FYR Diagnostics runs eight to ten multi-omic pipeline types in parallel on Fuzzball. “Fuzzball gives us the ability to implement and scale these pipelines for 100x the throughput in a fraction of the time,” says Claire Seibold, Director of Software and Data Analytics at FYR Diagnostics. New team member onboarding dropped from days to minutes, per pipeline.
5
Clouds, plus on-premises
AWS, Google Cloud, Oracle Cloud, CoreWeave, and Azure, federated with your data center and managed from one control plane, with work routed at runtime by cost, performance, and data locality.
Zero
Data migration, scheduler replacement, or SSH required
Runs against Lustre and GPFS in place, with PBS and Slurm staying on as backend provisioners. Researchers submit and monitor work from a browser.
See Fuzzball on your own workflow
Bring one workflow and the environments you have to run it in. A CIQ engineer will walk your team through the workflow file, a run on your own hardware, and the same run in a cloud, unchanged.
See Fuzzball on your own workflow
Bring one workflow. A CIQ engineer runs it on your hardware, then in a cloud, unchanged.