> For the complete documentation index, see [llms.txt](https://hugs-solutions.gitbook.io/hugs-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hugs-solutions.gitbook.io/hugs-platform/the-hugs-layer/multi-dapp-layer.md).

# Multi dApp layer

Curator is an infrastructure layer capable of hosting unlimited decentralised applications. The goal of Curator is to create an ecosystem of apps for collaborative working and crowdsourcing.

## Who can build on Curator?

Anyone will be able to create Dapps by using our software development kit. This lets developers focus on the core functionalities of their application whilst Curator processes the contributions, handles the review process, and takes care of the registration in the blockchain.

## A Web3 approach

In phase one of our development roadmap, the platform will be built on both Web2 and Web3 technology. This will accelerate our learning curve whilst moving into a fully Web3 solution. A Curator version of smart contracts will eventually exist, using Soulbound NFTs, and decentralised storage and compute.


---

# 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://hugs-solutions.gitbook.io/hugs-platform/the-hugs-layer/multi-dapp-layer.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.