INNOVEXUS
Verified
Compliance Report · Live VerificationVerified live

Where we run,and how we prove it.

Every fact on this page is pulled from live infrastructure telemetry — not a marketing deck. If our hosting configuration ever drifts away from what we claim, this page will say so before you have to ask.

2026-04-25 07:21:23 UTCInnovexus HubUS-IL-1JSON endpoint
§ 01 / Live verification

The pod servingthis request.

When you opened this page, we queried the RunPod REST API for the hub pod hosting the request and read back its actual cloud type and data-center placement. No caching. No precomputed assumptions.

Infrastructure Verification
#a9c707ef1055
Secure Cloud verified
Data Center
US-IL-1
Location
US
CPU Flavor
cpu3c
Cloud Type
SECURE
Secure Cloud
true
Checked At
2026-04-25 07:21:23Z
§ 02 / Provisioning policy

Hardcoded intoevery new pod.

These are not preferences. They are enforced at the API level in the provisioning code path. If RunPod ever returns a pod that doesn't match, we terminate it before it ever serves a request.

provisioning_policy.py
# Enforced on every client pod — fail-closed verification
cloudType           = "SECURE"
computeType         = "CPU"
requireSecureCloud  = true
dataCenterIds       = [
  "US-NC-1",
  "US-TX-3",
  "US-KS-2",
  "US-IL-1",
]
validCpuFlavors     = ["cpu3c", "cpu3g", "cpu5c", "cpu5g"]
§ 03 / Attestations

Certifications,attributed precisely.

Every certification below is labelled with the party that actually holds it. Innovexus inherits infrastructure compliance from its hosting partner's audited Secure Cloud facilities — we do not claim them as our own independent attestations.

Data Center / Hosting Facility

Active

SOC 2 Type II

Held by

RunPod Secure Cloud partner data centers

Active

ISO 27001

Held by

RunPod Secure Cloud partner data centers

On Request

HIPAA

Held by

RunPod Secure Cloud partner data centers (select facilities)

Cloud Provider (RunPod)

Active

SOC 2 Type I

Held by

RunPod (company)

In Progress

SOC 2 Type II

Held by

RunPod (company)

Data Center Tier

Deployed to Tier 3 / Tier 4 facilities operated by RunPod Secure Cloud.

Provider reference
§ 04 / What we will and will not say

Honest marketingby definition.

The left column is the full set of statements Innovexus will make about its infrastructure. The right column is the set of statements no Innovexus employee or partner may use — even if they would help close a deal.

Approved Claims
  • Hosted on RunPod Secure Cloud in Tier 3 / Tier 4 data centers.
  • Hosting-partner data centers are SOC 2 Type II and ISO 27001 audited.
  • HIPAA-capable data centers are available on request.
  • US data residency by default.
  • Every pod is verified at creation time to confirm Secure Cloud placement; pods that fail verification are terminated before entering service.
  • Encryption in transit (TLS 1.3) and at rest on RunPod network volumes.
Disallowed Claims
  • Innovexus is SOC 2 Type II certified (we are not — our hosting partner's data centers are).
  • Innovexus is HIPAA compliant (requires a signed BAA and a documented HIPAA security program).
  • All Innovexus deployments run in Tier 4 data centers (Secure Cloud spans Tier 3 and Tier 4).
  • Innovexus is ISO 27001 certified (the hosting partner's data centers are, not Innovexus).
§ 05 / Attestation boundary

The disclaimerwe believe in.

Innovexus does not independently hold SOC 2 or HIPAA attestations. Infrastructure-layer compliance is inherited from our hosting partner's audited Secure Cloud facilities and does not by itself constitute a HIPAA-compliant product offering. HIPAA-scoped deployments require a separate BAA.
Compliance Model
infrastructure_inheritance
Independently Certified
no
HIPAA Workloads
BAA required — contact us
§ 06 / FAQ

Common questionsauditors ask first.

Direct answers to the questions we get most often. Each answer is self-contained — quote any of them in an audit response, vendor questionnaire, or RFP and the meaning will not depend on the rest of this page.

Q.01Is Innovexus SOC 2 Type II certified?

Innovexus does not independently hold a SOC 2 Type II attestation. The infrastructure Innovexus runs on — RunPod Secure Cloud — is operated in data centers that are audited to SOC 2 Type II and ISO 27001 standards. We disclose this distinction explicitly: every certification on this page is labelled with the party that actually holds it. Customers requiring an Innovexus-issued SOC 2 letter for their own audit should contact the compliance team directly.

Q.02Where is Innovexus hosted, and which data centers?

Innovexus pods run on RunPod Secure Cloud, deployed exclusively to Tier 3 and Tier 4 facilities. The exact data center serving any given pod is verified live against the RunPod REST API at provisioning time and is published on this page. US data residency is the default; specific data center IDs are listed in the provisioning policy section above.

Q.03Can Innovexus support HIPAA-scoped workloads?

Innovexus infrastructure inherits SOC 2 / ISO 27001 controls from RunPod Secure Cloud, but infrastructure-layer compliance is not the same as a HIPAA-compliant product offering. HIPAA-scoped deployments require a separate Business Associate Agreement (BAA) and additional administrative controls. Email [email protected] to discuss BAA scope, PHI handling boundaries, and whether your use case fits within the current Innovexus HIPAA-ready posture.

Q.04How does Innovexus prove the infrastructure claims on this page?

Every fact on this page is fetched at request time from the Innovexus Hub, which queries the RunPod REST API for the actual cloud type and data center placement of the pod serving the request. There is no precomputed cache. If RunPod ever returns a pod that does not match our provisioning policy, the pod is terminated before it serves a request. The same JSON the page renders is exposed at /api/compliance/posture for auditors.

Q.05What is "Secure Cloud" and why does it matter?

Secure Cloud is RunPod's tier of GPU/CPU compute deployed exclusively to enterprise-grade audited data centers (Tier 3 / Tier 4) with stricter physical, network, and provider controls than general-purpose Community Cloud. Innovexus enforces Secure Cloud at the API level: the provisioning code path will refuse to register a pod that is not flagged Secure Cloud, and any drift is surfaced on this report instead of being hidden.

Talk to ourcompliance team.

BAA AVAILABLEJSON API LIVE

For HIPAA-scoped deployments, regional data residency, or if you need a copy of the underlying hosting partner attestations for your auditor — we'll get you what you need.

[email protected]JSON API