CTF7
PricingFree tierFAQ Sign in

Hackathon management platform, from problem statements to results

Host a judged hackathon on CTF7 yourself: problem statements with team caps, multi-round submissions, rubric judging with fair-scoring controls, mentoring, prizes, and results that teams receive by email. Participants, mentors, judges and organizers each get their own view of the same event.

Self-serve setup Rounds, judges & mentors built in Results, prizes & certificates
Hackathon features

Everything a judged hackathon needs, in one event

Most hackathons run on a registration form, a shared drive for submissions and a judging spreadsheet that breaks at 2 a.m. CTF7 replaces all three. Registration, payments, invite codes, announcements and certificates work as they do for every CTF7 event; the features below are built for hackathons.

Problem statements

Publish statements with a code, theme, category and publishing body. Cap how many teams can take each one, show a live "slots left" count, and import hundreds at once from CSV with a preview.

Multi-round hackathons

Run an idea round, a prototype round and a finale, or as many rounds as you need. Each round has its own submission and judging windows, its own rubric and its own rule for who advances.

Submission forms per round

Build each round's form from text, long text, links, video links, file uploads and choices. Mark any field for judges only. Drafts save automatically, and whoever submits gets an emailed receipt.

Rubric judging

Weighted criteria with scales, written anchors and a tie-break criterion. Start from a built-in template, then judges score in a split view: the submission on the left, the rubric on the right.

Fair scoring

Balanced judge assignment with a minimum number of judges per entry, conflicts of interest and recusal, optional anonymous judging, and score normalization for lenient or harsh judges.

Shortlisting & results

Advance the top N overall, the top N per problem statement, or a manual shortlist, with a waitlist. Release results with a message per outcome, and choose how much feedback teams see.

Mentoring

Assign mentors to teams, by hand or by problem statement. Teams raise help requests, book office-hour slots and message their mentor, all inside the event.

Prizes & awards

Overall prizes, prizes per problem statement or theme, and special awards. Announce them with an email to winning teams, and issue Winner, Finalist and Participant certificates.

Leaderboard & showcase

A podium and a projector mode for the closing ceremony, people's choice voting, a public results page and an opt-in project gallery that shows only the fields you mark public.

  • Branded event page
  • Registration fees in INR
  • Invite-only or open entry
  • Registration questions
  • Announcements
  • Private file storage
  • Audited CSV exports
  • Mobile-friendly for every role
How it works

How to host a hackathon on CTF7

Six steps from announcement to winners, all from your organizer dashboard, with no setup call needed. For the planning that happens before the platform, such as budget, sponsors and writing problem statements, read our step-by-step guide to running a hackathon.

Create your hackathon

Create the event and publish problem statements

Choose the hackathon format, set the schedule, rules and prizes, and publish problem statements, typed in or imported from CSV. Choose open, invite-only or paid registration.

Problem statementsFee collection

Set up rounds, forms and rubrics

Add each round with its windows, its submission form and its rubric, and pick how teams advance: top N overall, top N per problem statement, or manual.

Multiple roundsRubric templates

Invite judges and mentors

Invite each person by email to a judge or mentor role in this event only. Invitations are single-use and expire, and nobody can be staff and a participant in the same event.

Event-scoped roles

Teams register, pick statements and submit

Teams choose a problem statement while slots last, then fill in each round's form before the deadline. Their dashboard shows the timeline, a countdown and what to do next.

Autosave draftsEmail receipts

Assign judges and score

Auto-assign entries evenly across judges, then adjust by hand. Track each judge's progress, send reminders, and review the ranking with raw and normalized scores side by side.

Balanced assignmentNormalization

Release results and announce winners

Advance, waitlist or eliminate teams and release each round with your message. Announce prizes, present the podium, and issue Winner, Finalist and Participant certificates.

Result emailsCertificates
Hackathon judging

Hackathon judging that holds up to scrutiny

The most common complaint after a hackathon is "the judging felt random." CTF7 builds the fixes into the platform instead of leaving them to a spreadsheet.

  • Written rubrics: weighted criteria, each with a scale and anchors such as "3 = works only in slides, 7 = working demo, 10 = deployable", plus a tie-break criterion.
  • Enough eyes on every entry: set a minimum number of judges per submission and auto-assign evenly.
  • Conflicts of interest: exclude a judge from a team, or let judges recuse themselves.
  • Anonymous judging: judges see an entry number instead of team and member names.
  • Score normalization: rank by scores adjusted for lenient and harsh judges, with raw scores always shown alongside and low-variation judges flagged.
  • A trail for every change: overrides, reopened reviews and excluded scores each need a reason and are kept in an append-only history.
