Organizer
Runs the event
The largest surface in the product, and most of it works while the event is live: people, content, announcements, rooms, judging assignment, the deadline, and the full audit log.
The online hackathon nobody has to leave.
Registration, challenge briefs, mentor office hours, a live stage, submissions and judging — all inside one platform, configured for your event, in Arabic and English.
One platform, from the invitation to the certificate.
Most online hackathons are assembled: a form here, a chat workspace there, a video link pasted into a document, scoring in a spreadsheet. Every seam is somewhere a participant gets lost and an organizer does manual work. NoHackathon is the whole event in one place, and every part of it knows about every other part.
- Fully online
- Participants join from wherever they are. The timeline shows every person their own local time.
- Five phases
- Registration, challenge selection, the build window, judging, results — each with its own state and its own controls.
- Four roles
- Organizer, participant, mentor and judge. One person can hold different roles in different events.
- Two languages
- English and Arabic across the whole platform, both directions, switchable per person.
How an event runs
The same five phases every time. What changes between clients is their content and their settings, not the machinery.
Two sides, one platform
Registration
Organizer
Import people from a spreadsheet, review the parsed rows and confirm. Issue an invite code per person and export the list. Assign roles, and change someone's role later without rebuilding their account.
Builder
Redeem the invite code, set your own password, complete onboarding and consent. Public sign-up is closed; being invited is how you get in.
Challenges
Organizer
Author the challenge briefs in both languages. Filter your participant list by which challenge each person picked.
Builder
Read the briefs and select one. Change your mind while you build — the choice follows you everywhere, and only locks when you submit.
Where both sides are in the same room
Live participation is part of the platform, not a link out.
This is the part that usually gets outsourced to a meeting tool and a shared calendar. Here it is a first-class room primitive with three types, so every room inherits the same rules.
Mentor rooms
One per mentor, live during their published office hours.
A first-come, first-served queue with the waiting time visible to both sides. Fifteen minutes on accept, a two-minute warning to both people, extendable by the mentor, and auto-extending when nobody is waiting. The clock only bites when there is a queue behind you.
The main stage
One per event. Broadcast, with a live audience.
Organizers and mentors present. The audience submits questions, upvotes each other's, raises a hand, claps and reacts. A participant can be brought up to speak and dropped back afterwards. Nothing on stage is recorded.
Private rooms
Opened on demand, for whoever it is for.
A judges' huddle, a quiet word, a breakout. An organizer opens one and adds people to it.
What every room inherits
- Organizers can enter any room, and appear in the participant list like anyone else.
- Anyone in a room can be invited or removed.
- A fallback meeting link can be pasted into any room if the video fails, and the session continues.
The build window
Organizer
Announce by role, schedule announcements ahead, push a browser notification, move the deadline live, and answer support threads. Promote a good answer straight to the FAQ.
Builder
Build. Queue for a mentor, ask a question on the stage, talk to your organizer, and watch the countdown in your own time zone.
Where both sides watch the same clock
What gets handed in
Four things, all required, and every save is kept.
- A repository linkWhere the work actually lives.
- A demo videoUploaded, three minutes maximum. Progress is shown and the upload resumes after an interruption.
- A deck or documentWhatever the brief asked them to explain.
- Written answersThe questions the organizer set.
- Editing is free until the deadline, and the revision history stays visible to organizers.
- Submitting asks the participant to confirm their challenge, and that confirmation locks it. The artefacts can still be revised.
- Organizers see who has submitted and who has not, at a glance, throughout.
- One button sends a reminder to chat and browser notification, raises a countdown on every dashboard, and hands the organizer copyable text for their own channel.
Judging
Organizer
Assign submissions to judges by hand, set how many each one takes, and reassign mid-round when someone falls behind. Two rounds: assigned scoring, then a shortlist you choose from the ranking, then a full round.
Builder
Nothing to do but wait. Your submission is locked to the challenge you confirmed, and your revision history is preserved.
Where it ends
Published when you decide, not when the clock says so
The ranking is computed; the shortlist is yours to pick from it. Results stay hidden until an organizer explicitly publishes them, usually live on the main stage.
- One overall winner, or winners per challenge
- Both models are supported and neither is hard-coded, because clients decide this late.
- One prize structure for the event
- Shared across challenges rather than split into separate prize sets.
- A certificate for everyone
- Name, project, event and date, issued as an image in English and Arabic, with one-click sharing.
- Analytics, exports and a report
- Participant counts, submissions and judging results, filterable and breakable down by challenge.
- Access removed on your schedule
- Participants, mentors and judges are wound down when you choose. Submissions, messages and scores are preserved.
Configured for your event, not rebuilt for it.
Every client gets their own instance. What separates one event from another is settings and content — not a fork of the code, and not a design project.
How it looks
- Your domain
- Your background artwork
- Accent color and glass tint
- Corner style and fonts
Set once, applied everywhere in the instance.
How the event is shaped
- Solo entries or teams
- One challenge or several
- Your own phase timeline and deadlines
- Which language the event leads with
Participants can still read it in the other language.
How it is judged
- One rubric shared across challenges, or one per challenge
- How many submissions each judge takes
- Named or blind judging
- One overall winner, or winners per challenge
Criteria stay editable until judging opens, because clients decide late.
The second event for the same client costs less, because the instance already exists.
Who is in an event
Four roles, scoped per event. A person can hold different roles in different events.
Participant
Builds
Picks a challenge, uses mentor office hours and the stage, submits, and collects a certificate.
Mentor
Helps
Publishes office hours, runs their own room and queue, and can start a conversation with any participant — into the same thread the participant would have opened.
Judge
Scores
Works an assigned queue one submission at a time, with the challenge highlighted, and cannot see any other judge's scores.
Arabic and English, both properly
Not a translation layer bolted onto an English product. Interface and client-authored content are both bilingual, the layout mirrors correctly in both directions, and each person reads the event in the language they choose.
The same announcement, either way
English
العربية
What this is not, yet
Worth saying plainly, because the alternative is finding out later.
- No AI screening, summarizing or matching. Judges decide with what they can see.
- No plagiarism or originality checking.
- No prize payouts. Prizes are tracked as a task list; the money moves through your own finance.
- No enterprise single sign-on until a client's security team asks for it.
- No sponsor dashboard. Sponsors attach to a challenge and a prize without one.
Each of these gets built when a client needs it — and once built, every later client can switch it on.
Tell us about your event
Quoted per event, per client. We set the instance up, configure it with you, and are on hand while it runs.
- Roughly how many people, and when
- Solo entries or teams
- How many challenges
- Which language it leads with