> For the complete documentation index, see [llms.txt](https://parad0xlabs.gitbook.io/parad0xlabs-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://parad0xlabs.gitbook.io/parad0xlabs-docs/nebula-media-proof-carrying-media/make-money.md).

# Monetize

Media is where the money is, because media is where the *costs* are. Storage and bandwidth (egress) are among the largest line items for any platform that serves video. Nebula sells against that bill directly — as **open-core**: MIT code, with a managed tier for scale.

***

## The core pitch: smaller files, same quality, proven

Every percent smaller at equal quality is a percent off storage and a percent off every byte you ever serve. With four codecs (including VVC and hardware VideoToolbox) picking the smallest option per clip, the savings on a real catalog are material — and because the quality is *measured and proven*, nobody has to choose between "cheaper" and "looks fine." You get a number that says it's both.

***

## The open-core model

| Tier                     | What it is                                                                                                                          | Who                               |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- |
| **Public / free**        | MIT-licensed pipeline + a free web tool on parad0xlabs.com                                                                          | creators, developers, small teams |
| **Managed / enterprise** | usage-based throughput, dedicated deployments (private cloud / on-prem / air-gapped), SLAs, compliance & audit support, integration | platforms and orgs at scale       |

The code is **MIT and free** — that's the top of the funnel and the trust builder. You make money on what genuinely costs money to run: **hosting, sustained throughput, dedicated/air-gapped deployments, support, and SLAs.** It's the Red Hat shape — open code, paid operations — not closed software. Enterprise pricing is usage-based and deployment-dependent.

***

## Who pays, and for what

| Buyer                     | The pain                                         | What they buy                                                |
| ------------------------- | ------------------------------------------------ | ------------------------------------------------------------ |
| Streaming / UGC platforms | Egress and storage dominate the cloud bill       | Managed encoding that cuts both, with a provable quality bar |
| Creators / media teams    | Big files, quality anxiety                       | Free pipeline + provenance receipts                          |
| Archives / rights holders | Need provably intact, authentic masters          | Verified masters with an on-chain trail                      |
| Compliance / anti-fraud   | "Is this the real file or a tampered re-encode?" | Proof-carrying media — authenticity by receipt               |

***

## How it plugs into the flywheel

Nebula emits the same on-chain proof receipts the rest of Web0 anchors — so a platform paying for encoding is also generating x402-settled proof receipts, which feed the protocol fee and the NULL war chest. Media is a huge, cost-sensitive market with a built-in reason to want provenance (deepfakes, rights, authenticity). Open-core means adoption is frictionless (MIT, free to start) while the revenue comes from the scale and guarantees that only a managed service provides.

***

**Note:** Nebula is **alpha**, and the performance numbers are content-dependent — measured on specific media, not promised for every source. The pipeline is MIT and open; the paid tier is operations and scale, not locked code. We'd rather you run the benchmarks yourself than take a percentage on faith.


---

# 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:

```
GET https://parad0xlabs.gitbook.io/parad0xlabs-docs/nebula-media-proof-carrying-media/make-money.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.