> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/admins/pricing/cloud-streaming.md).

# Cloud Streaming

Morpheus Platform utilises 2 cloud streaming service providers (Nvidia Graphics Delivery Network and Ubitus. On-demand usage of these services is charged at $1.50 per user hour.

**Reservations**

For customers on a custom tier that are holding larger events (e.g. >2000 attendees), or when cloud streaming capacity needs to be guaranteed, reservations can be made to ensure that enough infrastructure will be available to meet demand. These reservations should be requested by the customer to MSquared at least 4 weeks in advance, and MSquared will work with its suppliers to plan the infrastructure for the event.

Infrastructure that is reserved will need to be paid for regardless of utilisation, and additional charges on top of this usage may apply.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otherside.xyz/platform-documentation/admins/pricing/cloud-streaming.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
