A cloud native platform offering comprehensive control and automation of all HPC tasks via CLI and a user-friendly GUI for designing, editing, and executing HPC jobs. Human-readable, portable workflow files that execute anywhere. Streamlined R&D for HPC & AI Research.
CIQ Fuzzball is a container-first performance intensive computing platform that accelerates innovation by reducing the burdens of workflow development, infrastructure provisioning and management of clustered jobs, even across hybrid environments.
Fuzzball modernizes traditional HPC with an API-first, container-optimized architecture. Operating on Kubernetes, it provides all the security, performance, stability, and convenience found in modern software and infrastructure.
Fuzzball takes an engineer and researcher-first approach and provides intuitive tools to build and deploy without expertise in infrastructure and lowers the barrier for all performance intensive computing. Fuzzball not only abstracts the infrastructure layer but also automates the orchestration of complex workflows, driving greater efficiency and collaboration. Plug it into your existing orchestration and automation, build your own SDKs, or simply point-and-click.
You define compute resource pools and the Fuzzball control plane analyzes the data, compute and storage requirements to automate the provisioning and orchestration of the right resources. Fuzzball makes it simple to embed and run applications with Workflow templates that can be built and designed for any workflow or application.
Fuzzball will deploy and optimize placement of your workflows across disparate clusters that reside in multiple regions or even across on-premise and cloud providers. This optimizes your environment based on data, compute and storage requirements and gives you the flexibility to develop in the cloud and deploy on premise or develop locally and deploy to the cloud for scale. And it comes with integrations for the tools you already use and templates so anyone can enjoy it, including Jupyter, Matlab, OpenRadioss, PyTorch, R Studio, TensorFlow, and it works with your CI/CD pipelines including Jenkins, GitLab, and GitHub Actions.
If you are planning on using CIQ Fuzzball, we strongly encourage you to review the Fuzzball documentation attached to this listing prior to purchase, and contact CIQ if you have any questions before clicking deploy.
Highlights
A user-friendly GUI for designing, editing, and executing HPC jobs. Comprehensive control and automation of all HPC tasks via CLI. Human-readable, portable workflow files that execute anywhere
Automated data ingress and egress with full compliance logs. Native integration with GPU, both on-prem and cloud storage, and your favorite applications and CI/CD pipelines.
Extensive is support included for installation and configuration, bug and security fixes, platform updates and upgrades, troubleshooting and diagnostics, integration, best practices, and general Fuzzball support for usage. See Support information for details.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Fuzzball bills by usage, charging you per minute across three separate dimensions. Fuzzball Orchestrate covers the control plane that schedules and manages your workflows. The two Substrate Node dimensions cover the compute that runs your jobs: a standard node and a GPU-enabled node. You pay for each node type by the minute it runs, so GPU workloads bill separately from standard compute. Total cost scales with how long you run Orchestrate plus the number and runtime of the nodes you use. Standard and GPU nodes are priced independently, letting you match compute to each job.
Top-of-mind questions for buyers
What counts as one Substrate Node for billing, and how does the GPU node differ?
A Substrate Node is a compute node that runs your workflow jobs. The standard node handles general compute, while the GPU node adds graphics-processing hardware for training and inference tasks. Each node bills per minute it runs. You choose which node type each job requires, so GPU compute meters separately from standard compute.
Am I charged when a node sits idle or a job finishes?
All three dimensions bill per minute of runtime. Charges accrue while Orchestrate is active and while each Substrate Node runs. When a node stops, its per-minute charge stops. GPU nodes bill only for the minutes they run, so ending a job halts that node's charges.
How do the three dimensions combine on my bill?
The three dimensions bill independently and appear together. Fuzzball Orchestrate meters the control plane that schedules workflows. Standard and GPU Substrate Nodes meter the compute running your jobs. Your total adds Orchestrate runtime plus the runtime of every node used. Node minutes usually drive most of the cost for compute-heavy or GPU workloads.
ciq.com
Helpful?
Vendor refund policy
CIQ does not offer refunds at this time.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
Fuzzball v4.2.1 release notes
Fuzzball v4.2.1 is a patch release that makes the AWS v4.1.0 -> v4.2.0
in-place upgrade reliable. The upgrade previously wedged in about one in ten
attempts when a targeted EKS control-plane update persisted an inconsistent
Pulumi snapshot; v4.2.1 removes that failure mode. It contains no other
user-visible changes.
Bug Fixes & Stability
Deployment & Infrastructure
AWS v4.1.0 -> v4.2.0 upgrades wedging on a corrupt Pulumi snapshot. The
targeted EKS control-plane up step ran with Pulumi's default parallel step
execution. Parallel checkpointing could record a renamed dependency's
untargeted Same step after its dependents' steps, saving a topologically
invalid snapshot; the stack then refused subsequent operations and the
upgrade had to be recovered by hand. About one AWS v4.1.0 -> v4.2.0 upgrade
in ten hit this. The targeted up is now serialized (--parallel=1); its
EKS operations are inherently sequential, so throughput is unaffected.
Deployments already past v4.2.0 are not exposed to the bug; this fix matters
for anyone still on v4.1.0 who has not yet upgraded.
Application-specific assistance to run workloads on Fuzzball and professional services to create and manage workflows are available from CIQ at an additional cost. Contact us for details.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.