Public home
A simple website or social page with current dates and contact details.
Field guide 001Built in Madison, WI
Build the community you wish existed.
Starting a local hacker community is free. Building one that lasts costs time, trust, and a few hard-earned lessons. Here is what we learned growing DC608.
Independent community guide · Not an official DEF CON publication
3+ yearsfrom an idea to a nonprofit, monthly meetup, and regional conference
Why bother?
We need local community now more than ever.
More of life happens behind screens. Hacker communities have always grown another way: through shared curiosity, patient mentorship, and learning beside one another.
A meetup can change someone’s career, confidence, or life. The strongest groups are not built by one exhausted person. They are built by teams who create something that can outlast any one organizer.
Part 01 / Begin
From “someone should” to a date on the calendar.
The official team decides how a group becomes recognized. Your job is to assemble the humans and make the local plan real.
- 01
Check the map
Look for an active or inactive group nearby. Reviving an existing chapter can preserve its name, history, and connections.
Open the official directory - 02
Find your people
Recruit two or three people who believe in the mission. Shared ownership prevents burnout and makes the group resilient.
- 03
Plan the basics
Choose a predictable cadence, an accessible venue, a public home, and one reliable communication channel.
- 04
Contact DEF CON Groups
Send the official team your proposal, location, organizer details, and the kind of community you want to build.
Official contact page - 05
Put a date on the calendar
Your first meetup can be small. A clear date and a welcoming room matter more than a famous speaker or perfect equipment.
Part 02 / Run it
You need less than you think.
A reliable way to find you, a place to talk, a place to meet, something to do together, and a schedule people can trust.
Community channel
Discord, Slack, email, or another place members can reliably reach you.
Welcoming venue
Accessible, safe, permitted for your activities, and easy to explain.
Consistent rhythm
Monthly or biweekly is easier to remember than an unpredictable schedule.
Programming
No speaker? No problem.
People return because of the community, not because every meetup has a keynote. Be ready to present yourself, cold-message interesting people, ask members to volunteer, and welcome virtual guests.
- Lock-picking night 01
- Hardware tinkering 02
- Hack The Box together 03
- Blue-team lab 04
- Project show-and-tell 05
- Coffee, food, and conversation 06
Part 03 / Sustain it
Build for the long game.
What follows is DC608’s experience—not legal, tax, or financial advice. Requirements vary by jurisdiction and change over time.
What worked for DC608
Make the invisible costs visible.
Starting recognition does not require a fee, but organizers may still encounter venue, platform, equipment, insurance, food, and accessibility costs. Track them before they become one person’s permanent burden.
What worked for DC608
Ask clearly and build momentum.
Your community may want to support work it believes in. Explain the goal and the numbers, line up early supporters, document how money is handled, and treat fundraising platforms as tools—not endorsements.
What worked for DC608
Choose a board for the mission.
Recruit for shared values, judgment, and follow-through. Learn your jurisdiction’s requirements, write governance before a crisis, hold regular meetings, and document decisions consistently.
Decision point
A nonprofit is optional.
DC608 used trusted guides and filed its own 501(c)(3) application. That route is not right for every group. Get qualified help when the stakes or uncertainty justify it.
IRS exemption applications“Don’t do this alone. Find partners who will share the work, challenge your assumptions, and carry the mission with you.”
Part 04 / Keep it safe
The Code of Conduct becomes real eventually.
Community safety is not a document in the footer. It is preparation, consistent decisions, careful communication, and people willing to act.
Respect anonymity, boundaries, and photography preferences.
Tell people who receives reports and how concerns are escalated.
Use a board or trusted co-organizers for consequential decisions.
Be factual and careful. Assume messages may eventually become public.
The goal is not universal approval; it is a safe and fairly treated community.
Part 05 / Take it with you
Steal these starting points.
Adapt these to your community and verify them against current local and official requirements. Nothing is stored or sent anywhere.
01PlanningOne-page group plan
Align your co-organizers before you announce anything.
GROUP NAME / CITY:
WHY THIS GROUP SHOULD EXIST:
WHO IT IS FOR:
CO-ORGANIZERS AND RESPONSIBILITIES:
MEETING CADENCE:
VENUE PLAN:
PUBLIC WEBSITE OR SOCIAL PAGE:
PRIMARY COMMUNITY CHANNEL:
FIRST THREE MEETING IDEAS:
HOW MEMBERS CAN ASK FOR HELP OR REPORT A CONCERN:02OutreachDEF CON Groups proposal email
A starting point—not a substitute for the current official instructions.
Subject: Proposal for a DEF CON Group in [CITY / REGION]
Hello DEF CON Groups team,
We would like to start or revive a DEF CON Group serving [AREA]. We checked the official directory and found [WHAT YOU FOUND].
Our organizing team is [NAMES / HANDLES]. We plan to meet [CADENCE] at [VENUE OR VENUE APPROACH] and communicate through [CHANNELS]. Our goal is to create a welcoming, all-skill-level community focused on [MISSION / ACTIVITIES].
We have reviewed the current DEF CON Groups guidance and Code of Conduct. Please let us know the next steps and any additional information you need.
Thank you,
[CONTACT DETAILS]03ProgrammingSpeaker invitation
Make the ask specific, friendly, and easy to decline.
Subject: Invitation to share [TOPIC] with [GROUP NAME]
Hi [NAME],
I help organize [GROUP], a local, all-skill-level security community in [CITY]. We would love to invite you to share [TOPIC] at one of our [IN-PERSON / VIRTUAL] meetups.
Our usual format is [LENGTH / FORMAT], followed by friendly Q&A. Possible dates are [DATES]. We can provide [EQUIPMENT / RECORDING POLICY / TRAVEL SUPPORT, IF ANY].
No pressure if the timing is not right. If you are interested, I would be happy to share more details.
Thanks,
[NAME AND CONTACT]04MeetupsFlexible meeting agenda
A repeatable rhythm gives newcomers confidence and organizers breathing room.
ONE WEEK BEFORE
[ ] Confirm venue access and accessibility
[ ] Confirm speaker or activity lead
[ ] Send the event reminder and Code of Conduct link
DAY OF
[ ] Test presentation equipment, Wi-Fi, and power
[ ] Identify the organizer handling safety concerns
MEETING
00:00 — Welcome, Code of Conduct, and announcements
00:10 — Newcomer-friendly introductions
00:20 — Main talk, workshop, or activity
01:05 — Break and informal conversation
01:20 — Questions, project sharing, or open discussion
01:45 — Next meeting date and ways to help
02:00 — Close05LogisticsVenue checklist
A useful room is safe, reachable, and comfortable—not necessarily expensive.
[ ] Accessible entrance, room, and restroom
[ ] Transit, parking, and clear arrival instructions
[ ] Enough capacity without feeling cavernous
[ ] Venue explicitly permits the planned activities
[ ] Power, Wi-Fi, display, audio, and adapters
[ ] Food and drink policy
[ ] Quiet option or lower-stimulation area when possible
[ ] Clear emergency exits and venue contact
[ ] Photography and recording expectations
[ ] Reliable opening, closing, and key-holder plan06CommunityNew-attendee welcome
A few deliberate sentences can turn an intimidating room into a community.
Welcome to [GROUP NAME]. We are glad you are here.
This community is open to every experience level; curiosity is enough. Tonight we will [FORMAT]. Questions are encouraged, and it is always okay to listen without introducing yourself publicly.
Our Code of Conduct applies to everyone. If anything makes you uncomfortable, you can speak privately with [ORGANIZER / REPORTING METHOD].
If this is your first time, an organizer can introduce you to a couple of regulars or help you find what you need.07MoneyBasic event budget
Make recurring costs visible before they surprise your organizers.
EXPECTED COSTS
Venue: $
Food / non-alcoholic drinks: $
Speaker support or travel: $
Equipment / supplies: $
Insurance / permits: $
Platform and payment fees: $
Accessibility needs: $
Contingency: $
TOTAL: $
EXPECTED SUPPORT
Donations: $
Sponsorship: $
Organizer contribution: $
Other: $
TOTAL: $
OWNER OF FUNDS / REIMBURSEMENT PROCESS:
NOTES AND RECEIPT LOCATION:08SafetyIncident documentation checklist
Record facts carefully and restrict access. For immediate danger, contact local emergency services.
DATE, TIME, AND LOCATION:
PERSON RECEIVING THE REPORT:
WHAT WAS REPORTED (USE THE REPORTER'S WORDS WHERE PRACTICAL):
PEOPLE INVOLVED AND WITNESSES:
AVAILABLE EVIDENCE OR LINKS:
IMMEDIATE SAFETY STEPS TAKEN:
REPORTER'S REQUESTED CONTACT METHOD AND DESIRED OUTCOME:
FOLLOW-UP OWNER AND DATE:
ACCESS RESTRICTIONS / SECURE STORAGE LOCATION:
Do not promise confidentiality you cannot guarantee. Share only with people responsible for handling the report and follow the current official escalation guidance.Your next move
Start small.
Start together.
Start now.
Someone near you is looking for a place to learn, contribute, and belong. Your first meetup does not need to be perfect. It needs to exist.
Before you announce
- Check the official directory
- Recruit co-organizers
- Define mission and audience
- Choose cadence and channels
- Plan a safe, accessible venue
- Read the current Code of Conduct
- Contact DEF CON Groups
- Schedule something simple
The talk behind the guide
Building a Hacker Haven
The Long Game of Growing a Local Hacker Community is presented by Ryan Zagrodnik and Allie Zagrodnik of DC608 at DEF CON 34.
Official talk listing