Skip to main content
Harp is three services around one source of truth: a Go API, a React portal for authenticated users, and a Next.js marketing site for the public.

​
The three services

​
Why the marketing site is separate

The portal and API are the stable platform: they carry over from year to year. The marketing site is the opposite. Every iteration of a hackathon should redesign it to match that year’s theme and identity. Keeping it as a separate application with a narrow contract (the public content API) means a fresh public experience never requires touching the platform. The marketing codebase is intentionally a basic template: a scaffold page that proves the backend connection, plus a data layer that consumes the public endpoints. You throw away the design each year and keep the data layer. See The marketing site.

​
Platform services

  • SuperTokens for authentication and OAuth (open source, managed or self-hosted)
  • PostgreSQL as the system of record
  • Google Cloud Storage for resumes and assets (optional in local dev)
  • SendGrid or SMTP for decision and notification emails
  • Web Push (VAPID) for browser push notifications
  • Apple Wallet for optional .pkpass event passes

​
Technology at a glance

  • Backend: Go, Chi, PostgreSQL (pgx)
  • Portal: React, TypeScript, Vite, Tailwind CSS, shadcn/ui
  • Marketing: Next.js, React, TypeScript, Tailwind CSS
  • Delivery: Docker-based local and production workflows