Stability AI Membership was introduced in December 2023 to license self-hosted core models for commercial use. For a deployment today, check the exact checkpoint's terms and Stability's current Community or Enterprise licensing route. Hosted API usage is billed separately through the Developer Platform. Announcement, dated archive, licensing overview, API pricing
What are the key facts about Stability AI Membership?
| Field | Verified detail |
|---|---|
| Developer | Stability AI. Announcement |
| Released | December 14, 2023; the company's dated news archive records the announcement. News archive |
| Type | Commercial licensing program for self-hosted core models. Announcement |
| Size or parameters | Not applicable: the program covers models rather than defining a model architecture. Announcement |
| License and access | Historical membership tiers; current eligible core-model use is described by the Community and Enterprise licensing routes. Announcement, overview |
| Where it runs | Licensed models can be deployed in the customer's environment; the announcement separately identifies API and cloud-provider access. Announcement |
What did Stability AI Membership cost and include?
The original program offered a named route for commercial self-hosting across multiple model types. That distinction helps a team identify the permission it needs before choosing an inference interface. Announcement
The launch tiers were Non-Commercial, Professional, and Enterprise. Professional was advertised at $20 USD per month, while Enterprise used custom pricing; these are historical launch terms. Announcement
Use that history to understand the program's purpose. For an actual purchase decision, record today's model name, the governing agreement, and the deployment arrangement in the same document.
The current licensing overview describes free qualifying use of covered core models below its stated annual-revenue threshold of $1 million. Larger commercial organizations are directed to Enterprise licensing. Licensing overview
This creates a concrete planning question: which agreement covers your organization and the exact checkpoint? Answering that is more useful than choosing a subscription name from a general model discussion.
Separate your project estimate into permission, compute, and operations. Give each item an owner and a source, so a missing hosting budget cannot be mistaken for a missing license fee.
Which licensing conditions should you check before deployment?
Coverage is model-specific. The membership announcement says some earlier releases have separate licenses, so the phrase Stable Diffusion alone does not identify the terms governing a particular file. Announcement
For example, the SDXL base repository links CreativeML Open RAIL++-M. Read that agreement when using the SDXL checkpoint, rather than automatically applying a newer core-model agreement. SDXL license
A license agreement and a compute service also have separate scopes. Stability's developer platform documents metered API credits; the permission to self-host does not specify your server's throughput. API pricing
The Community License Agreement includes registration requirements for commercial use, distribution obligations, attribution, and use restrictions. Read the complete agreement before deciding how to distribute a product. Agreement
Keep a copy of the accepted terms with the model revision and approval record. This is a practical documentation habit: a future teammate should be able to identify the same artifact without reconstructing your search.
How do you choose a Stability AI license and deployment route?
Choose the artifact and deployment route
Start by writing down the exact repository or API model identifier. Include the version, the component you will download, and whether your users will access a hosted endpoint or a service you operate.
Next, open the model card's license link. If it points to Stability's current licensing page, follow that route; if it contains a separate agreement, read the separate agreement before proceeding.
The Stable Diffusion licensing companion provides another entry point into this model-specific distinction.
For a covered Community License deployment, review the organization's eligibility and commercial registration requirements. Use the Enterprise contact route if the current licensing page directs your organization there. Overview, agreement
Arrange model licensing through Stability's website and licensing contacts before setting up the runtime. Licensing overview
Prepare the runtime separately
After resolving access, follow the selected model's own installation instructions. The official generative-models repository documents environment setup and inference demos for the checkpoints it supports. Reference repository
For example, once that repository and its required environment are installed, this command starts its documented image demo. Download and place a supported checkpoint as instructed before running it. Reference repository
streamlit run scripts/demo/sampling.py
This is a model-runtime command. Your licensing record remains a separate project document, so retain both the installation notes and the terms under which the checkpoint was obtained.
For a graphical workflow, the ComfyUI guide can help organize the generation process after model selection.
Build an estimate that matches the job
For self-hosting, list the machine, storage, expected operating hours, and maintenance responsibilities. For API usage, list the selected operation and its published credit charge. API pricing
Keep observed retry rates in your own estimate instead of treating every generated image as a finished deliverable. A rejected composition still belongs in the project's generation log and cost calculation.
The cloud GPU pricing page is a useful companion when comparing infrastructure. Use the same workload assumptions for each candidate so the comparison remains meaningful.
How does self-hosted licensing compare with API access?
| Route | What you arrange |
|---|---|
| Stability self-hosted model access | The applicable model license and a runtime you operate. Overview, repository |
| Stability Developer Platform | Hosted API operations with documented credit pricing. API pricing |
| SDXL under its attached license | Access governed by the SDXL artifact's separate agreement. SDXL license |
Choose among these routes by listing the responsibilities your team can support. Consider who handles installation, service availability, model updates, and the record of generated assets before selecting a deployment.
What else should you know about Stability AI Membership?
Does the original membership price still determine my bill?
Stability AI Membership's $20 monthly Professional price belongs to its 2023 launch announcement. Consult the current licensing route and any accepted agreement for the project you are starting now. Announcement, overview
Does licensing a model include API credits?
Stability documents its developer platform as a separate access route with credit-based pricing. Budget for the API operation you select using that platform's pricing documentation. API pricing
Can I use a covered model commercially for free?
Stability AI's Community License provides free qualifying commercial use of covered models, with registration required. The agreement ends that grant if you or your affiliates individually or together exceed $1 million in annual revenue; review its distribution and attribution conditions too. Agreement
Should every Stable Diffusion checkpoint use the same agreement?
Check the exact checkpoint's attached license. SDXL's published agreement illustrates why a family name alone is insufficient to determine the terms. SDXL license
Sources
- Stability AI Membership announcement
- Dated Stability AI company news archive
- Current Stability AI licensing overview
- Stability AI Community License Agreement
- Stability Developer Platform pricing
- SDXL license
- Stability AI reference implementation
Top comments (0)