> For the complete documentation index, see [llms.txt](https://docs.onlydust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onlydust.com/overview/how-do-we-flow.md).

# How do we flow

A common question we get: how does OnlyDust make money?

The answer is simple: **sponsorships**.\
\
We partner with companies and organizations who want to support open source and reach developers like you. They fund the platform - and we put that funding to work where it matters.

#### Where the Money Goes

We reinvest the majority of sponsorship revenue back into the open source community.

* In 2024, 72% of our income was distributed directly to maintainers and contributors for their work (PR activity and onboarding activity).
* In 2025, this amount goes through our 3-month grant program, supporting long term contributors and maintainers across the space.
* Every month, we add $15,000 of our own budget toward:
  * Exclusive merch
  * Travel and conference grants
  * Event tickets
  * And other meaningful rewards for active contributors

Our goal is to make contributing to open source recognized, supported, and rewarding -not just technically, but financially and personally too.\`


---

# 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://docs.onlydust.com/overview/how-do-we-flow.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.