Alpha
Contact
Assess · Runware

Can you own it?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input D ยท 54.4/100

This page is a projection of the one entry record, the Use & modify and Transparency factors that Assess 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

Data governance - retention, ZDR & training

Training: none. Terms Sec 3 says "Runware will not use your Training Data or Trained Models to train, fine-tune, or develop Runware's own models or those of any third party", and Sec 4 (Serverless) says the same for Customer Material. The docs add that API data is never used to train, with or without zero data retention. Nothing in the current Terms permits training on ordinary inputs either.

Retention on the managed API is generic and not zero. The Privacy Policy (Sec 6) keeps data "as long as necessary" and no longer than the account lifetime, with no numeric window, no auto-purge and no opt-in-storage clause. Terms Sec 2 says Runware "does not retain your Outputs on a long-term basis", and the docs say output URLs last 7 days.

Zero data retention exists, with limits. It is an organisation-level option for enterprise accounts, switched on by Runware staff on request, applying only from that moment and covering a listed set of models. It appears in the docs and not in the Terms or Privacy Policy.

Closed partner models change the picture. The catalogue includes models licensed to Runware by their owners. When a provider runs the model, the docs say that provider's own retention terms apply to its copy (for example HeyGen keeps request data for 24 hours).

The July and August 2026 versions of the Terms carried a broad licence over inputs and outputs, and the current text has none. No archived copy of the earlier text is readable, so no verbatim comparison exists.

Data & IP ownership

Terms Sec 2: "As between you and Runware, you own your Outputs ... Runware asserts no ownership of, and claims no intellectual property rights in, your Outputs" and "Runware takes no licence in your Outputs." Trained Models and Serverless Customer Material are also yours. The only licence granted to Runware is the use of your company name and logo for marketing, revocable on request. The earlier Terms text granted a worldwide, perpetual, transferable licence over inputs and outputs.

Confidentiality is express in two places only: privately uploaded models (Sec 2, "whether or not an NDA has been signed") and Serverless Customer Material (Sec 4). Prompts and outputs on the managed Models API have no stated duty of confidence, so protection there comes from the absence of any licence.

The Privacy Policy names only analytics and payment tools (Google Analytics, PostHog, Meta Pixel, LinkedIn Insight Tag, Umami, Stripe), so the infrastructure processors that handle prompt content are undisclosed. Self-hosting the open-weight checkpoints is the cleanest route where data control matters most.

Data residency & jurisdiction

Marketing and binding text disagree. The help centre says all data is "stored on secure, EU-based servers". Terms Sec 16 says "the Services are hosted in the United States, Germany and Romania." The Terms govern.

There is no customer-selectable region and no contractual pinning, and US CLOUD Act reach is not addressed. The binding entity is Runware Ltd, United Kingdom, under English law with arbitration seated in London, but hosting is partly US and the site footer names "Runware, Inc.". Runware is a UK-jurisdiction provider with EU and US hosting and no sovereign option.

Compliance & attestations

SOC 2 and ISO 27001 appear only as footer badges with no report, number, issuer, scope, type or period, and trust.runware.ai is a JavaScript-only page that cannot be read. A DPA is available through the enterprise agreement process according to the help centre (the public runware.ai/dpa URL returns 404), and its text is unread.

The Terms (Sec 1) state the Services are not tailored to HIPAA or FISMA and bar their use where those laws apply. The Privacy Policy cites GDPR and UK GDPR without naming SCCs or the EU-US Data Privacy Framework. Request the DPA and the attestation reports before any regulated use.

Security controls

There is a responsible-disclosure programme with safe harbour and a 5-business-day acknowledgement target; Runware states it is not a public bug bounty. The Terms add a Serverless clause under which Runware may scan workloads and isolate compromised ones, and the footer lists enterprise SSO/SAML and configurable MFA. The rating stays short of strong because no attestation report or independent penetration test is readable.

Pricing & cost model

Pay-as-you-go published rates cover 420 models across image, video, audio, text and 3D, billed per generation, per second or per million tokens. Per-second serverless GPU rates (L40s to B300) come with reserved starting prices. New business sign-ups get $2 of free credit. Community models carry no public price. Enterprise plans add custom terms.

Reliability posture

A public status page exists at status.runware.ai. On 2026-11-19 it reported "fully operational" and, for August to November 2026, 99.93% uptime for Models (Third-party Models 99.98%) and 99.90% for Serverless. The Terms disclaim availability (Sec 18) and contain no SLA or service credits. Custom SLAs are advertised for enterprise plans only.

How this scores

The ownership factors this domain covers, drawn from the one entry record.

1

Use and modify freelyCan you use it freely and leave without lock-in?

Moderate

The open and community models are open-weight and portable, and Serverless runs your own containers. The catalogue also holds closed Partner Models used under the owner's licence, and the Terms leave each model's commercial-use terms to its Model Licence, which Runware says it does not vet.

How this scores (AOI sub-dimensions)
Transparency & lock-in3/5how portable it is and how easily you can leaveThe catalogue is not open-weight only.
Cost4/5how the pricing model compares and how predictable it isPay-as-you-go published rates for 420 models plus per-second serverless GPU rates with reserved starting prices, and low cost is a core part of the positioning.
2

TransparencyAre the binding terms published, legible and independently checkable?

Moderate

The Terms (updated 2026-09-29) and Privacy Policy are published and legible. The level is moderate and not strong. The DPA is enterprise-only and unread, and no infrastructure sub-processor list exists. SOC 2 and ISO 27001 are badges with no report, and trust.runware.ai cannot be read.

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. The models you choose to run from the open-weight set are yours to move or self-host. The current binding Terms (updated 2026-09-29) give you the Outputs, take no licence over your inputs or outputs, and commit not to train on your training data or serverless workloads. That conclusion rests on the absence of the older adverse clauses in the current text, since no verbatim diff exists. Four things keep the level partial. Retention on the managed API is generic, and zero retention is an enterprise add-on for listed models. Closed partner models pass your prompts to their own providers. The Terms put hosting partly in the United States. The SOC 2 and ISO 27001 claims have no report. Marketing claims of EU-only storage are contradicted by the Terms. Use the open-weight route for sensitive data, and request the DPA and attestation 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
Replaced by ev-terms-2026-11.
Privacy Policyread2026-07-26
Replaced by ev-privacy-2026-11, which carries the same Sec 6 retention text.
Securityunverified2026-07-26
Runware Trust page (partial read): "Data residency EU & US" badge with no contractual region-pinning document.
Vendor announcementread2026-07-26
Runware pricing page: 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).
Third-party analysisread2026-07-26
Press coverage (SiliconANGLE and others, Dec 2025): Runware raised a USD 50M Series A (Speedinvest and others) to build "one API for all AI".
Terms of serviceread2026-09-21
Replaced by ev-terms-2026-11.
Terms of serviceread2026-11-19
Runware Terms of Service, "Last updated: 29 September 2026" (server-rendered page, 29 sections).
Privacy Policyread2026-11-19
Runware Privacy Policy: Sec 6 keeps data as long as necessary and no longer than the account lifetime, with no numeric window or auto-purge; prompts and training are not addressed.
Documentationread2026-11-19
Runware docs, Zero Data Retention page.
Securityread2026-11-19
Help centre and status page.
Securityunverified2026-11-19
runware.ai/trust is a Trust and Safety abuse-report form with no compliance content.
Vendor announcementread2026-11-19
Runware pricing page: pay-as-you-go rate sheet of 420 priced models (206 image, 114 video, 21 audio, 66 text, 7 3D), including closed partner models (GPT, Claude, Gemini and others) beside open ones.