Skip to content
inetGeek

Hyperstack vs Lambda

OCT 2026 audit

A comparison of Hyperstack and Lambda built from values read directly from each provider's own documentation, with the source recorded against every figure.

Reviewed by Palash BagchiUpdated 22 criteria compared

The short answer

Choose Hyperstack if…

Steady European workloads that can commit — reserved H200 at $2.79 against $3.99 on demand is the clearest published discount in this set, and egress is free.

Editorial · Palash Bagchi · approved

Choose Lambda if…

Renting exactly the instance shape you need — Lambda publishes 1x, 2x, 4x and 8x plans for the same card, so a single H100 is a real product rather than a fraction of a node.

Editorial · Palash Bagchi · approved

Consider something else if…

  • Hyperstack: Billing is per minute rather than per second, so very short jobs round up in a way they do not at RunPod.
  • Lambda: You want the cheapest single H100: its H100 SXM is $4.29 per GPU-hour single-card, more than Hyperstack ($3.20) and RunPod ($3.99) charge for the same card, though under Crusoe and Nebius at $4.50, and reserved capacity is quoted through sales rather than published.

Neither quite fits? Every other option, ranked by iScore: Hyperstack alternatives · Lambda alternatives

17 sourced criteria separate them — see where, with sources, below.

Visit Hyperstack documentationVisit Lambda documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionHyperstackLambda
Pricing
Entry paid planPrepaid credit rather than a plan: deploying a VM needs a balance covering at least one hour of combined hourly cost - their worked example is $10.00.Pay-as-you-go per GPU-hour rather than a monthly plan: the cheapest self-serve instance is a 1x Quadro RTX 6000 at $0.69 per GPU-hour plus sales tax.
Pricing modelPay-as-you-go at hourly rates billed per minute; prepaid credit by default, with postpaid accounts billed at a fixed interval, typically monthly.On-Demand instances are priced by hourly usage and billed in one-minute increments; 1-Click Clusters per GPU per hour billed weekly; filesystems per GiB used per month.
Egress over allowanceFree. Egress and ingress traffic are not charged; a public IP address costs $0.00672043 per hour.Free. Lambda states transparent pricing with no egress fees.
Infrastructure
Regions
Three documented regions: NORWAY-1 (Vestland, Norway), CANADA-1 (Quebec, Canada) and US-1 (Texas, United States); more may appear per account.
14 On-Demand Cloud regions: nine in the USA plus Tokyo, Osaka, India, Germany and Israel. Not every instance type is available in every region.
GPU
H100 SXM, per GPU-hour
$3.20 per hour for H100 SXM 80GB on demand. The H100 NVLink is $2.60, and the row the page lists as plain "NVIDIA H100" is $2.50.
$4.29 per GPU-hour for H100 SXM 80GB on a single-GPU instance, falling to $3.99 on an 8-GPU node. The PCIe variant is $3.29.
Cheapest GPU, per hour
$0.15 per hour for an A4000 with 16GB; the A100 SXM 80GB is $1.60.
$0.69 per GPU-hour for a Quadro RTX 6000 with 24GB; the V100 is $0.79 and the A6000 $1.09.
Largest GPU offered
288GB per GPU on B300 at $7.40 an hour; B200 at 192GB is $6.00.
180GB per GPU on B200 SXM6, from $6.69 per GPU-hour on an 8-GPU node to $6.99 on a single GPU.
Billing granularityPer minute, with enterprise-scale contracts negotiated separately.By the minute.
Reserved pricingPublished reserved rates rather than a percentage: H200 SXM falls from $3.99 on demand to $2.79 reserved, about 30% below.Reserved capacity is quote-only. Committed 1-Click Clusters list $6.16-$5.54 per H100 GPU-hour and $9.86-$8.87 per B200 GPU-hour for 2 weeks-1 year, 16 to 256 GPUs.
Compliance
SOC 2SOC 2 Type 2 attested, achieved via parent company NexGen Cloud; the same page shows SOC 2 Type 1 as certified.SOC 2 Type II attestation, listed under the security and compliance pillar of Lambda's trust framework.
ISO 27001
Not certified: ISO 27001 sits on the upcoming-certifications list, shown as "ISO 20071" (sic) in progress.
ISO 27001 certified, alongside ISO 27017, 27701 and 22301.
HIPAANot yet: HIPAA is listed under "Coming Next", the security page's roster of upcoming certifications.Platform Guidelines, binding with the Cloud Terms of Service, prohibit submitting personal health information to the Services. Contractual prohibition on PHI, not a statement about a HIPAA audit or BAA.
GDPR / data residency
Regional data residency options across the UK, EU and other supported regions, with data centre regions in the EU, Canada and the US.
Processes European personal data under the GDPR and relies primarily on the European Commission's Standard Contractual Clauses for EEA, UK and Swiss transfers.
Encryption at rest
Not server-side for Object Storage: docs tell users who need encryption at rest to encrypt client-side. The Secure By Design page separately claims data is encrypted at rest and in transit.
All data on the 1-Click Cluster persistent file storage system is encrypted at rest using industry standard algorithms and parameters.
Role-based access control
Role-based access control: custom user roles built from policies and individual permissions; invited members start with none until a role is assigned.
Two account-level roles, Admin and Member; both have full access to resources, while only admins invite users, change billing and manage workspaces.
Private networking / VPCEach environment is allocated its own private /24 subnet; every VM in it gets a private IP from that subnet and they share one network space.1-Click Cluster compute nodes sit on a dedicated network segment with no inbound firewall connectivity, on a logically isolated Ethernet fabric.
Dedicated infrastructureSecure Private Cloud: dedicated, single-tenant infrastructure with zero shared resources, running on dedicated hardware with no shared GPUs.1-Click Cluster compute nodes run on single-tenant hardware with GPUs, storage, memory and NICs unshared; management head nodes are multi-tenant.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

