> For the complete documentation index, see [llms.txt](https://docs.miuro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miuro.ai/sustainable-creator-economy/creator-subscription-a-sustainable-web2-+-web3-hybrid-model.md).

# Creator Subscription: A Sustainable Web2 + Web3 Hybrid Model

MIURO adopts a hybrid business model combining Web2 subscriptions with Web3 token economics.

We believe a healthy ecosystem needs stable revenue sources, rather than relying entirely on token issuance.

Regular users, including creators, musicians, and content creators, will use core cloud capabilities through monthly subscriptions. This revenue will support platform operations, model training, and long-term investment into the Web3 ecosystem.

### Why Monthly Subscriptions Matter

Many Web3 projects try to operate entirely through token economics. In reality, early-stage projects often lack real demand and stable cashflow.

MIURO takes a different approach:

* Use stable Web2 revenue, including subscriptions, hardware sales, and DSP distribution fees, to support long-term platform development.
* Use Web3 token mechanisms, including $MIURO, MU, and content tokens, to capture value, incentivize nodes, and reward early participants.
* Combine hardware ownership with subscriptions: local capabilities are permanently owned through hardware, while cloud capabilities are subscribed to on demand. This prevents users from buying hardware that later becomes useless.

This model can serve traditional creators or Web2 users, while also attracting Web3-native users, forming a two-way flywheel.

### Subscription Tiers

MIURO has designed clear subscription plans for creators at different stages.

| Tier   | Monthly Price | Main Benefits                                                            | Target Users                                       | Web2 / Web3 Positioning |
| ------ | ------------: | ------------------------------------------------------------------------ | -------------------------------------------------- | ----------------------- |
| Free   |            $0 | 10 songs per month, watermark and basic features                         | Trial users and beginner creators                  | Web2 entry              |
| Plus   |         $9.99 | 100 songs per month, no watermark and 1 voice cloning slot               | Content creators and light creators                | Web2 advanced           |
| Pro    |        $29.99 | Unlimited generation, high priority and 5 voice cloning slots            | Independent musicians and professional creators    | Web2 + Web3             |
| Studio |           $99 | Unlimited generation, unlimited commercial use, API quota and team seats | Professional studios, MCNs and commercial projects | Heavy Web3 users        |

### Core Principles

* Local creation capabilities through MiuroBox are permanently owned and do not consume cloud quotas.
* Cloud generation, voice cloning, and advanced features are unlocked based on subscription tier.
* All tiers support unlimited DSP distribution, including Spotify, Apple Music, NetEase Cloud Music, and more.

### Combining Hardware and Monthly Subscriptions

Users who purchase MiuroBox hardware receive a corresponding membership period and unlock permanent free access to local Claw.

* **VOX:** Includes 1 month of Pro membership.
* **MINI:** Includes 3 months of Pro membership and permanent free access to Local Claw.
* **ORIGIN:** Includes 12 months of Studio membership, a lifetime 50% discount, and Genesis equity benefits.

This means that after purchasing hardware, heavy creators can significantly reduce their monthly subscription cost and may rely on local capabilities at nearly no long-term cost.

### How Web2 Revenue Supports Web3

MIURO’s subscription revenue, hardware sales revenue and DSP distribution fees will become important sources of stable cashflow for the platform.

This revenue will mainly be used to:

* Continuously train and optimize cloud-based songwriting models
* Pay for cloud services, infrastructure and team costs
* Support long-term incentives for node operators and early contributors
* Provide real value backing for the $MIURO token economy

We do not want $MIURO to become a token that depends entirely on speculation and inflation.

Instead, we want it to be supported by real user payments and real business revenue.

### Exclusive MU Payment Discount

MU earned through mining within the MIURO ecosystem can be used directly to pay for any subscription tier and receive a 25% discount.

This allows Web3 users, including node operators and early participants, to use value generated inside the ecosystem to offset Web2 usage costs, forming a closed loop.

### Want to Learn More?

The next chapter is about token economics


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.miuro.ai/sustainable-creator-economy/creator-subscription-a-sustainable-web2-+-web3-hybrid-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
