Alpha
All entriesContact
Inference provider

Runware

HQ
United Kingdom
Serves
4 open model families
Pricing
per-request
API
proprietary

You 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.

Do you really own it?
Partial
none·limited·partial·substantial·full
Analytical input: AOI D · 54.4/100
The four ownership factors

Floor-weighted, not averaged. Nothing is weak, but use & modify and data control are only moderate, so it misses the bar for substantial - strong on both use & modify and data control - and lands at partial.

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.
3

ReliabilityDoes it stay up and stay secure?

Moderate

A public status page shows 99.90% to 100% uptime for Aug to Nov 2026, but the Terms disclaim availability (Sec 18), publish no SLA or service credits, and no independent attestation or failover documentation exists.

How this scores (AOI sub-dimensions)
Reliability3/5whether it stays up, with an SLA and status historyA public status page exists (status.runware.ai, incident.io), showing per-component uptime for Aug to Nov 2026 (API 100%, Models 99.93%, Serverless 99.90%) and a "fully operational" banner.
Security3/5the controls protecting your traffic and dataA responsible-disclosure programme (not a public bug bounty) with safe harbour and a 5-business-day acknowledgement target, the Terms' Serverless workload-security and scanning clause, and enterprise SSO/SAML and configurable MFA (footer, marketing) support a documented posture.
Compliance2/5which independent certifications and attestations it holdsThe help centre states a DPA is available through the enterprise agreement process, and the SOC 2 and ISO 27001 footer badges are self-asserted claims.
4

Doesn't extract your dataDo the binding terms keep your data and IP yours?

Moderate

The Terms give you ownership of Outputs with no licence taken, commit to no training, and add express confidentiality for private models and Serverless. The level is moderate and not strong. Managed-API retention is generic with no numeric window, and ZDR is enterprise-only and covers listed models. Closed Partner Models send prompts to the model provider, hosting is partly US with no region pinning, and infrastructure sub-processors are undisclosed.

How this scores (AOI sub-dimensions)
Data governance3/5retention, training-on-inputs and data ownershipThe Terms (updated 2026-09-29) give no licence over Outputs, state "Runware takes no licence in your Outputs", commit not to train on Training Data, Trained Models or Serverless Customer Material, and add an express confidentiality duty for Serverless and private models.
Residency2/5where your data is processed and storedTerms Sec 16 (binding) say the Services are hosted in the United States, Germany and Romania, so an EU location exists, but there is no customer-selectable region, no contractual pinning and no documented data boundary.

How the AOI score is computed

The seven dimensions above, each scored 0 to 5, weighted and summed to the 0 to 100 headline. The score is the analytical input behind the ownership verdict, not the verdict itself.

DimensionScoreWeightPoints
Data governance3/50.2414.4
Compliance2/50.187.2
Residency2/50.166.4
Security3/50.148.4
Reliability3/50.127.2
Transparency & lock-in3/50.106.0
Cost4/50.064.8
HeadlineD · 54.4/100
Dossier coverageAssess 73%Implement 31%Use 43%Support 43%How complete our four-domain documentation is, a measure of our coverage, not of the model. Each domain links to its page.

Sources

Every rating traces to a primary document. Read means the text was verified; unverified means it is known to exist but has not yet been read.

DocumentWhat it grounds
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.