Where they differ.

Entry paid plan

Hyperstack
Prepaid credit rather than a plan: deploying a VM needs a balance covering at least one hour of combined hourly cost - their worked example is $10.00.
Lambda
Pay-as-you-go per GPU-hour rather than a monthly plan: the cheapest self-serve instance is a 1x Quadro RTX 6000 at $0.69 per GPU-hour plus sales tax.
Sources (2) →

Pricing model

Hyperstack
Pay-as-you-go at hourly rates billed per minute; prepaid credit by default, with postpaid accounts billed at a fixed interval, typically monthly.
Lambda
On-Demand instances are priced by hourly usage and billed in one-minute increments; 1-Click Clusters per GPU per hour billed weekly; filesystems per GiB used per month.
Sources (2) →
  • Accounts, Billing Policies, and Usage Monitoring - Hyperstack Docs ↗

    “Hyperstack supports three account types, each with distinct billing behavior [...] Postpaid Account : Instead of pre-funding, postpaid accounts are billed periodically based on accumulated usage. Billing occurs at the end of a fixed interval, typically monthly. [...] Our billing system operates on a per-minute structure”

    Read 2026-10-17 · official docs · Report a correction

  • Billing overview - Lambda Docs ↗

    “ODC prices instances by hourly usage and bills in one-minute increments. [...] 1CCs are priced per GPU per hour and billed in weekly increments according to the terms of your reservation. [...] Filesystems are billed per GiB used per month in one-hour increments.”

    Read 2026-10-17 · official docs · Report a correction

Egress over allowance

Hyperstack
Free. Egress and ingress traffic are not charged; a public IP address costs $0.00672043 per hour.
Lambda
Free. Lambda states transparent pricing with no egress fees.
Sources (2) →

Regions

Hyperstack

Three documented regions: NORWAY-1 (Vestland, Norway), CANADA-1 (Quebec, Canada) and US-1 (Texas, United States); more may appear per account.

Lambda

14 On-Demand Cloud regions: nine in the USA plus Tokyo, Osaka, India, Germany and Israel. Not every instance type is available in every region.

Sources (2) →
  • Regions & Data Centers - Hyperstack Docs ↗

    “Hyperstack provides multiple regions (e.g., CANADA-1 , NORWAY-1 , US-1 ) [...] NORWAY-1 Vestland, Norway Sustainably Powered Region Not Available CANADA-1 Quebec, Canada Sustainably Powered Region Available* US-1 Texas, United States Standard Energy Region Available*”

    Read 2026-10-17 · official docs · Report a correction

  • Overview - Lambda Docs ↗

    “Lambda resources are hosted in multiple locations worldwide. Not every instance type will be available in every region. [...] asia-northeast-1 Tokyo, Japan asia-northeast-2 Osaka, Japan asia-south-1 India europe-central-1 Germany me-west-1 Israel [...] us-east-1 Virginia, USA us-east-2 Washington DC, USA us-midwest-1 Illinois, USA us-south-1 Texas, USA us-south-2 North Texas, USA us-south-3 Central Texas, USA us-west-1 California, USA us-west-2 Arizona, USA us-west-3 Utah, USA”

    Read 2026-10-17 · official docs · Report a correction

