Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The agreement states that the Community License is revocable upon violation of its terms, and frames revocability as necessary for Stability AI's legal compliance, safety promotion, and IP protection.
This analysis describes what Stability AI's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes that access to the Core Models and Derivative Works under the Community License is contingent on ongoing compliance with license terms, and that violations may result in license revocation. The document does not specify cure periods, notice requirements, or procedural steps prior to revocation in the text provided.
Interpretive note: The document does not specify notice requirements, cure periods, or procedural steps prior to revocation, creating ambiguity about the operational consequences and enforceability of this provision across jurisdictions.
Under the Community License terms, Stability AI reserves the right to revoke the license upon violation of its terms. The agreement does not specify in the provided text whether users receive advance notice or a cure period before revocation is effective, which may affect organizations that have built production workflows on these models.
Cross-platform context
See how other platforms handle Revocability of Community License and similar clauses.
Compare across platforms →Monitoring
Stability AI has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
"Like most agreements, the Community License is revocable if you violate its terms. Otherwise, Stability AI cannot comply with its own legal obligations, promote the safe use of our technology, and protect the hard work and considerable resources that we have invested into developing AI tools for our community.Excerpt from Stability AI's Model License
(1) REGULATORY LANDSCAPE: Revocability provisions in software and model licenses engage general contract law principles across jurisdictions. In the EU, consumer-facing revocability clauses may interact with the Digital Content and Digital Services Directive, which establishes baseline protections for digital content access. For business users, applicable law will govern what notice and cure rights, if any, apply absent explicit contractual specification. (2) GOVERNANCE EXPOSURE: Medium. The absence of specified cure periods or notice requirements in the document creates operational uncertainty for organizations that have integrated Core Models or Derivative Works into production systems. Revocation without advance notice could disrupt deployed services. (3) JURISDICTION FLAGS: EU and UK consumer protection frameworks may limit the enforceability of revocability clauses against individual consumers without adequate notice. California's consumer protection statutes may also be relevant for individual users. For business users, the enforceability of no-notice revocation will depend on governing law, which is not specified in the document text provided. (4) CONTRACT AND VENDOR IMPLICATIONS: Organizations relying on Stability AI models for commercial products should assess business continuity risk associated with potential license revocation. Downstream B2B contracts should include appropriate representations and warranties regarding the stability of the underlying model license, and may warrant inclusion of contingency provisions. (5) COMPLIANCE CONSIDERATIONS: Legal teams should document their compliance posture under the Community License terms, including revenue monitoring and acceptable use assessments, to establish a record demonstrating good-faith compliance in the event of a license dispute. Organizations should also evaluate whether their vendor contracts include provisions addressing the consequences of upstream license revocation.
This provision establishes that access to the Core Models and Derivative Works under the Community License is contingent on ongoing compliance with license terms, and that violations may result in license revocation. The document does not specify cure periods, notice requirements, or procedural steps prior to revocation in the text provided.
Under the Community License terms, Stability AI reserves the right to revoke the license upon violation of its terms. The agreement does not specify in the provided text whether users receive advance notice or a cure period before revocation is effective, which may affect organizations that have built production workflows on these models.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Stability AI.