> For the complete documentation index, see [llms.txt](https://boost.filecoin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boost.filecoin.io/deployment.md).

# Components

Overview of Filecoin Storage Provider (SP) components and how Boost fits in an SP stack

The **Lotus** stack is responsible for running a Filecoin full chain node, handling sector lifecycle, storing sectors, sector sealing, sector proving, handling wallets, and more. You can read about the Lotus components at <https://docs.filecoin.io/storage-provider/architecture/lotus-components/>

| Component        | Description                                                               |
| ---------------- | ------------------------------------------------------------------------- |
| **lotus**        | Lotus Daemon following the Filecoin chain                                 |
| **lotus-miner**  | Lotus Miner handling sector storage, jobs scheduling, etc.                |
| **lotus-worker** | Lotus Worker handling various types of jobs (PC1, UNS, PC2, C1, DC, etc.) |

The **Boost** stack is responsible for handling storage and retrieval requests, transferring data, indexing data, announcing data to network indexers, and ensuring that clients can retrieve their data once it is stored on the SP's infrastructure.

| Component           | Description                                                                                                                          |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **boost**           | Boost client-side executable that can be used to send a deal proposal to a Boost Storage Provider.                                   |
| **boostd**          | Boost SP daemon handling storage deals processing, Boost UI server, GraphQL server, etc.                                             |
| **booster-http**    | Serve blocks and files over HTTP                                                                                                     |
| **booster-bitswap** | Serve blocks and files over Bitswap                                                                                                  |
| **boostd-data**     | Data service handling Boost SP daemon state, and providing interface to the Local Index Directory (hosted on YugabyteDB, or LevelDB) |
| **yugabyted**       | YugabyteDB backend for Local Index Directory                                                                                         |


---

# 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://boost.filecoin.io/deployment.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.