28 to 30 July 2026, online, Bangladesh
A three-day hackathon for crisis technology and the ideals of the July Revolution. Teams of one to three.
185 Teams
Registered
103 Crisis Tech
82 Spirit of July
Jahiduzzaman Tanvin
Drone engineer and IT expert
Sheikh Ashabul Yamin
IT professional
Both were technologists. Both were killed during the July uprising. This event carries their names because the work they were doing is the work we are asking you to do.
It is also a tribute to Jogajog, the tool that let people reach each other through the nationwide internet shutdowns.
Pick one at registration. You can change it up to the close of registration. The lists below are there to start you thinking, not to choose from. Anything that fits the track counts, including ideas nobody here has thought of.
Offline communication, mesh and peer-to-peer networking, SMS and USSD services that work on a button phone, and tooling for low-resource disaster response.
Project Ideas
Example directions, not a checklist
Not a limit. Anything that fits this track counts.
Anything that upholds the ideals of the revolution. Accountability, access to information, civic participation, and the memory of what happened.
Project Ideas
Example directions, not a checklist
Not a limit. Anything that fits this track counts.
Puku CLI and editor
60,000 BDT
total prize pool
Sponsored by Omukk, title sponsor of the hackathon. Every team that takes part also gets a Puku subscription, not just the winners, from Poridhi, who make the Puku editor and CLI.
1st place
15,000 BDT
In each track — Crisis Tech and Spirit of July are judged separately.
2nd place
10,000 BDT
In each track — Crisis Tech and Spirit of July are judged separately.
3rd place
5,000 BDT
In each track — Crisis Tech and Spirit of July are judged separately.
Every participant
1 month
Puku CLI and editor subscription, for everyone taking part.
Top 3 teams in each track
6 months
Puku CLI and editor subscription. Awarded per track, so Crisis Tech and Spirit of July each have their own top three.
More prizes are being confirmed and will be announced here before the sprint begins. Full terms are in the participation guideline.
Seven checkpoints. No extensions past a cutoff.
26 July
Registration opens
Teams of one to three. Open to Bangladeshis anywhere.
Completed
28 July
Registration closes
23:59. No late entries.
Completed
28 July
Build sprint begins
00:00. A continuous 72 hours.
Completed
31 July
Submission deadline
11:59 am. Repo, demo video, and post.
Completed
30 July to 1 August
Social media engagement window
Public engagement counts freeze at 23:59 on 1 August.
Completed
31 July to 1 August
Judging
Runs alongside the closing engagement window.
Completed
2 August
Results announced
Winners published.
Completed
A fifth of your score is public engagement, so plan the post and the repository as part of the build, not as an afterthought. Buying reactions or stars scores zero on that component.
25%
Does it solve a real problem for real people, and does it belong in its track?
20%
Does it work? Is the engineering sound and non-trivial?
20%
Facebook reactions and shares, plus GitHub stars on your repository. Ten percent each, scored relative to the highest in your track.
15%
A genuinely new approach, or a sharper take on a known problem.
10%
Can it run on low bandwidth, low power, and low-end devices?
10%
Is the demo clear and the interface usable by its intended user?
Full detail is in the participation guideline.
Yes. Teams are one to three members, and solo entries are welcome.
No. A team can be one person, so you can register on your own and compete solo. If you would rather find teammates first, ask on the event Discord.
As a dependency, yes. Not as your submission. Core work must happen during the sprint, and you declare any prior work at registration.
Yes. Your video and deck may be in Bangla or English. The README should be English or bilingual.
No. One team, one submission, one track.
184 teams are in, and the build sprint is running. Sign in to check your team, and keep an eye on the Discord for submission.
Sign in to your team