> For the complete documentation index, see [llms.txt](https://whitepaper.gravityhub.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.gravityhub.xyz/onboarding-strategy/onboarding-developers.md).
# Onboarding Developers
Gravity Hub has a clear developers base growth strategy in place:
* **Revolutionary Game Publishing Platform:** Gravity Hub redefines game publishing by offering feature parity with Steam. Games published on Steam can now be seamlessly ported to Gravity Hub with minimal effort and no compromises.
* **Transparent and Secure Business Practices:** Gravity Hub ensures trust and security through blockchain technology, eliminating the possibility of sales report tampering. Developers no longer need to rely on platform owners; our decentralized blockchain network safeguards them against fraud. Collaborations between developers and publishers also benefit from Gravity Hub's advanced trustless features.
* **Advanced Developer Marketing Tools:** Gravity Hub is engineered to provide developers with cutting-edge marketing tools to thrive in today's competitive marketplace.
* **Developer-Centric Practices:** Gravity Hub prioritizes developers by offering a larger revenue share, enhanced data analytics, and facilitating direct relationships with gamers.
* **Expedited Payouts:** Unlike traditional publishing platforms that typically pay out 30 to 60 days after sales, Gravity Hub offers faster sales payouts. This enables developers to maintain sales momentum at launch by reinvesting in real-time marketing campaigns directly from sales.
\
---
# 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://whitepaper.gravityhub.xyz/onboarding-strategy/onboarding-developers.md?ask=&goal=
```
`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.