No E-Rate application tells you what to do — your duty of care does. Independent and private schools choose filtering because families trust them with their children, not because a funding form demands it. Our category-based filtering covers the whole web, runs itself for a lean IT team, and reaches every device in the building, from school laptops to a boarder's phone on dorm Wi-Fi.
Private schools rarely have a district technology office behind them. The requests we hear are practical: protect the students, respect the older ones, and do not create a second full-time job for whoever runs IT.
With 120M+ domains already classified and new ones categorized as they appear, the filter makes almost every decision itself. Your team handles the rare exception, not a daily queue.
Category-level reports translate directly into the language of a parents' evening: here is what we block, here is why, and here is the record showing it works.
Student- and staff-owned phones and laptops join your Wi-Fi every morning. Network-level filtering covers them without installing anything on a device you do not manage.
Residence halls are home and school at once. Evening and overnight policies keep boarders safe around the clock without treating a seventeen-year-old like a third-grader.
Multi-category classification and open education categories mean upper-school students researching difficult topics are not walled off by a blunt, over-blocking filter.
A bundled blocklist of 16,328+ AI-tool domains lets you permit approved tools for coursework while holding back essay mills, deepfake apps and companion chatbots.
Public districts filter because CIPA ties their E-Rate discounts to a technology protection measure. Many independent schools never file that paperwork, so the legal trigger simply is not there. What is there is heavier: a promise made to every family at enrollment that the school will look after their child, online as much as anywhere else on campus.
That is why the strongest independent schools treat CIPA-style protection — blocking obscene material, child sexual abuse material, and content harmful to minors — as their baseline even when nothing compels them to. It is the recognized benchmark for what a school-safe internet looks like, and holding yourself to it is far easier to explain to a governing board than any bespoke standard.
Families choose an independent school deliberately, and they arrive with deliberate expectations. The same parents who ask about class sizes and pastoral care increasingly ask: what exactly happens when my child opens a browser on your network?
"We have a firewall" is not an answer that survives a follow-up. A named filtering policy — which categories are blocked, how policies differ by age, and who reviews exceptions — is. The schools that handle this best publish their approach plainly: a one-page summary for parents, a fuller policy for staff and governors.
When a parent challenges a blocked site, an explainable decision — this domain is classified as gambling, and our middle-school policy blocks gambling — ends the discussion in seconds. When an incident does occur, category-level logs show the school acted with reasonable care, which matters enormously to insurers, accreditors and the head's office alike.
Independent-school parents are quick to object if a filter blocks the genuinely useful — a debate-club source, a health resource, an art-history archive. Because domains carry multiple category labels and education categories stay open by default, the filter can be strict about harm without being clumsy about learning.
The strongest schools publish a one-page summary for parents, a fuller policy for staff and governors, and internet filtering for independent schools that quietly enforces both. If you are still comparing approaches, our guide on how to choose a school web filter walks through the questions worth asking before you commit.
A private school network is a jumble of devices the school owns, devices families own, and devices nobody thought to mention. The filtering has to see them all.
Independent schools often welcome personal devices — and then discover that no family will hand over an expensive personal phone for the IT office to manage. The practical answer is to filter at the network layer. When web filtering independent schools rely on runs at the DNS and network level, every device that touches school Wi-Fi is covered the moment it connects, owned or not.
Encrypted traffic does not create a blind spot, because decisions are made on the categorized domain rather than by peering inside pages. And for the devices the school does manage, policy follows them off campus, closing the take-home gap that network-only filtering leaves open. Our cloud-based web filtering for schools page covers the deployment side in more depth.
Many independent schools run technology with one person, a part-timer, or an outsourced MSP. The comparison that matters is not feature counts — it is hours of attention per week.
| The job to be done | Category-based cloud filtering | Manual lists on the firewall |
|---|---|---|
| Covering brand-new websites | Classified as they appear, blocked by category | Open until someone notices and adds them |
| Keeping protection current | Daily category updates, no action needed | Only as fresh as the last manual edit |
| Different rules by age group | Policies per grade band, house or user group | Duplicate rule sets to build and maintain |
| Handling a teacher's exception | One allow rule, scoped to who needs it | Edits that risk opening the hole school-wide |
| Evidence for governors & accreditors | Category-level reports on demand | Raw logs someone has to interpret |
| Weekly staff time required | Minutes — review exceptions and reports | Hours of URL chasing that never ends |
When an accreditor, an insurer or an anxious parent asks how the school protects students online, the answer should be a folder you can open, not a meeting you have to schedule. Filtering built on named categories produces that folder as a by-product of running.
A written statement of which categories are blocked for which age groups — short enough for a parent handbook, precise enough for a board minute.
Regular reporting that shows the protective categories are enforced in practice, not just written down — the same evidence E-Rate auditors ask public districts for.
A record of every allow and block exception, who requested it and why. Exceptions are where filters drift; a log is what keeps drift visible.
When something does happen, category-level history shows what the filter saw and did — the difference between a defensible response and a reconstruction from memory.
This matters more, not less, for schools outside the E-Rate system. A public district can point to a federal certification as proof it met a standard; an independent school has to be its own standard-bearer. A documented, enforced, reviewable filtering policy is how a private school demonstrates — to accreditors, to its board, and in the worst case to a lawyer — that it exercised the care families were promised. It also scales gracefully: a single-campus day school, a small group of affiliated schools, or a boarding school with a dozen buildings can all run the same model — one categorized view of the web, policies per age group and building, and one set of reports.
Our bundled AI-tools blocklist tracks 16,328+ AI-tool domains across 18 categories, screened from roughly 300,000 newly registered domains every day — because the AI tool your students found this week did not exist last month.
In high-achieving independent schools, the first AI worry is usually essay writers, paraphrasers and homework solvers that quietly do the work a transcript claims. The blocklist groups them so you can block the shortcut tools while permitting the AI platforms your teachers actually assign.
The blocklist tracks more than 200 deepfake and face-swap tools and over 470 AI companion and character-chat services — categories that in a school context are safeguarding issues, capable of producing fabricated images of real students or forming para-social attachments with lonely ones.
There is a quieter risk too: pupils pasting names, addresses and personal struggles into ungoverned tools that make no promises about where that data goes. Filtering these as categories closes the door before data leaves.
Because the AI landscape changes daily, governing it by hand is hopeless. Treating AI tools as filterable categories — the same way our web filtering software for schools treats gambling or adult content — turns an unwinnable chase into a policy decision. See pricing for how the blocklist is bundled.
In a boarding school the network is a residence, not just a classroom resource. Four moves turn one filter into a policy that fits daytime lessons, evening prep and lights-out equally well.
Classrooms, boarding houses, staff accommodation and guest Wi-Fi carry very different users. Naming each segment first lets every later policy decision attach to the right people and places.
Lesson-time policy can stay study-focused, while evening policy in the houses relaxes recreation categories — streaming, games, social — for older boarders. Policy by user group and building makes this a few rules, not a second system.
Whatever else flexes, categories covering adult content, self-harm and exploitation stay blocked at 2 p.m. and 2 a.m. alike. Late, unsupervised hours are precisely when that floor matters most.
Pastoral staff do not need packet captures; they need to know when a student in their house repeatedly hits blocked self-harm content. Category-level reporting turns network data into a safeguarding conversation.
Generally no — CIPA's requirements are enforced through E-Rate certification, so a school that receives no E-Rate discounts is typically not bound by them. Most independent schools filter anyway, because duty of care, parent expectations and accreditation reviews all expect it, and CIPA's standard is the natural benchmark to adopt. If your school does take E-Rate for any service, the same filtering supports the certification you sign.
Yes. Filtering applied at the network level covers every device that joins your Wi-Fi, with nothing installed on the device itself. A student's personal phone gets the same category policy as a school laptop while on campus. Off campus, personal devices are the family's domain — but school-managed devices keep their policy wherever they go.
Policies attach to user groups, buildings and time windows, so a boarding house can run a study-focused policy during prep and a more relaxed one afterward — opening streaming or games for older students while the core protective categories stay blocked all night. Younger houses simply keep a stricter profile around the clock.
That is the situation the design assumes. Categorization does the daily work — 120 million+ domains already classified, new ones added automatically, categories refreshed daily — so the human workload is a short exception queue and a periodic report review. Schools working with an outsourced MSP can delegate that access instead.
Be specific and be brief: which categories are blocked, how policy differs by age, that SafeSearch is enforced, and how a blocked-site appeal works. Because every block maps to a named category, you can answer any individual complaint with a reason rather than a shrug — which is what maintains trust.
Yes, and they should. Policies are set per grade band or user group, so upper-school students can research difficult subjects — history, health, current events — under a policy with fewer restricted categories, while the non-negotiable protections remain identical for everyone.
Either works from the same categorized dataset. Most single-campus schools choose cloud — nothing to rack, nothing to patch, and take-home coverage comes naturally. Schools with strict data-locality preferences or existing server rooms sometimes prefer on-premise. The policy language and reporting are the same either way.
A cloud deployment can be filtering campus traffic within days, because the heavy lifting — classifying the web into categories — is already done. The work on your side is pointing your network at the service, mapping user groups to your age bands, and confirming a starting policy. Most schools run a short pilot on one network segment first, then widen coverage building by building before the first day back.
Yes. Accreditation reviews increasingly probe digital safeguarding, and category-level reports give you exactly the kind of evidence a self-study section wants: a documented policy, proof the protective categories are enforced, an exception log, and an incident trail. Rather than writing that you take online safety seriously, you can attach the records that demonstrate it — the same artifacts that reassure insurers and your board.
Walk through category coverage, boarding-house policy design and the AI-tools blocklist with us — and leave with a filtering story you can tell parents, governors and accreditors with confidence.