Support

Each submission gets a score on a 0–100 scale blending four components: peer reviews (40%), GitHub integrity (20%), self-review honesty (20%), and AI text analysis (20%). Weights can be adjusted per hackathon by the host. The full breakdown is visible on the results page for every submission.

Everyone starts at 1000. You gain ELO for placing well, for submitting quality reviews, and based on the ELO tier of the hackathon. Higher-ELO reviewers have more weight in the scoring. Nobody loses ELO for simply not winning — only for biased reviewing.

You lose your entry fee. The prize pool is still distributed among the submitters based on peer review. If you know you won't make it, back out at least 12 hours before the hackathon starts for a full refund.

From the Earnings page, request a redemption via your preferred payment method (PayPal, Venmo, Zelle, bank, gift card, or crypto). Admins verify and process your request, then respond with payment details. Every redemption is tracked with an audit trail.

Once results are posted, a 24-hour pending window opens on all payouts. Use that window to flag a review by contacting support. Reviews are AI-analyzed for sentiment and honesty; repeat offenders lose ELO and reviewing privileges.

Yes. Builder Basic ($5/mo) can host 1 hackathon per month; Builder Pro ($10/mo) can host unlimited. Free-tier accounts can only join, not host.

Yes, if you back out at least 12 hours before the build window opens. Once the hackathon is live, entry fees are non-refundable. If a hackathon is cancelled before it starts, everyone is refunded in full.