I Built a Hackathon Platform Because I Was Tired of Hackathons Breaking in the Same Places

Description and use

HackNext is a self‑hosted hackathon platform that addresses inconsistent judging, network bottlenecks, and fragmented tooling, ensuring reliable operation even when the internet fails.

Problem

Hackathons often suffer from inconsistent judging, network bottlenecks, and fragmented tooling, making organization difficult.

Outcome

HackNext delivers a robust, self‑hosted hackathon platform that handles network failures, scoring inconsistencies, and deployment edge cases, enabling organizers to run more reliable events.

Workflow

• Identify recurring hackathon pain points
• Define a self‑hosted architecture avoiding cloud dependencies
• Implement core stack: React + Express + PostgreSQL + Docker Compose
• Design for offline resilience: local storage, self‑contained services
• Add per‑judge score normalization to mitigate scoring variance
• Handle zero‑variance edge case in scoring algorithm
• Implement health checks, startup ordering, migrations, and deterministic seeding for Docker deployments
• Model judge assignment as a mathematical constraint to enforce feasibility
• Iterate on rules and constraints to cover edge cases (network failure, deadline passes, configuration impossibility, unauthorized access)

Evidence

Judging could feel inconsistent. Connectivity could become a bottleneck. Organizers were forced to stitch together forms, spreadsheets, messages, and separate tools just to run one event.

Source

The specification required the platform to work in a self-hosted environment without relying on cloud services.

Source

HackNext uses per-judge score normalization to reduce the effect of differences in scoring range and style.

Source

We explicitly handled the zero-variance case instead of pretending it wouldn't happen.

Source

Health checks, startup ordering, migrations and deterministic seeding became part of the product — not just deployment configuration.

Source