A hackathon needs less, not more
No programme, no presenters. Announcements that land and people who find each other.
What usually goes wrong
Event tools assume a talk schedule
You spend the setup deleting tracks, sessions and presenter slots you will never use, and participants scroll past empty screens all weekend.
Teams form slowly and painfully
The first three hours go into finding a designer. The people who came alone are the ones most likely to leave early.
A rule change reaches half the room
You shout it, put it on a whiteboard, post it in a chat. At 2am three teams still submit against the old deadline.
What you get
Set up from the first minute. Everything here is part of the free base up to the attendee cap, except where the line itself says otherwise.
- Networking Features
- Announcements Features
Left off
Not part of this setup, so nobody has to scroll past it. You can switch any of it on later.
- Sessions
- Tracks (parallel rooms)
- Presenters
- Q&A
- Polls
- Materials
- Gallery
- Exhibitors
How it runs
Set up only what a hackathon has
Sessions, tracks, presenters and Q&A are off. Participants open a screen that carries nothing they do not need.
People find their team
Who is here, what they build, who is still looking. The person who came alone gets a team by lunch.
Announcements land everywhere at once
A deadline change reaches every phone in the building, including the team that has been in a side room since midnight.
Worth adding
Paid modules that fit this kind of event. The base stays free.
Close to this
Set it up in a few minutes
Create the event, pick the “Hackathon” type in the setup wizard, share one link. No app to install, for you or for anyone attending.