For organizers
Sponsors and prizes people actually use
What sponsors actually want
A sponsorship budget is a marketing line item, not a donation. Pitch it as one: a challenge track puts their API in front of builders who might use it for years, a judging seat gives their engineers a reason to show up in person, and a named mention in your recap post is a backlink and a case study they didn't have to write themselves.
Apply through MLH first
Before cold-emailing individual vendors, apply as a Major League Hacking Member Event. One application unlocks a formal GitHub Education Grant (up to $1,000, paid 75% up front and 25% after you submit post-event data) and puts your event in front of MLH's existing sponsor network, instead of starting every vendor relationship from a cold inbox.
Vendor categories that reliably sponsor
Cloud and AI API credits
The easiest yes to get, because the vendor's marginal cost is near zero and the goal is simply putting their API in front of builders who might use it for years.
- AWS ActivateFormal credit tiers for startups and events, from low four figures self-serve up to six figures for qualifying AI programs.
- OpenAI, community hackathon supportDirect application form for API credits, Codex access, and prizes for community-led hackathons.
- Anthropic, Claude community ambassadorsFunds and API credits for organizers running Claude-focused meetups and hackathons in their city.
- GroqHas handed out flat per-participant API credits plus a larger bonus pool for the best project built on its inference API.
- PineconeRuns its own branded hackathons and shows up as a co-sponsor alongside AWS, OpenAI, Hugging Face, and LangChain on others; a good cold-email target if your event has a RAG or vector-search angle.
Identity and auth platforms
Free developer tiers here are already generous, which makes the sponsorship ask small: a challenge track and a booth, not a check. Two run formal, documented hackathon-sponsorship programs rather than just a free tier, worth applying to directly rather than cold-pitching.
- Auth0 (Okta)Free plan covers 25,000 monthly active users, more than enough for any hackathon build.
- SSOJet, hackathon sponsorship programWinning teams get a production-grade enterprise SSO Business License (2 SSO connections, unlimited auth, no expiration), 5-10 licenses per event. Minimum 50 registered participants, apply online, verified within 5 business days.
- WorkOSDeveloper-first API with a free tier built for exactly this kind of short-lived, high-volume experimentation.
- MojoAuth HackPassWinning teams get a passwordless-auth Business Pro license (5,000 MAUs, passkeys, SOC 2/GDPR/HIPAA compliance built in), 5-10 licenses per event, $3,000-$6,000 in annual value. Eligible: universities, nonprofits, MLH/Devpost-listed events. Apply 3+ weeks out.
Developer infrastructure and hosting
Deploy, database, and observability vendors sponsor for the same reason as the AI providers: cheap marginal cost, high visibility with exactly the audience they want.
- MongoDB AtlasFree tier plus a track record of hackathon-specific credit programs.
- DigitalOcean HatchCloud credits and mentoring aimed at early-stage builders; partners with Twilio Startups, so a joint pitch to both can work.
- GitHubCopilot and Education program access. The highest-leverage move: apply as an MLH Member Event (below), which unlocks a formal GitHub Education Grant application inside the same dashboard.
Communications and payments APIs
Not every sponsor needs to be infrastructure. Communications and fintech APIs sponsor for the same distribution logic, and they tend to have dedicated developer-marketing budgets.
- TwilioHas run hackathons directly on Dev.to with per-submission credit rewards; also reachable through its Startups program alongside DigitalOcean.
- StripeStartup program offers several thousand dollars in product credit plus a bundle of partner discounts, useful if your event has a fintech or marketplace track.
Design and prototyping
Less-documented territory. No major design tool runs a public, standing hackathon-sponsor program the way the categories above do, which just means the ask has to go directly to their developer-relations or education team rather than through a self-serve form.
Enterprise and CSR-driven sponsors
Large non-tech-vendor companies fund hackathons out of community-relations or social-good budgets, not developer marketing. The ask and the pitch deck look different: less about API adoption, more about visible community impact.
Compute-heavy and GPU events
If the event leans into model training, HPC, or GPU workloads, the standard credit-tier vendors above aren't the only option.
Running the event itself: free vs. platform
Registration, team formation, and judging are their own problem, separate from lining up sponsors. Two honest routes:
Free and open-source
A curated repo of hackathon tooling covers registration (Quill, HackAssistant, LaraHack), judging (Gavel), and queue management (HELPq), plus starter kits so teams stop losing the first two hours to environment setup. Right choice for most community and student events.
Enterprise platform
BrightIdea is an all-in-one hackathon platform (scheduling, judging, analytics) used by Adobe, Amazon, and Nike for internal innovation events. Worth the cost once you're running a company-internal hackathon at a scale where DIY tooling and spreadsheets start breaking down.
Sponsor tiers
Structure the ask before you send it. A vendor deciding between a $500 in-kind credit grant and a $10,000 title sponsorship needs to know which one you're asking for and what each buys them.
| Tier | Typical ask | What they get |
|---|---|---|
| Title | Largest cash or credit commitment, usually one per event | Top billing on every page and announcement, opening keynote slot, first pick of judging seats |
| Track / Challenge | Funds or credits tied to a specific problem statement | A named track with their branding, a dedicated prize, a judge on that track's panel |
| Infrastructure | In-kind: API credits, hosting, or tooling access, no cash required | Logo placement, mention in the participant welcome kit, inclusion in the recap's sponsor list |
| Community | Swag, small credit amounts, or venue/food support | Logo on swag or signage, a table at the event if in person |
For data-science-heavy events, Kaggle's competition structure is a useful prize-design reference: tiered cash prizes plus public leaderboard and notebook recognition, which rewards effort even for teams who don't place.
Outreach timeline
- 8+ weeks outApply as an MLH Member Event first. One application unlocks the GitHub Education Grant and puts you in front of MLH's existing sponsor network, instead of cold-emailing every vendor separately.
- 6-8 weeks outSend personalized pitches to the vendors in your specific tech stack, not a mass list. A DevRel inbox can tell the difference between a templated blast and someone who read their docs.
- 3-4 weeks outConfirm assets: logo files, API keys, credit codes, swag shipping addresses. This is where sponsorships quietly fall apart if nobody owns the checklist.
- 1 week outBrief judges and mentors on each sponsor's challenge criteria so scoring is consistent, and confirm who's showing up in person for a booth or keynote slot.
- Within 1 week afterSend every sponsor a short close-out: how many teams used their tool or API, who won their track, and a link to the public recap. This is what gets you a yes next year without re-pitching from zero.
What to put in the pitch
- Event name, exact date, and expected headcount up front. Vendors triage by scale before anything else.
- One specific ask: a dollar amount, a credit tier, or a named challenge track, not "whatever you can offer."
- What they get back: logo placement, a judging seat, a sponsor-branded challenge track, and a post-event recap that names them.
- A deadline. Sponsorship requests without one sit in an inbox until the event has already passed.
For where to find events in the Bay Area, see SF AI hackathons.
More on running a hackathon
The rest of this series: