AI Infrastructure Professional Service

Open-source AI infrastructure, installed and configured on your GPUs.

Our Kubernetes engineers set up what you need at each stage: a GPU cluster, an LLM serving stack, or a Run:ai AI platform. We test each one and hand it over with runbooks.

Book a call
Service 01 · GPU Cluster Foundation

Turn separate GPU servers into one Kubernetes cluster.

We install Kubernetes on your servers, automate the GPU drivers, and give your researchers one command to run a job on any free GPU. Your existing servers join the same cluster.

KubesprayGPU OperatorSkyPilot
GPU Cluster Foundation: separate servers before, one Kubernetes cluster afterBeforeTeams and researchersSSH to each serverServer A3 jobs waitingServer BidleServer CServer Dexisting×GPUs handed out in chat and spreadsheetsAfterTeams and researchersSkyPilotone command to submit a jobsky launchKubernetes control planeKubespray · free GPU per jobNode 1Node 2Node 3Node 4existingNode 5newGPU Operator · drivers on every node
Service 02 · LLM Serving

LLM traffic is not web traffic. It needs its own serving stack.

We install llm-d or NVIDIA Dynamo on your GPU nodes, connect it to your gateway and monitoring, and measure it under load.

llm-dNVIDIA DynamovLLM
LLM Serving architecture with llm-d or NVIDIA DynamoAppsChat · Agents · APIInference gatewayGateway APIInference Extensioncache- and load-aware1llm-d / NVIDIA DynamoPrefill poolreads the promptvLLMvLLM2KV cacheDecode poolwrites the answervLLMvLLMvLLMKV cache tiersGPU memoryCPU memoryStorage3Prometheus · Grafanametrics and dashboardsKubernetes · GPU Operator · NVIDIA GPUs
  1. 1
    Cache-aware routing

    Cache-aware routing sends each request to the replica that already holds its prompt start.

  2. 2
    Prefill and decode, split

    Prefill and decode run on separate GPU groups that scale on their own.

  3. 3
    KV cache tiers

    The cache moves to CPU memory and storage, and one model can span several nodes.

Service 03 · AI Platform (Run:ai)

Run:ai, installed with everything it depends on.

NVIDIA released Run:ai as open source in October 2026. It gives teams quotas, fair-share scheduling, and GPU fractions. It also needs Prometheus, an ingress, TLS, and workload operators. We install all of them, connect them to Run:ai, and customize the platform and the cluster for your teams.

Run:aiPrometheusKAI Scheduler
AI Platform architecture with open-source Run:ai and its required componentsTeams and researchersDepartmentsResearch50%Product30%Data20%guaranteed GPU share3Run:aiopen sourceKAI Schedulerfair share, gang schedulingResource Managementdepartments, projects, quotasGPU FractioningGPU fractionsWorkload Maptraining and inference jobs2Required componentsPrometheusmetricsIngress · DNS · TLSaccess and certificatesGPU Operatordrivers on every node1WorkloadsTrainingTraining OperatorInferenceKnativeNotebooksJupyterDistributedMPI · LWS4Node poolsPool A · H100Pool B · L40SGPU shared by workloads51STCLab setup stepGPU shared by workloads
  1. 1
    Install the required components
  2. 2
    Install Run:ai and connect it to them
  3. 3
    Set up departments, projects, and quotas
  4. 4
    Connect training and inference workloads, then validate
  5. 5
    Customize Run:ai and the cluster: scheduling policies, node pools, GPU fractions, and links to your systems

How an engagement runs

  1. 1
    Assess

    Your GPUs, workloads, teams, and targets.

  2. 2
    Select

    The open-source tools that fit your environment.

  3. 3
    Install and configure

    Each tool, connected to your gateway and monitoring.

  4. 4
    Validate

    Tests with your workloads and a written report.

  5. 5
    Hand over

    Runbooks, training, and support for your team.

+ Add-on
Wave GPU with HAMi Enterprise

Share each GPU between workloads, overcommit GPU memory, and see what every GPU is doing. Add it to any of the three services.

See Wave GPU →

Plan your AI infrastructure with us

Tell us about your GPUs and what you want to run. We will suggest the services that fit.

Book a call →