Claim $70 in
Nosana Compute Credits
Qualified participants in the Decentralize AI Hackathon can access Nosana compute credits to build, test, and deploy AI workloads.
Eligibility requirements
Who can claim credits
Valid AI Project Proposal
Submit a clear, well-scoped AI-related project proposal that leverages decentralized infrastructure.
Deploy on Nosana
Intend to deploy or test your AI workloads on the Nosana decentralized GPU network.
One Claim per Team
A single representative submits on behalf of the entire team. Duplicate submissions are not approved.
Note: These credits must be used exclusively for Decentralize AI Hackathon submissions. Builders may either extend an existing project using Nosana credits or create an entirely new project for the hackathon. Incomplete or duplicate submissions may not be approved.
Credit claim form
Submit your claim
Share your project details. Approved teams receive Nosana credit access instructions by email.
Usage Guide
Here’s How You Can Use Your Credits Efficiently
Deployments on Nosana are by default set to using an “Infinite Strategy”, with a default “Container Timeout” of 6 hours and a “Replica Count” of 1.
This mean that one instance will be created for you, and will continue running until your credits run out. Depending on the GPU market you have chosen, your credits will run out quickly.
With an NVIDIA 5090, at $0.48/h, this will cost $350/month.
With only $70 worth of compute credits, you’ll need to use it efficiently for the hackathon.
In order to do so, when creating your deployments, on https://deploy.nosana.com/deployments/create
- 1Click the “configure” button
- 2Go to the “Deployment Configuration” tab
- 3Select “Simple” from the “Deployment Strategy” drop down list
- 4Keep the “Replica Count” at 1
- 5Choose your desired “Container Timeout”
- 6Click “Save Changes”
- 7Last but not least choose a GPU market that fits your needs
Open in Nosana
deploy.nosana.com/deployments/create
Because billing is based on actual uptime, you only pay for the hours your instance is running. To avoid burning through credits, stop instances when they’re idle or lower the Container Timeout.
This should help you stretch those $70 as long as possible!