# Network Architecture

Sustainable growth of sharing platforms and marketplaces necessitates a fundamental change in the way they interact with suppliers and consumers. Solving the problems that plague the global sharing economy at scale calls for a paradigm shift from the monolithic platform driven model to a decentralised network driven approach that offers better inclusivity and interoperability.

<figure><img src="/files/v9szbnLHILHjzvrV7hsK" alt=""><figcaption><p>Rayy: Network Architecture</p></figcaption></figure>

Rayy attempts to transcend the demerits of the isolationist approach of sharing platforms where suppliers and consumers must be present on the same platform to conduct transactions. Rayy’s open network will facilitate interoperability between sharing applications, allowing their suppliers and producers to transact irrespective of which application they use.

Suppliers and sharing platforms shall have access to a gateway API and dedicated SDK's that will allow them to integrate the different components of the network. Upon successful integration, the suppliers and platforms will be able to:

* Feed their real-time inventory listings through the [Heracles Protocol](broken://pages/YHUMpBYtQIcoE19ePiT4) to reach a wider distribution network
* List their inventory on [Sharespark](broken://pages/NpwqZ8wGYcexUu2l3vuK) to reach a wider audience and execute cashback offers on their assets and services.
* Utilise [Canvas](broken://pages/pGYc99d68ThrmRDC9B0r) for user KYC and record transactional reviews in a manner that is portable across multiple platforms.

In the following sections we shall delve deeper into the individual components of Rayy.


---

# Agent Instructions: 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://docs.rayy.tech/network-architecture.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.