Is This Hackathon Legit? Red Flags and How to Check

Most hackathons are run in good faith. But a few are marketing exercises, lead-generation forms or outright traps, and a couple of well-known disputes show that even big names can fumble the details. The cost of a bad one is a weekend of unpaid work, plus whatever rights you hand over.

Here are the warning signs, and a quick way to check each one.

Red flag 1: you have to pay to enter

A hackathon exists to draw builders to a sponsor. When the entrant pays, the money flows backwards. There are exceptions: an in-person event may charge a modest ticket to cover food and venue, and a paid conference may bundle a hackathon in. The test is whether the fee is tied to something real you receive.

Be wary of "registration fees," "verification fees," "judging fees" or a required purchase of a product or token. If the prize pool is advertised as large and the entry costs money, ask who is funding the prizes.

Red flag 2: vague judging

Good events say how they judge. Bad ones say "judged by our panel of experts" and nothing else. Look for:

• Written criteria, ideally with weights.
• Named judges or at least their organizations.
• A stated process: scoring rounds, who decides ties, and when results come out.
• A way to see results afterwards.

Scoring disputes and prizes that never arrive are the two complaints you hear most after a badly run event. If the rules leave the organizer room to withhold awards, assume they may.

Red flag 3: an IP grab

Read the clause about ownership. You want to keep your work and grant the organizer a limited right to show it. Be careful with wording that:

• transfers ownership of your submission to the sponsor;
• gives the sponsor an unlimited, perpetual license to use it commercially without payment;
• claims rights to your ideas, not just your code;
• covers anything you ever build with their product.

If a contract-style document says you agree to all of this, and the prize is small, you may be giving away more than you get. Our choosing checklist covers the three common IP setups.

Red flag 4: prizes that say "up to"

"Win up to $100,000" is not a prize. It is a ceiling. Look for the actual table: how many prizes, what each one is worth, and what form each is paid in. Also watch for:

• prize pools that include "opportunities," "exposure" or "mentorship" in the total;
• credits and discounts counted as if they were cash;
• payment in tokens with lock-ups or vesting;
• the right to cancel or reduce prizes if entries are "insufficient."

Add up only the cash. That's the number to compare, which is what we do on the odds page when we work out prize per entrant.

Red flag 5: no past winners

If an event has run before, it should be easy to find who won and what they built. If it's a first edition, look at the organizer's other events. A series with no winners page, no photos, no project gallery and no one who'll vouch for it deserves suspicion. A first-time event is not automatically bad, but you are taking a risk, and the prize should reflect that.

Other warning signs

• No official rules page. Serious events have one. Without it, nothing binds the organizer to anything.
• No named organizer or company. You should know who is on the hook.
• Pressure. Countdown timers, "only 10 spots left" and demands for fast payment are sales tactics.
• Requests for sensitive data. Asking for ID or bank details at sign-up, before anything is won, is not normal. You may be asked for tax or identity paperwork after winning; that's different.
• Unexplained sponsor. If the sponsors are logos with no links, check they exist.

How to check, in ten minutes

1. Find the official rules and read the sections on eligibility, judging, prizes and IP.
2. Search the event name with words like "complaint," "scam," "prize not paid" and "results." Read the forum threads, not just the first page.
3. Search the organizer and look at previous events. Did winners get announced? Did anyone say they were paid?
4. Look at the winners. Do they have real profiles and public projects?
5. Check the sponsor. Does the sponsor's own site or social account mention the event?
6. Ask a question. Email the organizer something specific, like how prizes are paid and when. A real organizer answers; a fake one dodges.
7. Look at the timeline. A real event gives dates for submission, judging and announcements.

Keep screenshots of the rules and prize page when you enter. Pages change, and a record helps if there's a dispute.

A note on trust, and on us

We list events and rank them by prize per entrant, but we do not vouch for any organizer. The numbers tell you how crowded a prize pool is, not whether it will be paid. That judgment is yours to make using the steps above. If you want events with fewer restrictions, the open to everyone list is a good place to start, and then run the checks. Once an event passes, the value math is the next question.

When in doubt, skip it. There is always another hackathon next month.

Search 405 live hackathons