Hacker House

This is the official Zo House playbook for hosting a Hacker House. Whether it’s a 3-day builder sprint or a week-long residency, this guide will walk you through every step — from proposal to booking to post-event wrap-up.

Note: In Zo House SF, there are no stay facilities. Accommodations must be arranged separately, but the event flow remains the same.


Who is this for?

This template is for founders, devrel leads, product folks, and community managers looking to host an immersive building experience at Zo House, with both work and stay under one roof (except in SF).

1. Start Here: Get Approval

  • In the form or follow-up, submit a detailed requirements doc covering:

    • No. of days for the Hacker House

    • Accommodation needs (beds, max residents)

    • Food & beverages requirements (meals per day, dietary notes)

    • Agenda breakdown for each day (sessions, mentors, workshops)

    • Special arrangements needed (AV setup, internet boost, signage)

    • Outside vendor support (swag, sponsor booths, logistics)

  • Wait for approval from Zo HQ and the ground team (BLRxZo/SFO/etc.)

2. Booking & Logistics

If Zo House has rooms (most locations):

  • Book the entire property early — event space + all rooms

  • Confirm number of beds and allocate rooms in advance

  • Ensure cleaning and room prep before check-in

If SF Zo House (no rooms):

  • Arrange off-site accommodation (hostel, Airbnb, hotel)

  • Provide participants with location details, transport options, and check-in instructions

3. Set Up Registrations

Hackers / Participants:

  • Create a Luma event with:

    • Clear theme/title

    • Date, venue, and daily schedule

    • Details about accommodation (if applicable)

  • Add products@zo.xyz as a co-host

  • Refer to Zo’s Luma How-To Guide for setup

Demo Day or Open House Guests:

  • Optional: Create a separate Luma RSVP for guests attending the final day

  • Clarify if access is public, limited, or invite-only

4. Promote the Event

  • Use Zo House design templates or request creative help

  • Include Zo branding and logo in all visuals

  • Share Luma link across:

    • Twitter/X, Instagram, Telegram, WhatsApp groups

    • Dev circles, ecosystem pages, local college clubs

  • Tag Zo accounts and any sponsor/partner handles

  • Promote:

    • Hack themes

    • Mentors/speakers

    • Bounties, free housing, meals, merch

5. Event Day Flow

Day
Time
Activity

Day 1

Morning

Arrival, check-in, orientation

Afternoon

Kickoff session, welcome talks, house tour

Day 2–4

Full day

Hacking, mentoring, side sessions

Final Day

Afternoon

Demo Day (project pitches, judging)

Evening

Awards, photos, party/networking

Throughout:

  • Chill zones, snacks, content creation

  • Optional night jams or AM wellness sessions

Event Flow changes according to the no: of days and as per the teams (hosts) requirements.

6. Execution & Setup Guide

Zo’s House ops team will be on-ground to support.

Any AV or extra setup must be shared in advance for smooth operations.

What to Keep Ready:

  • Full event flow

  • Final participant & room allocation list

  • Mentor/speaker schedule

  • Event signage & branding assets

  • Luma check-in QR code printed/displayed

Standard Setup Includes:

  • Co-working space ready with tables, chairs, extension cords

  • High-speed internet

  • Projector or screen (if needed)

  • Basic sound system & mic

  • Portals activation (Digital screens at Zo used for displaying branded assets)

Extra Setup Options (request in advance):

  • Stage lighting

  • Extra monitors/screens

  • Whiteboards/flip charts

  • Swag tables

Food & Beverage:

  • Stocked snacks & beverages

  • Coffee/tea station

  • Catered meals (breakfast, lunch, dinner) — coordinate with ops

  • Dietary preferences handled in advance

Vendor Coordination:

  • If you need something Zo House doesn’t have:

    • Ops team will connect you to vendors for AV, catering, extra furniture, etc.

7. Rules & Revenue

  • Only approved hackers may stay/work—must be on Luma list

  • Zo Founder Members: First-priority access

  • No walk-ins without prior approval

  • Respect house rules: noise, shared spaces, cleanliness

  • If ticketed:

    • 21% of revenue goes to Zo House treasury

    • 79% goes to host (via Luma or other payment links)

8. After the Event

  • Share Demo Day highlights on Luma or social

  • Post content: group photos, recap thread, reels

  • Submit report & feedback to Zo ops team

See it in Action

Here is an example of a Hacker House luma -

This is how you should make a luma with banner and description detailing out the event agenda and vibes.

Below are some pictures from past hacker houses.

Previous Hacker Houses

DeFi Mania Hacker House
Algorand Hack Series

Last updated