H100 SXM, per GPU-hour

Hyperstack
$3.20 per hour for H100 SXM 80GB on demand. The H100 NVLink is $2.60, and the row the page lists as plain "NVIDIA H100" is $2.50.
Lambda
$4.29 per GPU-hour for H100 SXM 80GB on a single-GPU instance, falling to $3.99 on an 8-GPU node. The PCIe variant is $3.29.
Sources (2) →
  • GPU Pricing — Hyperstack ↗

    “NVIDIA H100 SXM 80 24 240 $3.20 NVIDIA H100 NVLink 80 31 180 $2.60 NVIDIA H100 80 28 180 $2.50”

    Read 2026-10-17 · official pricing · Report a correction

  • GPU Cloud — Lambda ↗

    “NVIDIA H100 SXM 80 GB 26 225 GiB 2.75 TiB SSD $4.29 NVIDIA H100 PCIe 80 GB 26 225 GiB 1 TiB SSD $3.29 [...] Launch GPU instance 8x 4x 2x 1x Plan VRAM/GPU vCPUs RAM STORAGE PRICE/GPU/HR* NVIDIA B200 SXM6 180 GB 208 2900 GiB 22 TiB SSD $6.69 NVIDIA H100 SXM 80 GB 208 1800 GiB 22 TiB SSD $3.99”

    Read 2026-10-17 · official pricing · Report a correction

Cheapest GPU, per hour

Hyperstack
$0.15 per hour for an A4000 with 16GB; the A100 SXM 80GB is $1.60.
Lambda
$0.69 per GPU-hour for a Quadro RTX 6000 with 24GB; the V100 is $0.79 and the A6000 $1.09.
Sources (2) →

Largest GPU offered

Hyperstack

288GB per GPU on B300 at $7.40 an hour; B200 at 192GB is $6.00.

Lambda

180GB per GPU on B200 SXM6, from $6.69 per GPU-hour on an 8-GPU node to $6.99 on a single GPU.

Sources (2) →

Billing granularity

Hyperstack
Per minute, with enterprise-scale contracts negotiated separately.
Lambda
By the minute.
Sources (2) →

Reserved pricing

Hyperstack
Published reserved rates rather than a percentage: H200 SXM falls from $3.99 on demand to $2.79 reserved, about 30% below.
Lambda
Reserved capacity is quote-only. Committed 1-Click Clusters list $6.16-$5.54 per H100 GPU-hour and $9.86-$8.87 per B200 GPU-hour for 2 weeks-1 year, 16 to 256 GPUs.
Sources (2) →
  • GPU Pricing — Hyperstack ↗

    “NVIDIA H200 SXM 141 22 225 $3.99 [...] Reservation Pricing GPU Model Starting from Reserve NVIDIA H200 SXM $2.79 Reserve here”

    Read 2026-10-17 · official pricing · Report a correction

  • GPU cloud pricing: rent NVIDIA H100, H200, and B200 | Lambda ↗

    “Contact us for reserved capacity at our lowest prices. [...] NVIDIA HGX B200 2 weeks – 1 year 16 $9.86 Talk to our team NVIDIA HGX B200 2 weeks – 1 year 64 $9.36 Talk to our team NVIDIA HGX B200 2 weeks – 1 year 256+ $8.87 Talk to our team NVIDIA HGX B200 1 year+ 16+ — Talk to our team [...] NVIDIA H100 2 weeks – 1 year 16 $6.16 Talk to our team NVIDIA H100 2 weeks – 1 year 64 $5.85 Talk to our team NVIDIA H100 2 weeks – 1 year 256 $5.54 Talk to our team NVIDIA H100 1 year+ 16+ — Talk to our team”

    Read 2026-10-17 · official pricing · Report a correction

SOC 2

Hyperstack
SOC 2 Type 2 attested, achieved via parent company NexGen Cloud; the same page shows SOC 2 Type 1 as certified.
Lambda
SOC 2 Type II attestation, listed under the security and compliance pillar of Lambda's trust framework.
Sources (2) →
  • Secure By Design — Hyperstack ↗

    “We have achieved SOC 2 Type 2, an independent attestation of our security controls. [...] SOC 2 Type 2 achieved via NexGen Cloud, our parent company [...] SOC 2 Type I Certified SOC 2 Type II Attested”

    Read 2026-10-17 · official site · Report a correction

  • Trust | Lambda ↗

    “SOC 2 Type II attestation. ISO 27001, 27017, 27701, and 22301 certified. Strict access controls, MFA, continuous monitoring.”

    Read 2026-10-17 · official site · Report a correction

