How Simple Hack works

The whole journey of a hackathon on simple-hack.app: who does what, in what order, and what each person sees.

1. The three places

Every event lives in three kinds of address.

simple-hack.appThe app. Sign in, create and manage events, join and judge links, scoring, your account.
<event>.simple-hack.appThe public event page: about, rules, prizes, schedule, sponsors, FAQ, announcements, project gallery, winners.
<team>.<event>.simple-hack.appEach team's own live website, published from their AI app.
flowchart LR
  A["simple-hack.app
the app"] -->|organiser creates| E["event.simple-hack.app
public event page"] A -->|team publishes| T1["team-a.event.simple-hack.app"] A -->|team publishes| T2["team-b.event.simple-hack.app"] E -->|gallery links to| T1 E -->|gallery links to| T2 D["simple-hack.app/directory
all hackathons"] --> E

2. The people

Each person has one role per event. Anyone can sign in with an email code or Google. It is free and there are no size limits.

OrganiserCreates and runs the event. Can invite co-organisers, and can also judge.
ParticipantJoins with the join link, forms or joins a team, builds and publishes the team's site, writes the entry.
JudgeJoins with the judge link and scores projects on phone or laptop.
PublicSees the event page, the gallery and the winners. Can vote if people's choice is on.
Platform admin (you)Sees every event and who runs it, can take an event down, can keep team sites longer.

3. The life of an event

The organiser moves the event through these stages. The usual order is left to right.

flowchart LR
  D[Draft] --> O[Open] --> B[Building] --> C[Submissions closed] --> J[Judging] --> R[Results] --> X[Ended]
StageWhat happens
DraftJust created. The organiser fills in the page. Nobody can join.
OpenPeople join with the link and form teams. Team site addresses get ready.
BuildingSame as Open: teams build and publish. Joining is still allowed.
Submissions closedThe deadline is now. Sites and entries freeze; each team's site is pinned as it was at the deadline for the judges.
JudgingJudges score. Judges can still join.
ResultsResults are published. No new judges.
EndedFinal. The page and results stay forever; team sites stay 30 days.

An organiser can step back from Closed, Judging or Results to Open or Building, which reopens publishing. Nothing comes after Ended.

4. Organiser's journey

flowchart TD
  S[Sign in] --> C["Create event
name, title, who is running it,
purpose, expected people, dates"] C --> P["Fill the public page
about, rules, prizes, code of conduct,
schedule, sponsors, FAQ"] P --> R["Optional: sign-up questions,
approval, tracks, deadline,
required entry fields"] R --> O[Open the event] O --> L["Share the join link with participants
and the judge link with judges"] L --> M["During the event
approve sign-ups, post announcements,
move people, give a team more time,
take a site down if needed"] M --> CL[Close submissions] CL --> JU["Judging tab
rubric, who judges whom,
conflicts, progress"] JU --> LK[Lock scores] LK --> PB["Publish results
break any ties"] PB --> V["Choose the public view
winners only or full ranking"] V --> EN[End the event]

What the organiser sets up

An organiser can create 3 events a day and have 2 not yet ended at once. There is no limit on participants, teams or judges.

5. Participant's journey

flowchart TD
  S[Sign in] --> J[Open the join link]
  J --> A["Accept the code of conduct,
give a display name,
answer sign-up questions"] A --> Q{Approval needed?} Q -->|no| T Q -->|yes| W[Wait for the organiser] -->|approved| T T{Team} -->|start one| N["Create a team
share its 8-letter code"] T -->|have a code| JT[Join a team] N --> K JT --> K K["Connect your AI app to simple-hack.app,
or get your own team key"] --> B["Build and publish
team.event.simple-hack.app"] B --> E["Fill the entry
title, description, video,
code link, screenshot"] E --> D[Deadline: site and entry freeze] D --> RS["After results: see your own
score, rank and judges' comments"]

6. The deadline

flowchart LR
  B["Building
publish as often as you like"] --> D{"Team's deadline
event deadline,
or a later one if given more time"} D --> F["Frozen
no publishes, no entry edits,
no new keys"] F --> P["Pinned version
what judges open"]

The organiser can give one team more time. Whatever was live at the moment of the deadline is what judges see, even if something was halfway through publishing. Visitors can still use the site's forms afterwards; only the team's own changes stop.

7. Judge's journey

flowchart TD
  S[Sign in] --> J[Open the judge link]
  J --> L["My projects
the list depends on how
the organiser assigns judges"] L --> O["Open project
the site as it was at the deadline,
plus the entry"] O --> C{Conflict of interest?} C -->|yes| X["Tap 'I have a conflict'
this team is skipped"] C -->|no| SC["Score each criterion
one at a time, saves on every tap"] SC --> CM[Optional comment] CM --> N[Save and next] N --> L

How judges get their projects

ModeHow it works
Open (default)Every judge can score every team.
AutomaticEach team gets a set number of judges (2 unless changed), spread evenly.
ManualThe organiser picks each judge–team pair.
Track panelsJudges are put on a track's panel and score the teams in that track.

Organisers can judge too, from the Judging tab, without a second account. A judge with a conflict, or marked as one by the organiser, never counts for that team: neither their score nor their comment.

8. How scores become results

flowchart TD
  R["Rubric
starts as Idea, Execution, Design, Demo
25% each, scored out of 5"] --> JS["Each judge's score for a team
converted to a mark out of 100"] JS --> AV["Team total
average of its judges
conflicts left out"] AV --> MD{Score mode} MD -->|raw| RK[Ranking] MD -->|normalised| NM["Evens out harsh
and generous judges"] --> RK RK --> TI{Tie?} TI -->|yes| TB["Break it with the chosen criterion,
then how judges compared the two,
then the organiser decides"] TI -->|no| LK TB --> LK[Lock scores] LK --> PB[Publish] PB --> PUB["Public: winners only,
or the full ranking"] PB --> TM["Each team privately:
its own score, rank and comments,
without judge names"] PB --> TW[Track winners and prizes]

9. People's choice and the directory

flowchart LR
  G[Gallery open] --> V["Organiser turns on voting
with open and close times"] V --> W["Who can vote:
anyone signed in,
event members, or participants"] W --> C["One vote each, can be changed,
never for your own team"] C --> R["Counts shown only
after voting closes"]

The directory at simple-hack.app/directory lists events as Now, Upcoming and Past. Drafts and taken-down events are never listed; an organiser can take theirs off the list at any time.

10. After the event

flowchart LR
  E[Event ended] --> K["Team sites stay up
30 days"] K --> W["Day 16: one warning email
to the organiser"] W --> RM["Day 30: team sites removed"] E --> ST["Event page, results,
scores and votes stay"]

An organiser who needs more time writes to support; the platform admin can keep an event's sites.

11. Who sees what

PublicParticipantJudgeOrganiser
Event page, galleryYesYesYesYes
Other people's emailsNoNoNoYes
Sign-up answersNoOwn onlyNoYes
All entries and pinned sitesLive sites onlyOwn teamYesYes
Scores while judgingNoNoOwn scoresYes
ResultsWinners, or full ranking if chosenOwn score, rank, commentsPublic viewEverything
Which judge said whatNoNoOwn onlyYes
Vote countsAfter voting closesAfter voting closesAfter voting closesAfter voting closes