# About

Fleek Protocol is an open-source Edge Computing Platform to accelerate the development and execution of decentralized Web Services.

The system builds on a distributed network of nodes, where services run within a fair and incentivized ecosystem constituted by an open community of developers and operators who can operate nodes, build services that use the network’s resources, or consume Fleek Protocol services on the Edge.

Applications, platforms and protocols build and utilize decentralized services on Fleek Protocol to optimize performance and reduce dependency on centralized cloud providers. Developers can build faster and launch better products by offloading parts of the stack to the Edge to focus on core features.

### Roadmap <a href="#roadmap" id="roadmap"></a>

We aim to bring computation to where demand is. You can find Fleek Protocol's public roadmap here.

### Need help? <a href="#need-help" id="need-help"></a>

Be part of a community! Join the Fleek Protocol telegram if you want to ask a question, require help or exchange ideas.

### Found an issue? <a href="#found-an-issue" id="found-an-issue"></a>

Issues can be reported in the correspondent repositories here and any other reports by messaging us on telegram.


---

# 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.fleek-protocol.com/about.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.