ISO 27001

Hyperstack
Not certified: ISO 27001 sits on the upcoming-certifications list, shown as "ISO 20071" (sic) in progress.
Lambda
ISO 27001 certified, alongside ISO 27017, 27701 and 22301.
Sources (2) →
  • Secure By Design — Hyperstack ↗

    “SOC 2 Type II Attested ISO 20071 In progress [...] ISO 27001 A globally recognised standard for information security management”

    Read 2026-10-17 · official site · Report a correction

  • Trust | Lambda ↗

    “ISO 27001, 27017, 27701, and 22301 certified. Strict access controls, MFA, continuous monitoring. Customer-governed access (revoke Lambda credentials anytime).”

    Read 2026-10-17 · official site · Report a correction

HIPAA

Hyperstack
Not yet: HIPAA is listed under "Coming Next", the security page's roster of upcoming certifications.
Lambda
Platform Guidelines, binding with the Cloud Terms of Service, prohibit submitting personal health information to the Services. Contractual prohibition on PHI, not a statement about a HIPAA audit or BAA.
Sources (2) →
  • Secure By Design — Hyperstack ↗

    “Coming Next Our upcoming certifications include: HIPAA A US healthcare standard for protecting sensitive patient data”

    Read 2026-10-17 · official site · Report a correction

  • Terms of Service | Lambda ↗

    “These Platform Guidelines are intended to be read together with Lambda's Cloud Terms of Service [...] (x) submit any sensitive personal data or information to the Services (including government issued identification numbers, financial account information, payment card information, and personal health information) to the Services”

    Read 2026-10-17 · official site · Report a correction

GDPR / data residency

Hyperstack
Regional data residency options across the UK, EU and other supported regions, with data centre regions in the EU, Canada and the US.
Lambda
Processes European personal data under the GDPR and relies primarily on the European Commission's Standard Contractual Clauses for EEA, UK and Swiss transfers.
Sources (2) →
  • Secure By Design — Hyperstack ↗

    “Availability of data centre regions in the EU, Canada, and US [...] Regional Data Residency Options Choose where your data resides across the UK, EU and other supported regions.”

    Read 2026-10-17 · official site · Report a correction

  • Privacy Policy | Lambda ↗

    “We rely primarily on the European Commission's Standard Contractual Clauses to facilitate the international and onward transfer of personal information collected in the European Economic Area ("EEA"), the United Kingdom and Switzerland [...] Pursuant to the European Union's General Data Protection Regulation, the UK General Data Protection Regulation (collectively, the "GDPR")”

    Read 2026-10-17 · official site · Report a correction

Encryption at rest

Hyperstack
Not server-side for Object Storage: docs tell users who need encryption at rest to encrypt client-side. The Secure By Design page separately claims data is encrypted at rest and in transit.
Lambda
All data on the 1-Click Cluster persistent file storage system is encrypted at rest using industry standard algorithms and parameters.
Sources (2) →
  • Object Storage - Hyperstack Docs ↗

    “Server-side encryption is not currently supported. Users who require encryption at rest should implement client-side encryption.”

    Read 2026-10-17 · official docs · Report a correction

  • Security posture - Lambda Docs ↗

    “All 1CC compute and management nodes have pre-configured access to a customer-specific portion of a multi-tenant persistent file storage system. The storage system is on an isolated network accessible only to management and compute nodes. All data on the storage system is encrypted at rest using industry standard algorithms and parameters.”

    Read 2026-10-17 · official docs · Report a correction

Role-based access control

Hyperstack
Role-based access control: custom user roles built from policies and individual permissions; invited members start with none until a role is assigned.
Lambda
Two account-level roles, Admin and Member; both have full access to resources, while only admins invite users, change billing and manage workspaces.
Sources (2) →
  • Organization - Hyperstack Docs ↗

    “Role-Based Access Control (RBAC) system enables you to create user roles that specify the level of access each member has. [...] new members will not have any permissions assigned by default”

    Read 2026-10-17 · official docs · Report a correction

  • Access and security overview - Lambda Docs ↗

    “When you invite new members to your Lambda Cloud account, you assign them one of two roles: Admin or Member . Both roles have full access to your Lambda resources. [...] Admins can also: Invite new users to the account or remove users from the account Modify billing information Update account details, such as the account name Manage workspaces and their memberships”

    Read 2026-10-17 · official docs · Report a correction

