Someone is scared, hurt, lost, overwhelmed, or trying to get help. What could you build that makes the next few minutes safer?

RescueHacks is an online, beginner friendly hackathon where students build AI powered tools that could help people survive, respond, recover, prevent harm, or get help faster.

Our mission is simple: build AI that could help save a life.

You do not need to be an experienced programmer to participate. RescueHacks welcomes projects built with code, AI tools, and no code or low code platforms like ChatGPT, Glide, Bubble, Replit, Lovable, Figma, Airtable, Zapier, Make, and more. You'll be judged on your idea, execution, and potential impact, not the amount of code you write.

A RescueHack can be an app, chatbot, website, dashboard, workflow, voice assistant, prototype, design, spreadsheet, or another creative solution. It doesn't have to be fully polished.

What matters is that your project helps someone in a serious situation by making information clearer, action easier, support faster, or risk lower.

Choose any problem where technology could help protect or save lives, including:

• Emergency Response
• Medical Navigation
• Mental Health Support
• Accessibility and Disability Support
• Community Rescue
• Prevention and Early Warning

These tracks are meant to inspire you, not limit you. If your project has the potential to help save a life, it belongs at RescueHacks.

Some example projects include:

• AI emergency checklist generator
• Disaster check in dashboard
• Mental health safety plan assistant
• Shelter supply tracker
• Volunteer matching platform
• Medication safety helper
• Missing person coordination tool
• Multilingual emergency guide
• First aid question organizer
• Weather warning simplifier

Projects should support people, not replace emergency responders, doctors, therapists, crisis counselors, or other trained professionals. If your project involves medical, emergency, or mental health situations, design it responsibly and encourage users to seek qualified help when appropriate.

The winning projects won't necessarily be the most technically complex. We'll be looking for ideas that solve meaningful problems, are practical and responsible, show a working prototype, and have the potential to continue making an impact long after the hackathon ends.

• Problem & Impact
  How well does the project identify and address a real problem related to safety, emergencies, accessibility, or disaster response? Judges will evaluate the potential impact the solution could have on helping or saving lives.
• Creativity & Innovation
  How original and thoughtful is the idea? We value creative problem-solving and unique approaches, regardless of the technical tools used to build the project.
• Execution
  How effectively was the idea brought to life? Projects may be built using code, no-code, or low-code tools. Judges will focus on how well the team executed their vision rather than the amount of code written.
• Future Potential
  Could this project continue beyond the hackathon? Judges will consider whether the team has demonstrated a realistic vision for improving, expanding, or implementing their solution after the event.
• Presentation
  How clearly did the team communicate their project? Judges will evaluate the quality of the demo, explanation of the problem and solution, and the team's ability to answer questions.