{"resourceId":"nvidia-dgx-cloud-create-runai-limitations","versions":[{"version":"external-f82e3351b89ba20c3f745058dbf506bd0549074cbb2b0294b2b3904c58cf169d","resource":{"id":"nvidia-dgx-cloud-create-runai-limitations","title":"DGX Cloud Create docs: Run:ai managed limits — no SOC 2/HIPAA, H100-only, no GPU splitting","organization":"NVIDIA","sector":"Technology vendor","geography":"Global (AWS/GCP managed service)","publishedAt":"undated documentation page (retrieved 2026-10-14); why now: day after Run:ai open-source release","publicationDate":null,"eventDate":null,"sourceName":"NVIDIA DGX Cloud Create Documentation","sourceLabel":"Vendor product documentation","sourceUrl":"https://docs.nvidia.com/dgx-cloud/run-ai/latest/limitations.html","evidenceClass":"vendor-claim","outcomeClass":"cautionary","topics":["infrastructure","data-security","operating-model","governance-procurement"],"finding":"NVIDIA's DGX Cloud Create limitations page states the managed Run:ai offering is restricted: customer workloads cannot use privileged containers, host networking, HostPath mounts and related Kubernetes features; customer admins cannot create/edit clusters, nodes, node pools or Run:ai control-plane settings. Only H100 GPUs on AWS and GCP are supported (not GB200 NVL72). NVCF, NVIDIA Blueprints, multi-node inference, GPU splitting/partial GPUs and mixed GPU types in one cluster are unsupported. The cluster is not SOC 2 Type 2 nor HIPAA compliant. Why now: day after the Run:ai open-source release, buyers comparing community self-host vs managed DGX Cloud Create need these constraints.","sledRelevance":"High for universities and agencies evaluating managed GPU clouds for research or pilots with regulated data.","evidence":"Vendor documentation of product limits; page undated in retrieved HTML; applies to managed service, not all Run:ai deployments.","architectureImplications":"Managed multi-tenant restrictions; no MIG/partial GPU; H100-only today.","governanceImplications":"Customer System Administrator capabilities removed; TAM-mediated changes.","securityPrivacyImplications":"Hardened Kubernetes policies; explicitly not SOC 2 Type 2 or HIPAA—block PHI/regulated workloads.","caveats":"Docs page undated; limits may change; distinct from self-hosted open-source Run:ai.","streamIds":["nvidia","research","campus-operations"],"roles":{"sales":"Sales framing: NVIDIA's own DGX Cloud Create docs say the managed Run:ai cluster is not SOC 2 Type 2 or HIPAA compliant, supports only H100 on AWS/GCP today, and disables GPU splitting plus several AI Enterprise components. For SLED sellers comparing yesterday's open-source Run:ai to managed cloud, lead with these limits so regulated-data buyers are not surprised. Interpretation: use the page as a disqualifier checklist, not a feature pitch.","engineering":"Engineering framing: security policies block privileged containers, host networking, HostPath mounts and ClusterRoleBinding changes, and customer admins cannot edit nodes, pools or Run:ai control-plane settings. Pre-sales engineers should map workloads that need MIG or partial GPUs, Blueprints, NVCF, multi-node inference or GB200 off this SKU onto self-hosted open-source Run:ai or another cloud before a proof of concept starts, especially after yesterday's open-source release.","delivery":"Delivery framing: onboarding must include a compliance and feature-fit gate before any proof of concept with student, health or justice data, because the docs state the cluster is not SOC 2 Type 2 or HIPAA compliant. Delivery teams should record the H100-only and no-partial-GPU constraints in the architecture decision record and brief researchers who may assume open-source Run:ai features apply here. Acceptance criteria below are proposals, not observed results."},"roleDetails":{"sales":{"customerProblem":"Buyers need clear limits of managed GPU cloud before placing research or pilot workloads with regulated data.","stakeholders":["Research computing director","CISO / compliance","Cloud procurement","PI / data steward"],"discoveryQuestions":["Does any workload involve PHI, CUI or other regulated data?","Do you need GPU fractions or MIG?","Is GB200 or multi-node inference required?"],"valueHypothesis":"Interpretation: the managed service can speed non-regulated H100 research if limits are acceptable; it cannot satisfy HIPAA/SOC 2 needs per this page.","potentialEngagement":"Fit assessment comparing DGX Cloud Create limits to self-hosted open Run:ai for one research workload class.","unsupportedClaims":["HIPAA or SOC 2 compliance","GB200 support","GPU splitting on this SKU","That limits match self-hosted Run:ai"]},"engineering":{"fit":"Moderate for non-regulated H100 research on AWS/GCP; poor for HIPAA/PHI, Blueprints, NVCF, partial GPUs or GB200.","architectureIntegration":"Managed Run:ai on DGX Cloud Create with restricted Kubernetes capabilities and customer admin roles.","prerequisites":["AWS or GCP tenancy via NVIDIA","H100-compatible workloads","TAM channel for cluster changes"],"constraints":["Not SOC 2 Type 2 or HIPAA","H100 only (no GB200 NVL72)","No GPU splitting/partial GPUs","No Blueprints/NVCF/multi-node inference"],"security":"Platform blocks high-risk Kubernetes features; compliance certifications for the cluster are explicitly absent for SOC 2 Type 2 and HIPAA.","proofOfValue":["Classify data before onboarding","Test a non-regulated workload end-to-end","Confirm Nsight/profiling needs against documented limits"]},"delivery":{"work":"Run a compliance and feature-fit gate, then onboard only eligible workloads with documented exceptions.","dependencies":["NVIDIA TAM","Institutional compliance office","Cloud networking/identity"],"ownership":"Research computing with CISO sign-off for data classes.","skillsAdoption":"Users adapt to reduced admin powers; ops rely on TAM for cluster changes.","governanceCheckpoints":["Data-class approval","Feature-fit sign-off","Exit criteria if limits block science"],"acceptanceCriteria":["Proposed: written HIPAA/SOC 2 disqualifier acknowledgment","Proposed: pilot workload completes without needing blocked features"],"risks":["Regulated data placed on non-HIPAA cluster","Science blocked by missing fractions/Blueprints","Confusion with open-source Run:ai capabilities"]}},"retrievedAt":"2026-10-15T03:01:18Z","enrichedAt":"2026-10-15T03:08:04Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Reduced admin surface may ease ops but blocks advanced profiling (Nsight limits).","procurementImplications":"Compliance buyers must not assume HIPAA/SOC 2 from this SKU.","operatingModelImplications":"Managed service tradeoff: less control, NVIDIA-operated plane.","sourceVerification":{"openedUrl":"https://docs.nvidia.com/dgx-cloud/run-ai/latest/limitations.html","referenceExcerpt":"The DGX Cloud Create cluster is not SOC2 Type 2 nor HIPAA compliant.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}