01
Find
Upcoming hackathons in one list, filtered by format and source, each linked to its own page and to where hackbrief found it. Imported daily from 3 sources whose terms allow it.
Browse the listLoading upcoming hackathons…
Open source · for students and early-career developers
Pick the right hackathon.Then play to win.
hackbrief lists hackathons from the sources that allow it, and turns any event's rules into a plan: when it closes, what to hand in, and where the judges' points are.
The rules, as pastedFictional
# Lagoon Build Weekend 2027 Organised by the Lagoon Dev Collective. A 48-hour online hackathon for builders of tools that help small businesses. ## EligibilityOpen to students and early-career developers aged 18 or over. Employees of the organisers are not eligible. ## TeamsTeams of up to 4 members. Individuals are welcome too. ## Key dates- Registration closes: 2027-03-05- Hacking starts: 2027-03-12 18:00 UTC- Submission deadline: 2027-03-14 18:00 UTC- Winners announced: 2027-03-20 ## Judging criteria- Technical quality (30%): does it work, and is the code clear?- Innovation (20%): is the idea new?- Impact (25%): would a small business use it?- Presentation (25%): is the demo clear? ## What to submit- A link to a public GitHub repository with a README.- A demo video of no more than 3 minutes.- A short slide deck. ## Prizes- First place: $3,000- Second place: $1,500- Best use of open data: $500
The brief
Lagoon Build Weekend
Deadline
Sunday 14 March 2027
18:00 UTC
Team and prize
- Team
- 1 to 4 people
- Solo
- You can enter alone
- Top prize
- $3,000
Where the points are
- Technical qualityFocus30%
- ImpactFocus25%
- PresentationFocus25%
- InnovationSteady20%
Technical quality is 30%: spend the time on a reliable demo path and clear code, not on extra features.
To hand in
- Link to a public code repository
- Demo video, at most 3 minutes
- Slide deck
- README
Read 931 charactersNothing sent, nothing stored
106 platforms' terms read before a single listing was collected
See the full list- Devpost: Not collected
- MLH: Asked first
- Devfolio: Asked first
- Hack Club Hackathons: Used
- Unstop: Asked first
- HackerEarth: Asked first
- Hack2skill: Asked first
- Hackathon.com: Asked first
- Hackster.io: Used
- TAIKAI: Asked first
- Agorize: Asked first
- AngelHack: Not collected
- BeMyApp: Linked to only
- Hackalist: Used
- HackHQ: Used
- HackTrack-EU: Linked to only
- dev.events: Asked first
- DoraHacks: Linked to only
- ETHGlobal: Asked first
- Colosseum: Asked first
- Superteam Earn: Asked first
- HackQuest: Asked first
- Encode Club: Asked first
- AKINDO: Asked first
- Gitcoin: Not collected
- Kaggle: Used
- lablab.ai: Asked first
- Zindi: Asked first
- DrivenData: Used
- AIcrowd: Asked first
- Luma: Asked first
- Eventbrite: Usable with care
- Meetup: Asked first
- Google Developer Groups: Linked to only
- KonfHub: Asked first
- Allevents: Asked first
- Peatix: Asked first
- connpass: Asked first
- Doorkeeper: Usable with care
- Sympla: Linked to only
- NASA Space Apps Challenge: Used
- Junction: Linked to only
- HackZurich: Linked to only
- Microsoft Imagine Cup: Linked to only
- Google Solution Challenge: Linked to only
- ETHIndia: Asked first
- Smart India Hackathon: Linked to only
- tech.africa events: Linked to only
- dev.events Africa: Asked first
- Opportunity Desk: Asked first
- Africa's Talking developer community: Linked to only
- Startup Map Hub: Linked to only
- AfriLabs: Linked to only
- MEST: Asked first
- iHub: Linked to only
- CcHub: Linked to only
- Opportunities for Africans: Linked to only
- After School Africa: Linked to only
- Youth Opportunities: Linked to only
- Techpoint Africa: Linked to only
- OpenAgenda: Used
- Jugend hackt: Used
- CASSINI Hackathons: Used
- Hackathons UK: Asked first
- allhackathons.com: Asked first
- Create With: Linked to only
- Garage48: Asked first
- Crossweb: Linked to only
- Hackathon Lovers: Linked to only
- EU Code Week: Linked to only
- Eventos de IA: Asked first
- Get on Board: Linked to only
- Shawee: Linked to only
- Even3: Not collected
- ProtoPedia: Usable with care
- TECH PLAY: Asked first
- Wevity: Asked first
- Contest Korea: Asked first
- Linkareer: Linked to only
- DACON: Linked to only
- Tianchi: Not collected
- Huodongxing: Not collected
- Accupass: Not collected
- infolomba.id: Asked first
- Dicoding: Linked to only
- Eventpop: Linked to only
- Techcareer.net: Asked first
- TEKNOFEST: Asked first
- Coderspace: Not collected
- Youthall: Linked to only
- Wamda: Linked to only
- USA.gov active challenges: Usable with care
- GOV.UK Search API: Usable with care
- Innovate UK: Linked to only
- EIC Prizes: Linked to only
- Impact Canada: Linked to only
- GovHack: Linked to only
- MyGov Innovate: Not collected
- Topcoder: Asked first
- Reskilll: Linked to only
- WhereUElevate: Asked first
- CLIST: Usable with care
- Wikidata: Used
- dribdat/awesome-hackathon: Used
- unicorn-mafia/awesome-hackathon-winners: Usable with care
- Olanetsoft/awesome-hackathon-projects: Usable with care
UsedUsable with careAsked firstLinked to onlyNot collected
The problem the promise
The rubric is in paragraph nine. The deadline is in another time zone.
Every hackathon hides what matters in its own rules page: who can enter, how big a team can be, what to hand in, and how the judges will score it. Most people skim, build the wrong thing well, and miss a required video.
hackbrief reads the rules for you and hands back one page: the deadline counted down, the checklist, and the judging weights turned into where to spend your hours.
How it works
From ten pages of rules to one page of plan.
02
Read
Paste any hackathon's rules. hackbrief pulls out the deadline, who can enter, the team size and exactly what to hand in, and quotes the line each one came from.
In the rulesWhat hackbrief reads
- Submission deadline: 2027-03-14 18:00 UTCDeadlineSun, 14 Mar 2027, 18:00 UTC
- Teams of up to 4 members.Team1 to 4 people
- Technical quality (30%)CriterionTechnical quality, 30% of the score
- A demo video of no more than 3 minutes.To hand inDemo video, at most 3 minutes
03
Plan
The deadline becomes a prep plan, counted back from the day the hacking starts to the hour you submit, with the finishing work your checklist asks for.
Prep planLagoon Build Weekend
- Fri, 26 Feb 2027
Form the team
Agree who builds what, pick a track, and read the judging criteria together.
+11 days
Tue, 9 Mar 2027Get set up
Create the repository and boilerplate, and try any APIs the rules require.
+3 days
Fri, 12 Mar 2027Kick-off
Choose one demo path that scores on the heaviest criteria, and cut everything else.
+1 day
Sat, 13 Mar 2027Finish
Stop adding features: fix the bugs on the demo path, record the demo video, finish the README, make the slides.
+1 day
Sun, 14 Mar 2027Submit by 18:00 UTC
Submit at least an hour before the deadline, then check every link works.
Try the strategy
Move the judging weights. Watch the advice change.
This is the coach's own code: weights are scaled to whole percentages that add up to 100, and each criterion gets its focus.
The rubric says
The weights add up to 100%.
So the coach says
- Technical quality30%Technical quality is 30%: spend the time on a reliable demo path and clear code, not on extra features.
- Impact25%Impact is 25%: name a real user and their problem, and show measured results for the difference you make.
- Presentation25%Presentation is 25%: rehearse the pitch, keep the video inside the limit, and open with the problem, not the stack.
- Innovation20%Innovation is 20%: make the new part obvious in the first minute of the demo, and say what existing tools miss.
hackbrief in numbers
- 106platforms whose terms were read
- 12allow it, so hackbrief uses them
- 40asked for permission first
- 3sources imported every day
What hackbrief promises
Honest numbers, respected sources, your data left alone.
Every number is computed
Weights, dates and days left come from tested code. A language model may one day word a summary; it never makes up a figure.
Terms before data
hackbrief reads each site's terms before collecting anything, takes only what they allow, and credits every source.
Private by default
Rules you paste are read on the page, in your browser. Nothing is sent to a server, and there is no account to make.
Open source
MIT licensed and built in the open: the code, the decisions and the list of sources are all on GitHub.
Questions
Asked, and answered plainly.
Is hackbrief free?
Yes. It is free, open source under the MIT licence, non-commercial, and needs no account.
Where do the hackathons come from?
From sources whose terms allow it: Hack Club's public API, Hackster's contests feed and HackHQ's open list (organisers' own sites only), imported once a day. More join as their terms allow; every listing links to its own page and credits its source.
Does hackbrief keep the rules I paste?
No. The coach reads them in your browser, on the page. Nothing is sent to a server or stored, and the code that does it is public.
Is the advice written by AI?
No. Today every part of the brief, from the weights to the plan, comes from tested code. If a language model is added later, it will only word facts the code has already worked out, and it will be labelled.
What rules can it read?
English rules as Markdown, tables or plain prose, with dates such as 2027-03-14, March 14, 2027 or 14th March 2027. Times are shown as written, not converted between time zones, and anything it could not find is listed for you to check.