28 to 30 July 2026, online, Bangladesh

Build what holds
when the signal drops.

A three-day hackathon for crisis technology and the ideals of the July Revolution. Teams of one to three.

1

team registered

Crisis Tech1
Spirit of July0

This hackathon is dedicated to

Portrait of Jahiduzzaman Tanvin

Jahiduzzaman Tanvin

Drone engineer and IT expert

Portrait of Sheikh Ashabul Yamin

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.

Two tracks

Pick one at registration. You can change it up to the close of registration.

Crisis Tech

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.

  • Mesh messaging without a tower
  • USSD services for feature phones
  • Offline-first disaster mapping

Spirit of July

Anything that upholds the ideals of the revolution. Accountability, access to information, civic participation, and the memory of what happened.

  • Public accountability tooling
  • Archives that resist deletion
  • Civic access and participation

Dates

  1. 25 July

    Registration opens

    Teams of one to three. Open to Bangladeshis anywhere.

  2. 27 July

    Registration closes

    23:59. No late entries.

  3. 28 July

    Build sprint begins

    00:00. A continuous 72 hours.

  4. 30 July

    Sprint ends, submissions lock

    Repo, demo video, and post.

  5. 1 August

    Engagement window closes

    Public engagement counts freeze.

How you are scored

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%

Impact and relevance to track

Does it solve a real problem for real people, and does it belong in its track?

20%

Technical execution

Does it work? Is the engineering sound and non-trivial?

20%

Public engagement

Facebook reactions and shares, plus GitHub stars on your repository. Ten percent each, scored relative to the highest in your track.

15%

Innovation and originality

A genuinely new approach, or a sharper take on a known problem.

10%

Feasibility and resilience

Can it run on low bandwidth, low power, and low-end devices?

10%

Presentation and usability

Is the demo clear and the interface usable by its intended user?

Full detail is in the participation guideline.

Questions

Can I participate solo?

Yes. Teams are one to three members, and solo entries are welcome.

Do I need a team before registering?

No. Register solo and use the team-matching channel to find people.

Can I use an existing open-source project as a base?

As a dependency, yes. Not as your submission. Core work must happen during the sprint, and you declare any prior work at registration.

Can we submit in Bangla?

Yes. Your video and deck may be in Bangla or English. The README should be English or bilingual.

Can one team enter both tracks?

No. One team, one submission, one track.

What if my hardware does not arrive in time?

Submit a simulation or bench prototype with a video. Judges assess the working portion.

Registration closes 27 July

Register your team, then start thinking about what breaks first when the network goes down.

Register your team