Private networking / VPC

Hyperstack
Each environment is allocated its own private /24 subnet; every VM in it gets a private IP from that subnet and they share one network space.
Lambda
1-Click Cluster compute nodes sit on a dedicated network segment with no inbound firewall connectivity, on a logically isolated Ethernet fabric.
Sources (2) →
  • Environments - Hyperstack Docs ↗

    “Each environment is allocated its own private subnet, expressed as a /24 CIDR block such as 10.0.5.0/24 [...] Every virtual machine you deploy into the environment receives a private IP address from that subnet. All virtual machines in an environment therefore share the same network space”

    Read 2026-10-17 · official docs · Report a correction

  • Security posture - Lambda Docs ↗

    “Compute nodes live on a dedicated network segment with no inbound connectivity from the firewall. [...] 1CC compute and management nodes share a logically isolated Ethernet switching fabric.”

    Read 2026-10-17 · official docs · Report a correction

Dedicated infrastructure

Hyperstack
Secure Private Cloud: dedicated, single-tenant infrastructure with zero shared resources, running on dedicated hardware with no shared GPUs.
Lambda
1-Click Cluster compute nodes run on single-tenant hardware with GPUs, storage, memory and NICs unshared; management head nodes are multi-tenant.
Sources (2) →
  • Secure Private Cloud for AI Workloads: Single-Tenant GPU Infrastructure | Hyperstack ↗

    “Hyperstack Secure Private Cloud provide dedicated, single-tenant infrastructure with zero shared resources and full control. [...] Your workloads run on dedicated hardware with no shared GPUs, no noisy neighbours, no cross-tenant risk.”

    Read 2026-10-17 · official site · Report a correction

  • Security posture - Lambda Docs ↗

    “1CC compute nodes run on single-tenant hardware with tenant isolation enforced using logical network segmentation. Underlying hardware resources, including GPUs, local storage, memory, and network interfaces, aren't shared with or accessible by any other customers. [...] 1CC management nodes run on multi-tenant hardware with tenant isolation enforced using hardware virtualization.”

    Read 2026-10-17 · official docs · Report a correction

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

Documented by only one.

These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing — except where we say we read the other provider's own page on a given date and it does not state it. Those rows lean, and the provider can correct them with a link.

Free tierHyperstack: No — No free plan published; prepaid accounts must hold a positive balance to create or keep resources.
Kind of free offerHyperstack: No free offer
Credit card to startHyperstack: Yes
PCI DSSLambda: Platform Guidelines, binding with the Cloud Terms of Service, prohibit submitting payment card or financial account information to the Services. Contractual prohibition on cardholder data, not a statement about a PCI DSS assessment.
Customer-managed keysLambda: Superintelligence/Supercluster page states each cluster uses AES-256 encryption at rest with unique keys under your control. Stated for single-tenant Superclusters, not for public-cloud on-demand instances.
04.

Questions this comparison answers.

Entry paid plan: Hyperstack or Lambda?

Hyperstack: Prepaid credit rather than a plan: deploying a VM needs a balance covering at least one hour of combined hourly cost - their worked example is $10.00.

Lambda: Pay-as-you-go per GPU-hour rather than a monthly plan: the cheapest self-serve instance is a 1x Quadro RTX 6000 at $0.69 per GPU-hour plus sales tax.

Egress over allowance: Hyperstack or Lambda?

Hyperstack: Free. Egress and ingress traffic are not charged; a public IP address costs $0.00672043 per hour.

Lambda: Free. Lambda states transparent pricing with no egress fees.

Should I choose Hyperstack or Lambda?

Pick Hyperstack if Steady European workloads that can commit — reserved H200 at $2.79 against $3.99 on demand is the clearest published discount in this set, and egress is free.

Pick Lambda if Renting exactly the instance shape you need — Lambda publishes 1x, 2x, 4x and 8x plans for the same card, so a single H100 is a real product rather than a fraction of a node.

Provider pages

HyperstackEuropean GPU cloud billed per minute, with published reserved rates alongside on-demand and free egress.LambdaGPU cloud from an AI hardware vendor, billed by the minute per GPU with no egress fees.

Related comparisons

CoreWeave vs HyperstackCoreWeave vs LambdaRunPod vs HyperstackRunPod vs LambdaVast.ai vs HyperstackVast.ai vs LambdaAnthropic vs DeepInfraAnthropic vs Fireworks AI

Comments

Every page here is sourced and dated.