Hackathons
Demo night, without the dead air.
A hackathon is two days of energy that usually ends in a quiet room watching slides. Live voting, scored rounds and a leaderboard put the audience back into the last hour, which is the hour everyone remembers.
The three moments worth instrumenting
Kickoff
A word cloud on “what are you building” turns a room of strangers into a map. Teams find each other, and you get a list of themes before anyone writes a line of code.
Submissions
A form collects project names, repo links and team members, with conditional logic so teams that shipped answer different questions from teams that did not. It exports to CSV for the judges.
Demo night
People's choice voting from every phone, live on the big screen, plus a scored round for judges. The board reorders between demos and the room watches it move.
Why organisers pick it for this specifically
You pay for the weekend, not the year
A hackathon is one event. A Day Pass covers it. Most tools in this category want an annual commitment for a room that exists for 48 hours.
Nobody installs anything at 11pm
Participants are on a hotel or campus network, on the phone in their hand, and tired. One code in a browser is the only thing that reliably works.
Teams and rounds are built in
Group participants into teams and run a series of scored rounds, so standings carry across the whole event rather than resetting per activity.
Sponsors want proof
Every session rolls up into a report with participants reached, activities run and response trends. That is what a sponsor renews on.
Questions organisers ask
How many participants does a Day Pass cover?
Can we stop people voting for their own project twice?
Can judges score separately from the audience?
Do we need our own screen software?
Can we set the whole thing up from a terminal?
Running one this month?
Buy a single Day Pass for the event. No annual contract for a one day room.