Team
- TARA workflow (STRIDE + 5 automotive)
- 3 projects (Starter scope)
- Email support (48h response)
- ISO 21434 work-product templates
- EDP burndown eligible
Procure ThreatZ through the AWS Marketplace listing for EDP-eligible billing, pre-vetted contract terms, and fast vendor onboarding. The Marketplace handles billing and contracting only — every ThreatZ tenant deploys to your private cloud or on-premise environment, with your data plane under your control.
Team and Pro are sold through AWS Marketplace under VxLabs GmbH. Enterprise programs — private cloud, on-premise, air-gapped, custom SLAs, unlimited projects — are sold direct.
12-month contract on AWS Marketplace; 3-day refund window for minimal-usage cancellations. AWS Private Offers available for negotiated pricing, multi-year terms, or custom support — contact us to scope.
Each one collapses a procurement cycle from months to days.
F500 OEMs and Tier-1s sit on multi-year AWS Enterprise Discount Programs. 100% of Marketplace purchases count against that committed spend. For a $32K Pro plan, this is the single biggest unlock — you're spending money you've already paid for. Shortcuts the "new vendor" budget fight.
AWS Marketplace SaaS contracts use AWS's standard CLUA, which most enterprise legal teams have already redlined once. Skipping a 6–12 week MSA / DPA / InfoSec review on a $32K SKU is enormous — legal won't even open the file under the materiality threshold.
Creating a new supplier at a VW / Stellantis / Bosch is a 3–6 month process: tax forms, sanctions screening, ESG questionnaire, cyber-supplier audit, banking setup. AWS is already an approved supplier; ThreatZ rides that rail. Invoice from AWS, not from VxLabs GmbH.
Several large OEMs — including Ford, GM, Stellantis IT, and increasingly BMW / Mercedes cloud-procurement teams — have an internal rule: if it's on AWS Marketplace under $X, it MUST be bought there. Not optional. Selling outside the channel triggers an exception request.
AWS Marketplace classifies any subscription not sold as a downloadable AMI under the "SaaS" billing category — that is AWS's procurement taxonomy, not our deployment topology. ThreatZ tenants deploy to your environment.
What lives on AWS: the Marketplace listing, the 12-month contract, the EDP burndown record, the AWS-generated invoice, and AWS's vendor-of-record relationship with you.
What does NOT live on AWS's multi-tenant cloud: your vehicle data, your ARXML, your MATLAB System Composer models, your TARA work products, your ECU bindings, your incident telemetry, your CIA / DIA evidence. All of that stays in your private cloud, your on-premise environment, or your air-gapped deployment — same as for any Enterprise customer.
This holds the sovereignty pillar that OEM and Tier-1 cybersecurity programs require. The OEM SVP Engineering who vetoes multi-tenant cloud for vehicle data is not blocked by the AWS Marketplace listing — because vehicle data never enters AWS's multi-tenant cloud through ThreatZ.
Procure the Team or Professional plan through AWS Marketplace for the fast procurement rail — or talk to us about Enterprise deployment with private cloud, on-premise, or air-gapped tenancy. Both paths run the same 8-workflow platform with ISO 21434, R155, GB 44495, and EU CRA coverage.
Same ThreatZ, two deployment modes: AWS Marketplace for authoring and pilots, private cloud or on-premise wherever vehicle data lives. Mutual NDA available; not required for the initial scoping call.