Support · Runware
Will it last?
Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input D ยท 50.4/100
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
Which domain expands which factor
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Security disclosure & trust surface
The website is the trust surface: claimed SOC 2 / ISO 27001 certification, encryption in
transit, no training on inputs, and default auto-purge of generated content. A dedicated trust
centre with downloadable reports, a security.txt, and a published vulnerability-disclosure or
bug-bounty channel are not published.
Enterprise plans advertise a shared support channel, 24/7 on-call engineering and priority
routing. The breadth of self-serve and community channels, and the standard-tier support
commitments, is not publicly detailed.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
2
TransparencyAre the binding terms published, legible and independently checkable?
ModerateThe binding Terms and Privacy Policy are legible and independently re-read 2026-09-21. Held at moderate rather than strong: the DPA still returns 404, the SOC 2 / ISO 27001 reports remain badges with no readable report or dated certificate, and the confidentiality-clause correction below rests on inferred current-text absence rather than a verbatim historical diff (archives were proxy-blocked).
How this scores
Not a scored AOI dimension. For a hosted provider, transparency is whether the binding terms are published, legible and were actually read - the read/unverified evidence below, not a certification. A strong rating here must trace to a retrieved binding document.
What this means for adoptionYou partly own workloads here, but this picture improved materially on independent re-verification (2026-09-21). The models are open weights, so use, modification and exit stay fully in your hands, and self-hosting the same checkpoints avoids the hosted data terms entirely. On a hosted basis, the current binding Terms no longer grant Runware a broad licence over your inputs and outputs or deem them non-confidential - a 2026-08-06 pass found exactly that, but the current text (independently re-read) shows the customer owns Outputs outright and Runware commits not to train on your data. Load-bearing caveat: this correction is inferred from the current text's absence of the old clauses, not a verbatim old-vs-new diff (web archives were proxy-blocked). What has not improved: retention is still generic with no auto-purge or numeric window, and SOC 2/ISO 27001 remain self-asserted badges with no readable report. Use Runware with more confidence than before for ordinary workloads, but still confirm retention terms directly and request the underlying compliance reports before regulated use.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.
Terms of serviceread2026-07-26
Runware Terms of Service (Runware Ltd, UK; read 2026-07-26): the customer owns the Generations (outputs) but grants Runware a worldwide, perpetual, transferable licence over inputs and outputs; the Terms reference "storing training data and models per our pricing schedule"; UK governing law and London arbitration; termination at Runware's sole discretion; data deleted on request.
Privacy Policyread2026-07-26
Runware Privacy Policy (Runware Ltd, UK; read 2026-07-26): generic retention ("as long as necessary" / account life) with no auto-purge or opt-in-storage clause; training use not addressed; sub-processors named are only Stripe and Google Analytics; GDPR/UK GDPR referenced without naming SCCs or the EU-US Data Privacy Framework.
Securityunverified2026-07-26
Runware Trust page (read 2026-07-26, partial): "Data residency EU & US" badge with no contractual region-pinning document located; SOC 2 and ISO 27001 shown as badges only with no readable certificate or report; a separate security-disclosure page for vulnerability reporting.
Vendor announcementread2026-07-26
Runware pricing page (read 2026-07-26): pay-as-you-go usage-based pricing with representative rates; enterprise plans add dedicated capacity and custom terms.
Vendor announcementunverified2026-07-26
Runware website ("One API for all AI"): a unified API over a large catalogue of open-weight Hugging Face models run on Runware's own Sonic Inference Engine; low usage-based pricing; markets a US HQ and states data belongs to the customer (marketing framing not supported by the binding Terms/Privacy read this session).
Third-party analysisread2026-07-26
Independent press (SiliconANGLE and others, Dec 2025): Runware raised a USD 50M Series A (Speedinvest and others) to build "one API for all AI"; markets a San Francisco HQ with operations in London and 10+ countries (the binding legal entity is Runware Ltd, UK); inference pods in the US and central Europe; aims to make the broad Hugging Face open-model catalogue addressable behind one schema.
Terms of serviceread2026-09-21
Runware Terms of Service, current version (independently browser-read 2026-09-21, two fetches including a targeted negative search for the prior adverse clauses).