C-Gen.AI
Menu
Nucleaton™
Enterprise-level Architecture

One platform layer.
Two architecture paths.

Nucleaton sits between your resource scheduler and your customer workloads.
Whether you're running an enterprise AI platform or operating a datacenter, the same policy and placement engine connects commitment to capacity.

Enterprise Architecture

Slurm as the foundation, Nucleaton as the platform.

Slurm remains the authoritative resource scheduler for GPU allocation. Nucleaton operates on top, automating cluster deployment, enforcing resource policy, managing training jobs, and placing inference workloads into eligible spare capacity.

An optional Kubernetes overlay provides inference endpoints, agent hosting, and model serving. Both Slurm and K8s draw from the same physical fleet, coordinated by Nucleaton's resource policy layer.

Enterprise architecture stack: customers, Nucleaton platform layers, Slurm, and GPU hardware
Slurm as base resource authority with Nucleaton platform layers above
Why Slurm

Purpose-built for GPU training at scale.

Slurm is the de facto workload manager for large-scale GPU training. It understands job arrays, node partitions, hardware topology, and fair scheduling across thousands of GPUs. Nucleaton doesn't replace Slurm; it extends it with automated deployment, resource policy, converged inference placement, and customer-facing service delivery.

Platform Layers

Each layer adds capability. None replaces your scheduler.

Service Delivery

Inference endpoints, agents, model hosting, and branded tenant portals.

Resource Policy

Guaranteed, flexible, and reclaimable capacity tiers governed by operator-defined rules.

Placement Engine

Priority-aware scheduling that places training and inference into one physical pool.

Cluster Automation

OS, drivers, networking, parallel filesystems, and Slurm configuration, deployed in minutes.

Datacenter Architecture

From tenant contract to physical fleet.

For datacenter operators, Nucleaton extends northward to meet customer contracts and southward to manage physical infrastructure. The same policy engine that places workloads also connects to Redfish, BMC interfaces, and datacenter management systems.

This creates a single control loop: customer commitments become enforceable resource policies, resource policies drive placement decisions, and placement decisions respond to real hardware state.

Datacenter architecture: northbound tenants through Nucleaton to southbound Slurm and physical hardware
Northbound service contracts mapped to southbound datacenter controls
Control Plane

Northbound commitments, southbound control.

The northbound interface handles tenant onboarding, service level definitions, and capacity commitments. The southbound interface manages compute nodes, GPU health, scheduling partitions, and physical infrastructure state.

Datacenter integrations are currently in beta.
Supported management systems are expanding.

Existing Slurm clusters can be integrated through assisted deployment with appropriate administrative access.

See how Nucleaton fits your infrastructure.