CriterionWeightWhat judges look for
Problem fit25%Is it a real problem for a real user? Is the scope realistic for the time available?
Technical depth30%Working code in the repository, sound architecture, not just a UI mock.
Security & robustness25%Input validation, secrets handling, threat model. Weight this higher for a cybersecurity hackathon.
Demo & communication20%A clear demo video or live pitch, and a README another developer could follow.

The security hackathon starter rubric. CTF7 also ships starter rubrics for government-style innovation challenges and product hackathons; criteria and weights are yours to change per round.

One event, four views

Built for participants, judges, mentors and organizers

Participants

A dashboard with the round timeline, a live countdown and the next action. A problem-statement picker with slot meters, autosaved submissions, "My results" for every released round, voting and "Get help".

Judges

A queue with progress, and a split-pane evaluation page with autosave, previous and next, finalize and recuse. Judges reach only the entries assigned to them.

Mentors

Their assigned teams, a help-request queue they can claim and resolve, office-hour slots teams book, and a message thread per team.

Organizers

Setup, moderation, judge progress, the ranking with cut lines, results release, prizes and exports. Organization viewers can see everything and change nothing.

Large and institutional hackathons

Ready for government, university and corporate innovation challenges

Problem statements from many publishing bodies, hundreds of teams and several shortlisting rounds are the normal case on CTF7, not an edge case.

  • Statements at scale: import up to 500 problem statements per CSV, re-import to update only the columns in the file, and review a before-and-after diff first.
  • Per-statement shortlists: advance the top teams of every problem statement, so a crowded statement cannot crowd out the rest.
  • Private submission files: decks and source archives sit in private storage, and every download is permission-checked and served through a short-lived link.
  • Exports you can hand over: submissions, scores, decisions, problem statements and staff as CSV, with every export audited.
Cybersecurity hackathons

Run a cybersecurity hackathon

A security hackathon asks teams to build defensive tools, detection rules or hardened apps. Use the security starter rubric, weight "Security & robustness" to match your theme, and write problem statements around real threats.

Want players who would rather break things than build them? Run a jeopardy CTF or a Raw Ops bug hunt as a separate event for the same audience, from the same organization account. Each event keeps its own registration and results.

Problem statement ideas for a security hackathon

  • A phishing URL triage tool for a college helpdesk
  • Detection rules for a common attack technique, with test data
  • An auditor for over-permissive cloud storage or IAM policies
  • A secrets scanner for repositories, tuned to cut false positives
  • A hardened version of a deliberately vulnerable sample app
Example timeline

A three-round college hackathon, from announcement to finale

This is a sample plan for a tech-fest hackathon with around 200 participants, which fits a Standard event at a fixed ₹9,999 per event. Larger or multi-day events are quoted on Premium. Compress it to a weekend for a community hack night, or stretch it for a corporate innovation challenge.

WhenPhaseWhat happens on CTF7
T − 6 weeksAnnounceEvent page live, problem statements published, registration and fees open.
T − 3 weeksTeams lockRegistration closes, teams pick their problem statements, judges and mentors accept their invitations.
T − 2 weeksRound 1 · IdeasTeams submit a one-page proposal. Judges score it, and the top 3 teams per problem statement advance, with a waitlist.
T − 1 weekResults & kickoffRound 1 results are released by email with your message, and shortlisted teams get the build-round form and rubric.
Day 1–2Round 2 · Build36-hour build with mentor help requests and office hours. Repository, demo video and deck uploads close at a fixed time.
Day 3Round 3 · FinaleThe top 10 teams demo live. Judges score against the rubric, people's choice voting closes, and the podium goes on the projector.
T + 3 daysWrap-upPrizes announced, Winner, Finalist and Participant certificates issued, the project gallery published and CSV exports shared with sponsors.
Checklist

Hackathon organizer checklist

Print this, or paste it into your team channel. The full hackathon organizer guide expands each item, and the code of conduct covers originality rules you can link from your event page.

  • Problem statements written, reviewed and capped
  • Eligibility and team-size rules published
  • Registration fee (if any) and refund terms set
  • Code of conduct linked on the event page
  • Rubric per round, with weights and scale anchors
  • At least two judges per submission
  • Conflicts of interest collected from judges
  • Mentor roster and office-hour slots
  • Submission form per round: repo, demo video, deck
  • Hard submission deadline communicated twice
  • Advancement rule and waitlist for each round
  • Prizes, sponsors and certificate design ready

Host your hackathon on CTF7

Create the event, publish your problem statements and invite your judges today. Running something large or unusual? Talk to the event team and we will help you plan the rounds.

CTF7 mascot holding a CTF7 flag