Common questions about hackathons.

No. BetaHacks events are free to attend. RSVP on Luma so we know how much food and space to plan for, then show up ready to build.

Head to the Events page for upcoming dates and the Luma RSVP link. You can also leave your email on the homepage and we will send you details before the next hackathon.

A laptop, charger, and whatever dev tools you normally use. We provide Wi‑Fi, meals, and snacks during the event. If you have a favorite keyboard or monitor, bring it — but it is not required.

Yes. Many attendees arrive without a team. Check-in and the opening block are designed for meeting co-founders and forming groups. Solo builders often find teammates in the first hour.

Most teams are 2–4 people. There is no hard cap, but smaller teams tend to move faster and give everyone a real role in the demo. One submission per team.

Ship something real in 48 hours — a working product, not a slide deck. Each event has optional tracks (agent-native GTM, MVP speed-run, infrastructure, and a wildcard), but you can build across tracks or pick your own problem.

No. Sponsors often run workshops and offer credits, but you are free to use whatever stack fits your product. Build what you would actually use.

Final demos are reviewed by operators, founders, and partners from the BetaHacks network. There is also a ranked-choice audience vote. Judges look for a clear problem, a working product, and a team that can keep building after the weekend.

Each team gets a strict 3-minute slot. Use three slides: team intro, product overview with architecture, and a live demo. Submissions close at the deadline — late entries are not accepted.

Top teams receive fellowship invites into the Beta Fellowship — a 4-week structured program with weekly goals, mentor access, and accountability. Investment of up to $50,000 is awarded after the fellowship, not at the hackathon itself.

The main outcome is a fellowship invite and a path to investment. Some events include sponsor perks or credits, but the prize that matters is getting into the program and in front of partners.

A 4-week program for hackathon teams we want to back. Cohorts are typically 8–12 teams. You set weekly goals, get mentor access, and stay accountable to shipping — the same intensity as the hackathon, with more runway.

At the end of the fellowship, partners review every team. Selected companies receive up to $50,000 and join the BetaHacks portfolio. No pitch deck required — we have already seen you build.

Not necessarily. The hackathon is a starting line, not a single gate. Keep building, stay in touch, and come back to the next event. Many strong teams take more than one weekend to find the right co-founder or idea.

Most BetaHacks hackathons are in San Francisco. The exact venue and address are on the Luma event page and the Schedule page for each upcoming event.

Plan for a full weekend — roughly 48 hours of building with scheduled blocks for check-in, workshops, meals, final demos, and an award ceremony. The day-of agenda is on the Schedule page.

Yes. Meals and snacks are covered during the event. Dietary needs vary by venue — check the Luma listing or ask an organizer at check-in.

Yes. The space stays open during build blocks, but you are responsible for your own equipment. Most teams stay for the key sessions — opening, submission deadline, and demos.