Working product first
Technical implementation and product quality make up 55 of the 100 available points, reflecting the importance of credible engineering and a useful demonstration.
Six selected student teams are designing practical applications with one shared goal: benefiting Palestine.
About the event
The Palestine Innovation Hackathon builds on the previous Quantum Computing and AI Hackathon. Selected students formed six teams and have been developing applications since approximately April 2026. The teams are working toward practical, context-aware solutions that can benefit Palestine. Final judging is currently planned for late October in Aqaba; the date and logistics remain subject to organizer confirmation.
Participation is limited to the six teams formed by selected students from the previous hackathon.
Six active teams. Team membership is not published here.
Participation
Six selected student teams continue from the previous hackathon. Team membership and project names will be published only when confirmed and appropriately consented.
The journey
This is a continuation programme, giving selected teams time to turn their ideas into practical applications before a shared final review.
01
Students selected from the previous hackathon formed six teams for continued project work.
02
Teams have been developing their applications since approximately April 2026.
03
October milestones prepare the final technical package, relevant validation evidence, and a consistent live demonstration.
Towards the final
The final is being prepared as an evidence-led review of working products, not a pitch-only event. Staged submissions give organizers time to review the final materials and prepare a shared framework for judging.
Technical implementation and product quality make up 55 of the 100 available points, reflecting the importance of credible engineering and a useful demonstration.
Teams are encouraged to show what they learned from relevant people and real settings, with meaningful evidence valued over large but weak numbers.
Every team is working toward the same public scoring categories, submission stages, and planned presentation format.
Aqaba · planned
The current plan is a three-day Aqaba programme centred on final judging. The exact date, hall, timings, travel, accommodation, and remaining logistics are still subject to organizer confirmation.
Day 1 · planned
Team arrival and any confirmed check-in arrangements will be shared by the organizers.
Day 2 · planned
Teams will present their progress, demonstrate the product, discuss validation and sustainability, and answer judge questions.
Day 3 · planned
A free or community day is part of the current plan; the final activity details are yet to be confirmed.
Planning
Project work began (approximate)
External validation and traction evidence due
First complete technical and product package due
External evidence closes for normal scoring
Final technical and product package due
Judging package freeze (planned)
Final judging in Aqaba: current plan
Impact
6
Active teams
100
Final score
October
Planned final month
Final evaluation
30
points
25
points
20
points
15
points
10
points
With thanks
On behalf of the organizing team, we extend our sincere thanks to the Open Quantum Institute (OQI) and CERN for their major support in making this hackathon possible. We are also grateful to Universe Telecom, Cystack, the Qaddumi Foundation, the Cooperative Society for Computing and Training, and the participating Palestinian universities for their valued support and partnership. Our special appreciation goes to Dr. Mousa Farajallah for leading this initiative, Prof. Sana Odeh for her generous support and connections, and the OQI team—Audrey Himmer, Marina Chibli, and Dr. Tim Smith—for their thoughtful coordination and continued support.
For questions, contact Huthayfa Mutan (Huthayfa.mutan@gmail.com).
FAQ
The current plan is around 27 October 2026 in Aqaba. The organizer guide notes that the exact date, time, and logistics will be confirmed later.
The final package includes a clearly identified GitHub version, a testable build or equivalent demo, project summary, architecture diagram, limitations, pivot explanation, validation evidence, and team-contribution summary.
No mid-competition judging elimination is planned. The guide does note that sustained inactivity or repeated non-response can affect a team’s eligibility through a documented organizer process.