Compliance ReportVerified 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-14 00:41:21 UTC
Innovexus Hub
US-IL-1
JSON endpoint
01Live Verification

The pod serving this 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-14 00:41:21Z
02Provisioning Policy

Hardcoded into every 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-IL-1",
  "US-KS-2",
]
validCpuFlavors     = ["cpu3c", "cpu3g", "cpu5c", "cpu5g"]
03Attestations

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

SOC 2 Type II
Active

Held by

RunPod Secure Cloud partner data centers

ISO 27001
Active

Held by

RunPod Secure Cloud partner data centers

HIPAA
On Request

Held by

RunPod Secure Cloud partner data centers (select facilities)

Cloud Provider (RunPod)

SOC 2 Type I
Active

Held by

RunPod (company)

SOC 2 Type II
In Progress

Held by

RunPod (company)

Data Center Tier

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

Provider reference
04What we can and cannot claim

We keep our marketing honest by writing down what it can't say.

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).
05Attestation Boundary

The disclaimer we 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
Questions about compliance scope?

Talk to our compliance team.

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.