Skip to main content
Running a hackathon usually means stitching together a form builder, spreadsheets, an email tool, a check-in app, and a website. None of them talk to each other. Harp brings that work into one system with one source of truth.

​
The problems it solves

​
Design principles

Configuration over code. The hackathon’s identity (name, dates, contact email, application schema, scan types, feature toggles) lives in the database and is managed from the super-admin UI. Renaming your event or changing the application deadline never requires a deploy. A stable platform with a fresh face. The participant portal stays familiar from year to year, while the public marketing site is deliberately separate and meant to be redesigned for every iteration of the event. See Architecture for how that split works. Built to be adopted. Harp is not HackUTD-specific. Another school can run it by deploying the services and filling in their own settings. See Adopting Harp.