Idle-time contribution
Contribute when your eligible machine is available.
Community Providers
Individuals and small teams can contribute eligible compute when it fits their day, with supported incentive paths that match their reasons for participating.
CheckReview device eligibility
ConnectSet up supported serving
ChoosePick your contribution mode
TrackReview activity and incentives
The part worth solving
Work, study and personal projects come first. Participation needs to fit the capacity and availability you can actually offer.
A clearer model
Review device eligibility and supported onboarding options. Choose idle-time contribution or a more consistent always-on setup when suitable.
Where it fits
Contribute when your eligible machine is available.
Review the relevant Windows, Ubuntu, macOS or Docker setup for your hardware.
Explore Rewards, Exchange or Mission according to program availability.
Choose your motivation
Explore the incentive paths available to eligible Providers. Review the applicable program and device requirements in your Provider workspace.
Rewards is the monetary incentive path for eligible capacity contributed to the network where available. Review its terms and attributed activity; a connected machine is not a guaranteed income.
Exchange offers tokens or AI usage value for eligible compute contribution where supported. This connects contributing to the network with using AI under the applicable Exchange terms.
Choose supported causes where Mission is available. Examples include education, environmental, healthcare, humanitarian and animal welfare initiatives.
Put your GPU to work
Choose your GPU, set your rates and find out what a fully booked schedule could be worth.
Reference modelLlama 2 7B · Q4_0
Short requests: 512 input tokens and 128 output tokens. Each GPU handles one request at a time.
Have your own benchmark? Replace both speeds. Selecting another GPU restores its reference values.
100% means requests arrive continuously throughout your selected hours. Lower it to account for idle time.
Published speeds come from community llama.cpp tests with Flash Attention off. The RTX 3080 Ti preset uses an RTX 3080 reference; it is an approximation, not a measured 3080 Ti result.
Input processing and output generation share the same time budget. Real throughput also depends on context, software and request overhead. A month is 30 days, with your weekly schedule repeated.
View benchmark sourcesAt 100% job load
Gross estimate, before electricity, fees and taxes.
This is a synthetic scenario, not a payout offer. Actual serving and Rewards depend on eligibility, demand and program terms. Exchange and Mission have their own incentives.
A practical scenario
An individual contributes available capacity and chooses Exchange where supported, receiving tokens or AI usage value under that program’s terms.
Participation depends on device eligibility and supported configuration. Review the Provider requirements before connecting hardware; no machine is automatically eligible.
Providers can explore idle-time contribution or always-on contribution. Choose the mode that fits your setup and review availability requirements for the program you select.
Provider onboarding topics include Windows, Ubuntu, macOS and Docker. Review the current instructions for the platform, hardware and serving setup relevant to your device.
They are distinct incentive paths. Rewards offers money where available, Exchange offers tokens or AI usage value, and Mission directs contribution toward supported causes. Applicable terms determine participation.
Providers contribute compute. Builders own applications and earn their configured margin on routed AI traffic. Creators own or control model assets and choose their model access terms.
Providers