> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gamerhash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Business model

> Where GamerHash revenue comes from — pay-per-request compute, direct AI partnerships and store margin — and what it funds: payouts for GPU work and running the platform.

The platform earns when AI jobs run on the network. That revenue funds two things — **payouts to the people sharing GPU power** and **platform operations**. Nothing else.

The part worth reading twice: **those payouts are funded by compute revenue — what buyers actually paid for AI jobs — not by token emissions.**

## The business at a glance

|                           |                                                |
| ------------------------- | ---------------------------------------------- |
| **Founded**               | 2017 — Poland                                  |
| **Registered users**      | 820,000+ worldwide                             |
| **Network**               | thousands of active GPUs                       |
| **Buyer access**          | OpenAI-compatible REST API + official n8n node |
| **Developers registered** | 10,000+                                        |
| **Store catalogue**       | 600+ digital items                             |

Registered users are platform accounts, not a GPU count. The network itself is powered by thousands of active GPUs.

## Revenue sources

<CardGroup cols={3}>
  <Card title="Pay-per-request compute" icon="code">
    Developers and applications pay per request for AI jobs — text, image, video, embeddings, transcription.
  </Card>

  <Card title="Direct AI partnerships" icon="handshake">
    Bulk compute agreements with AI projects, agencies and platform integrations.
  </Card>

  <Card title="Store margin" icon="cart-shopping">
    The GamerHash Store earns a margin on digital goods — games, game keys, gift cards, prepaid codes.
  </Card>
</CardGroup>

The first two are paid by buyers of AI compute. The third comes from the spend side: earnings used inside the platform instead of taken out.

## Where the revenue goes

<Frame>
  <img src="https://mintcdn.com/gamerhash/xVp-mW9DIyqS08n6/images/revenue-flow.png?fit=max&auto=format&n=xVp-mW9DIyqS08n6&q=85&s=fa7daaa4ef2a80d675aa79c794a50ac2" alt="Revenue flow: three revenue sources — pay-per-request compute, direct AI partnerships and store margin — feed one platform revenue pool, which funds two things: payouts in GUSD for completed AI jobs, and platform operations (infrastructure, development, support)." width="1600" height="785" data-path="images/revenue-flow.png" />
</Frame>

<CardGroup cols={2}>
  <Card title="Payouts for GPU work" icon="microchip">
    Every completed AI job credits the earnings balance of the machine that ran it, in GUSD.
  </Card>

  <Card title="Platform operations" icon="server">
    Infrastructure, development and support — the cost of keeping the network running.
  </Card>
</CardGroup>

How the two shares compare is not published — no percentage, no range, no formula.

## What buyers pay

Buyers pay per request. Access is one OpenAI-compatible REST API plus an official [n8n](https://n8n.io) node, so an application or an automation workflow can send AI jobs to the network without building infrastructure for it. 10,000+ developers are registered.

## What the people sharing GPU power get

You install the app and opt in; the app takes the jobs on its own. There is no queue to watch and nothing to accept by hand — this is passive income from a machine that is switched on anyway.

* **Earnings in GUSD** — credited as AI jobs complete on your GPU. GUSD is counted 1:1 with the dollar inside the platform. It is not a token and not a stablecoin — it is an earnings balance in your account.
* **Payout in the asset you choose** — take the balance out as USDC to any BNB Chain address (a Binance deposit address, MetaMask on BSC, any BEP-20 wallet), or as GHX onchain on Ethereum, BNB Chain or Solana.
* **Or spend it in the Store** — 600+ digital items in the [GamerHash Store](https://gamerhash.com/en/shop): games, Steam keys, gift cards, prepaid codes.

<Note>
  Payouts leave the platform in crypto only — as USDC or as GHX. There is no transfer to a bank account.
</Note>

## Outside the revenue model

Two things sit next to the revenue model and are not paid for out of it:

* **The monthly season rewards.** The GHX handed out each season is provided by GamerCoin under a cooperation arrangement — it is not funded from platform revenue. The activity points (GHXP) participants lock decide where each of them places in the season ranking, and each place carries a defined reward; none of it changes what a single AI job pays.
* **GHX itself.** The ecosystem token is documented and operated on its own site, outside the GamerHash AI platform.

<CardGroup cols={2}>
  <Card title="Activity points (GHXP)" icon="bolt" href="/ai/ghxp">
    How points accrue every minute the app runs, and how a monthly season ranking pays out.
  </Card>

  <Card title="GamerCoin: token documentation ↗" icon="book" href="https://docs.gamercoin.com">
    GHX is documented and operated outside this platform.
  </Card>
</CardGroup>

## Why the model holds up

Payouts are funded by what buyers pay for compute, not by issuing a token. What there is to distribute follows how much compute the network sells.

Whether to spend the balance in the Store, take it out as USDC, or take it out as GHX is a separate decision from whether the machine is earning at all.

<Note>
  Earnings depend on demand on the network. There is no fixed or promised rate.
</Note>

## Next

<CardGroup cols={2}>
  <Card title="Earning model" icon="coins" href="/ai/earning">
    What the app pays for and what determines how much a machine earns.
  </Card>

  <Card title="GamerHash Store" icon="cart-shopping" href="/apps/store">
    600+ digital items you can pay for with your earnings balance.
  </Card>

  <Card title="Wallets" icon="wallet" href="/platform/wallets">
    What sits in your account, and how a payout leaves the platform.
  </Card>

  <Card title="Developer API" icon="code" href="/deapi/overview">
    The buyer side — OpenAI-compatible REST plus an official n8n node.
  </Card>
</CardGroup>
