> For the complete documentation index, see [llms.txt](https://docs.kc7cyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kc7cyber.com/planning/technical-requirements.md). # Technical requirements This is the reference for what KC7 needs to run, broken down by role and venue type. If your participants can browse the web, they can play. ## Quick summary * Stable broadband internet * A modern browser updated within the last year * A computer or laptop (tablets work but aren't ideal) * No installation ## Requirements by role ### Hosts **Minimum.** A free account at [kc7cyber.com](https://kc7cyber.com), internet, an email address for the approval, and a basic computer. **Recommended.** A laptop or desktop, an optional second monitor, backup internet for virtual events, and a working microphone and camera if hosting online. ### Participants **Minimum.** Desktop, laptop, or Chromebook. Updated Chrome, Firefox, Safari, or Edge. A stable connection at 3 Mbps or more. 1024x768 resolution or higher. Keyboard and mouse or trackpad. **Recommended.** A full-size screen, wired internet, headphones for virtual events, and a place to take notes. ## Browser compatibility | Support | Browsers | | --------------- | --------------------------------------------- | | Fully supported | Chrome 90+, Firefox 88+, Safari 14+, Edge 90+ | | Limited | Older browser versions, mobile browsers | | Not supported | Internet Explorer | JavaScript, cookies, and pop-ups must be enabled. ## Venue requirements ### In-person events You need power outlets for everyone, WiFi that handles concurrent users, projection for instructions (recommended), and tables with computer space. For network, plan 3 Mbps per participant or more. Standard HTTPS (port 443) must be open. The network can't block kc7cyber.com. A guest network helps if your main network is restricted. ### Virtual events **Hosts need** a video platform (Zoom, Teams, Discord), screen sharing, 10 Mbps upload or more, and a backup communication channel. **Participants need** access to the video platform, the ability to view a shared screen, and ideally a phone for video alongside a computer for the game. ## Test before the event **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, and keep IT support contact info handy. ## Common blockers ### School and corporate networks Firewall blocking KC7? Whitelist `*.kc7cyber.com`, switch to the guest network, or fall back to mobile hotspots. Content filter 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? Switch to incognito mode, disable ad blockers temporarily, or change browsers. ## Device notes | Device | Supported | Notes | | -------------- | --------------- | ----------------------------------------------------------------------- | | Chromebook | Yes | Keep Chrome OS updated. Check school management settings. | | iPad or tablet | Functional | Smaller screens and touch slow people down. An external keyboard helps. | | Phone | Not recommended | Use only for event communication, not play. | ## Bandwidth calculator ``` Required Bandwidth = Number of Participants × 3 Mbps ``` | Participants | Bandwidth | | ------------ | --------- | | 10 | 30 Mbps | | 30 | 90 Mbps | | 100 | 300 Mbps | Add a 50% buffer for headroom. {% hint style="warning" %} Test KC7 access from school or corporate networks well in advance. Some networks block cloud services or require IT approval for whitelisting. {% endhint %} ## Tips for large events For 50 or more 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 For technical issues during an event, start with this checklist, then visit [Discord](/community/getting-help.md) for real-time help, or email for a 24-48 hour response. For pre-event planning, walk through requirements with your IT team, test the participant experience, and prepare contingencies. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kc7cyber.com/planning/technical-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.