Comparison Overview
Modal

Modal
New York City, New York, US, 10038
Last Update: 10/08/2026
Customers rely on Modal for instant GPU access, sub-second container starts, and native storage, so it's simple to serve low-latency inference, fine-tune models, and access production-ready sandboxes at scale. Every era of computing came with new workloads that previou...

DoorDash
San Francisco, US
Last Update: 07/10/2026
At DoorDash, our mission to empower local economies shapes how our team members move quickly and always learn and reiterate to support merchants, Dashers and the communities we serve. We are a technology and logistics company that started with door-to-door delivery, and...
Compliance Ranges Comparison

Modal







DoorDash






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
Modal has 4.76% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
DoorDash has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Modal (X = Date, Y = Severity)
Modal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DoorDash (X = Date, Y = Severity)
DoorDash cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Modal

DoorDash
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.