Skip to main content
Print this page or save it offline before your hackathon starts for quick access when you need it most.

Must-have free credits

Claim these credits before your hackathon begins. Many require verification that can take time.

Vultr

$250-300 for 30 daysHigh-performance cloud servers with global data centers

Serper

2,500+ search queriesLightning-fast Google Search API

Twilio

1 phone number + $15Calling, SMS, and OTP integration

GitHub Student Pack

Copilot + $100+ creditsFree developer tools and cloud credits

Copy-paste starters

Get your project running in minutes with these starter templates.
# Backend
pip install fastapi uvicorn
uvicorn main:app --reload

# Frontend
npx create-react-app frontend
cd frontend && npm start
Minimal setup for building REST APIs with modern React frontend.

Environment variables template

Copy this template and fill in your API keys. Keep your .env file secure and never commit it to git.
.env
# Database
DATABASE_URL=postgresql://user:pass@host:5432/db

# AI APIs
OPENAI_API_KEY=sk-...
HUGGINGFACE_TOKEN=hf_...

# Search & Data
SERPER_API_KEY=...
FIRECRAWL_API_KEY=fc-...

# Communications
TWILIO_ACCOUNT_SID=AC...
TWILIO_AUTH_TOKEN=...
TWILIO_PHONE_NUMBER=+1...

# LiveKit
LIVEKIT_API_KEY=...
LIVEKIT_API_SECRET=...
LIVEKIT_URL=wss://...

# Deployment
VERCEL_TOKEN=...
Add .env to your .gitignore file immediately after creating it to prevent accidentally committing secrets.

Last-minute fixes

When things go wrong minutes before demo time, these fixes can save you.
Use Ngrok to expose your localhost when deployment doesn’t work:
ngrok http 3000
Give judges the ngrok URL instead. It’s not ideal, but it works.
from fastapi.middleware.cors import CORSMiddleware

app.add_middleware(
    CORSMiddleware,
    allow_origins=["*"],
    allow_credentials=True,
    allow_methods=["*"],
    allow_headers=["*"],
)
Quick SQLite fallback when your database won’t connect:
import sqlite3
conn = sqlite3.connect('hackathon.db')
Not production-ready, but gets you through the demo.

Judging day checklist

Use this checklist on presentation day to make sure you’re ready.
  • Record backup demo video (use Loom)
  • Test on mobile devices
  • Prepare 3-minute pitch
  • Have localhost running (+ Ngrok ready as backup)
  • Print architecture diagram
  • List all APIs used (show free tiers)
  • Prepare GitHub repo link
  • Battery charged, charger ready

Pitch structure (3 minutes)

Follow this proven structure for maximum impact with judges.
1

Hook + Problem (0:00-0:30)

Start with a shocking statistic OR personal story. Explain why current solutions fail.
2

Live Demo (0:30-2:00)

Spend 60% of your time showing the core feature working. Handle edge cases gracefully.
3

Tech Stack + Innovation (2:00-2:30)

Highlight free/open-source tools you used. Mention any novel approaches you took.
4

Business Model + Q&A (2:30-3:00)

Explain how it scales and revenue potential. Take questions from judges.
Judges remember demos, not slides. Spend most of your time showing your working product.

Debug commands

Common commands for fixing issues fast.
# Check what's using a port
lsof -i :3000
kill -9 <PID>
The git reset --hard command permanently deletes uncommitted changes. Make sure you want to lose that work before running it.

Resource limits

Know these limits and backup plans before you hit them during your demo.
ServiceRate LimitAction if Hit
OpenAI Free3 RPMUse Hugging Face
SerperDepends on tierCache results
Vercel100 GB bandwidthUse Netlify
Render FreeSleeps after 15mKeep-alive ping
Cache API responses during development to avoid hitting rate limits. Most services count requests, not cached responses.

Emergency contacts

Save these in your phone before the hackathon starts:
  • Teammate 1: [Phone]
  • Teammate 2: [Phone]
  • Faculty Mentor: [Phone]
  • Venue WiFi Password: [Password]
Take a screenshot of the WiFi password and save it to your device. You’ll thank yourself when the venue loses the paper with credentials.

Build docs developers (and LLMs) love