Nepal Hackathon
Hack, create,and collaboratefor a stronger Nepal.
A platform connecting Nepali teams with the people, compute and funding to go further — during a crisis, and long after one.
Current event · Registration open
Bhote Koshi–Trishuli flood response
Kickoff Sunday 30 August, 09:00 NPT
- 02
- Days
- 07
- Hrs
- 43
- Min
- 02
- Sec
Link emailed once the platform is confirmed.
What this is
A catastrophic flood hit Nepal. We’re bringing people, technology and resources together to help.
On 26 August 2026 a massive flash flood tore through Rasuwa, devastating communities and destroying roads, bridges, communications and critical infrastructure along the Bhote Koshi–Trishuli river system.
Nepal’s responders and experts are already at work. Nepal Hackathon helps them draw on engineers, scientists, mappers, satellite data, AI, cloud infrastructure, funding and other resources from around the world — for the emergency now and the work that comes after.
Put scattered expertise on one problem
Hydrologists, mappers, engineers, translators and software people — in Nepal and outside it — rarely end up working on the same thing. Each event puts them there, and keeps a record of who works on what.
Pool the resources, not just the people
Compute, satellite tasking, connectivity and funding are far easier to unlock together than one team at a time. Doing that collectively is a large part of what a platform is for.
Start the next one further along
Known data sources, known contacts, known gaps, and people who have already worked together. That is what makes the second event faster than the first.
- 01
Start with the people already responding
Teams in Nepal explain what is happening, what is already under way and where additional help would actually be useful. New contributors organise around those needs.
- 02
Bring expertise and resources together
Engineers, scientists, mappers and software teams work alongside access to compute, satellite imagery, connectivity, equipment and funding.
- 03
Current needs and future preparedness
Teams work in real time and asynchronously. Some focus on urgent needs; others build for the future on warning systems, risk mapping, recovery and longer-term resilience.
Latest coverage
All coverage- Race to get aid into Nepal and Tibet amid warnings flood lake could burstThe Guardian
- Death toll rises to 353, with more than 1,300 missing in Nepal, Tibet after catastrophic floodsCBC
- Nepal flash floods kill 350, leave 900 missing as families searchIndia Today
Publishers’ own words and figures, not ours, and unverified by us.
How it works
Led from Nepal. A global invitation to bring your skills to a problem that matters.
Four steps, and the last one is the point. Most of what gets built at a hackathon dies on Monday. Here it does not, because somebody is already waiting to use it.
- 01
Start with the people doing the work
Responders, researchers, engineers, drone operators and institutions in Nepal explain what is happening, what already exists, where the gaps are and what additional help would actually be useful.
- 02
Build the team around the problem
Tell us what you know and how much time you have. We match engineers, scientists, mappers, designers and other contributors to problems where their skills can be useful — before the work begins.
- 03
Work live. Keep working async.
Teams use the event to move quickly together, then keep going across countries and time zones. They might map, analyse data, process imagery, build tools, find resources or work through longer-term technical problems.
- 04
Keep useful work moving
If the work is valuable, it does not stop when the event ends. Nepal-side teams and contributors can keep it moving, with additional funding, compute, technology and expertise brought in as needed.
Ground rules
Five things we hold to.
They apply to every event, and to anything built at one.
- 01
The agenda comes from Nepal
Work is scoped by the people already doing it. If you arrive with a solution looking for a problem, we will point you at the list instead.
- 02
Show your sources
Anything we publish names where it came from, when, and how confident we are. Work that cannot say what it is based on does not go out under our name.
- 03
No risk scores on named places
We do not publish hazard ratings or evacuation guidance for particular settlements. A wrong number next to a village name moves people, and that call belongs to the authorities who are accountable for it.
- 04
Build for the handover
A prototype nobody in Nepal can run is a weekend spent on yourself. Find the owner early and build something they can actually keep.
- 05
Nothing that identifies a person
No missing-person lists, no casualty records, nothing that names or locates someone affected. This holds for prototypes as firmly as it holds for the site.
Register
Tell us what you can do.
Two minutes. It goes to the Nepal-side Problem Leads so they can match you to a team before the kickoff — and it puts you on the list for whatever we run next.
Who is joining
Who is already in.
Live from the registration list. Names show only for people who asked to be listed, so expect fewer faces than the count beside them.
- Registered
- 0
- In Nepal, on the response
- 0
- Listed publicly
- 0
- Areas covered
- 0
Registration just opened, and this counter is live rather than seeded. Be the first name on it.
No photographs: a LinkedIn profile picture cannot be fetched from a pasted URL, only through a sign-in each person completes themselves. Initials are the honest stand-in.