Technical Requirements
Technical requirements and setup checklist for hosting KC7 events - simpler than you think
KC7 has minimal technical requirements. No special software, no servers, no IT expertise needed. If your participants can browse the web, they can play. This page covers what you need, what makes things easier, and how to test ahead of time.
Quick Requirements Summary
Internet connection (stable broadband recommended)
Modern web browser (updated within the last year)
Computer or laptop (tablets work but aren't ideal)
No installation required
π Detailed Requirements by Role
Event Hosts
Minimum: a free KC7 account at kc7cyber.com, internet access, an email address for the approval, and a basic computer.
Recommended: laptop or desktop for managing the event, optional second monitor, backup internet for virtual events, and a working mic and camera if hosting online.
Participants
Minimum: desktop, laptop, or Chromebook; updated Chrome, Firefox, Safari, or Edge; stable connection (3+ Mbps); 1024x768 or higher; keyboard and mouse or trackpad.
Recommended: full-size screen, wired internet, headphones for virtual events, and somewhere to take notes.
π Browser Compatibility
Fully supported: Chrome 90+, Firefox 88+, Safari 14+, Edge 90+.
Limited support: older browser versions and mobile browsers (playable but not optimized). Internet Explorer is not supported.
Make sure JavaScript, cookies, and pop-ups are enabled.
π« Venue Requirements
In-Person Events
Power outlets for everyone, WiFi that handles concurrent users, projection for instructions (recommended), and tables with computer space.
Network considerations: at least 3 Mbps per participant, standard HTTPS (port 443) open, no firewall blocks to kc7cyber.com, and guest network access if your main network is restricted.
Virtual Events
Host needs: a video platform (Zoom, Teams, Discord, etc.), screen sharing, 10+ Mbps upload, and a backup communication channel.
Participants need: access to the video platform, ability to view shared screen, and ideally a phone for video plus a computer for the game.
π§ Pre-Event Testing
One week before: test the participant link on multiple browsers, verify network capacity, check firewall and content filter settings, and test projection or screen sharing.
Day before: confirm all links work, run through with a sample participant account, verify venue WiFi credentials, and have backup access methods ready.
Day of: arrive early, fully test one machine before participants arrive, and keep IT support contact info handy.
π« Common Blockers & Solutions
School/Corporate Networks
Firewall blocking KC7? Whitelist *.kc7cyber.com, use the guest network, or fall back to mobile hotspots.
Content filters blocking the game? Request a temporary exception, work with IT to pre-approve, and test the week before.
Browser Issues
Old browser version? Update before the event or have an alternate browser ready.
Extensions interfering? Use incognito mode, disable ad blockers temporarily, or switch browsers.
π± Device-Specific Notes
β Chromebooks. Fully supported. Keep Chrome OS updated and check school management settings.
β οΈ iPads / tablets. Functional but not ideal. Smaller screens and touch interfaces slow people down. An external keyboard helps.
β Phones. Not recommended for play. Use them only for event communication.
π Bandwidth Calculator
Examples: 10 participants = 30 Mbps. 30 participants = 90 Mbps. 100 participants = 300 Mbps. Add a 50% buffer for headroom.
π‘ Pro Tips
For smooth events, test everything twice (week before and day before), have backup plans for internet and browsers, arrive early, and keep notes for next time.
For large events (50+ participants), stagger start times, line up dedicated IT support, test at maximum expected load, and have offline activities ready as a backup.
π Quick Troubleshooting
Can't access KC7: check internet, try a different browser, clear cache, disable VPN, check firewall.
Slow performance: close unnecessary tabs, check internet speed, try a wired connection, lower video quality on virtual events.
π Support Resources
For technical issues during an event, start with this checklist, then visit Discord for real-time help, or email [email protected] (24-48 hour response).
For pre-event planning, walk through requirements with your IT team, test the participant experience, and prepare contingencies.
Last updated

