BugClub HQ for schools
Your students learn to find security bugs and report them properly. Same eight weeks as everyone else, a class of up to 12 and a whole week on permission before anyone opens a lab.
What we can set up for a school
Tell me how many students you have and when they're free. We'll work out the rest on a call.
A private class
Up to 12 of your students in their own cohort, on a day and time we agree on. After school or during a class period both work.
Seats in an open group
A few students can join the high school group, Thursdays, 5:30 to 7 PM Eastern, alongside students from other schools.
Progress for the teacher
If the teacher or program lead wants to see where each student is, week by week, ask about it when we talk.
One invoice
The school gets one bill for every seat, so families pay nothing. You can pay by card, or I can send an invoice. I take purchase orders too.
Nothing to install
Everything runs in a web browser, so school Chromebooks work. If your network filters sites, I'll send the list of domains to allow.
A syllabus you can check
Every week, lesson and lab is public, so you can hold it up against your standards before you commit to anything. See the eight weeks.
Safety, privacy and the rules
The course teaches students to look where they're allowed to and nowhere else. Students under 18 get a few extra protections.
Practice apps only
Every lab runs on apps built to be broken, inside each student's own sandbox. No real sites, including your school's. Week 0 covers ethics and the law, and week 1 stays locked until the ethics agreement is signed.
Parents stay in the loop
For students under 18, a parent or guardian co-signs the agreement and gets their own account showing progress, without seeing the student's work. What parents see.
No private messages between students
Students can't message each other. Outside live sessions, the forums are the only place students talk to each other, and the only private thread a student has is with me, about their own work.
Student data
We keep what the course needs and nothing for advertising. If your district has a data privacy agreement, send it over and I'll read it. Read the privacy policy.
Who teaches your students
Josh Brody
Instructor
I've written software for about 20 years and reported security bugs through bug bounty programs.
More about JoshI teach every live session and read every write-up. You'll find this when you look me up, so here it is first: I went to federal prison for hacking and internet piracy after a conviction in 2023.
It's why week 0 is about permission.
Pricing for schools
One price per seat or per class, paid once. Every seat includes the full course and a year of sandbox access after it ends.
One to four seats
$399 a seat, the same as everyone else.
Five or more seats
For five or more seats in an open group, email hello@bugclubhq.com and I'll send the details.
A private class
Up to 12 of your students, on your schedule. Email hello@bugclubhq.com and I'll send the details.
Tight budget
Title I schools, libraries and nonprofits: email me. The budget doesn't decide whether your students get in.
How it works
1. Email me
How many students, how old and when they're free. I reply within a day.
2. A call
About 20 minutes by video with you, and it's a casual chat. Bring your questions and your IT person, if you want.
3. Schedule and invoice
We agree on the group, the time and the price. You get one invoice for every seat.
4. Students sign on
Each student still applies and gets their own account, then signs the ethics agreement, with a parent or guardian for students under 18.
Bring it to your school
Email works best. Tell me a little about your students and I'll take it from there.