One source for product evaluation
See the whole platform before you schedule a call.
This guide documents current Classroom Guardian capabilities, the people who can use them, the deployment model, plan boundaries, and known gaps. It is written for school technology, teaching, safeguarding, privacy, and procurement teams.
Complete feature matrix
Implemented capabilities, stated precisely.
"Bryce Powers" and "Classroom Guardian" refer to the same product: brycepowers.org is Classroom Guardian's public website. "Available" means the capability exists and is enabled by the applicable plan. It does not mean every configuration or district scale has been independently validated.
Web filtering and access
Policy that follows the managed student identity and current class.
Classroom monitoring and control
Teacher tools remain limited to assigned classes and enrolled students.
Safety, writing, reporting, and operations
Evidence supports trained people; automation does not make disciplinary decisions.
Role and permission model
Every workspace has an explicit boundary.
Role checks are enforced by the service, not only by hiding navigation.
Assigned classes
Views enrolled students, current screens, class activity, access requests, classroom tools, writing evidence, and class-related safety reports.
Cannot browse another teacher's classesOne school
Manages people, licensing, school rules, categories, deployment, reporting, retention settings, integrations, and school safety review.
Cannot access a different schoolConnected schools
Manages district rules, inherited category decisions, connected-school oversight, and time-limited emergency scenes.
District membership is requiredService operations
Manages plans, school records, catalogs, final category decisions, billing, trials, and service operations.
Internal operational roleAdministrator guide
A practical path from pilot to daily operation.
- 1Create the school boundary
Confirm the school, plan, purchased student and teacher licenses, active administrators, retention choices, and approved domains.
- 2Connect identity and rosters
Register staff, create or import students and classes, test Google sign-in, and validate Google Classroom sync where configured.
- 3Deploy the managed browser
Build the school-specific package, choose the generated Google Admin, Windows, macOS, or Linux policy, and verify Chrome or Edge policy status on pilot devices.
- 4Publish policy deliberately
Set school allow and block rules, review managed categories, configure Safe YouTube, and test precedence with approved URLs.
- 5Validate classroom workflows
Test screen targeting, image refresh, open and close tab commands, scenes, access requests, teacher boundaries, and command acknowledgements.
- 6Review evidence and operate
Reconcile reports, review uncertain site classifications, monitor service status, document safety responsibilities, and record the pilot decision.
Technical architecture
Separate paths for policy, events, commands, and screens.
The diagram describes the current service design. It is not a claim of independent scale certification.
Clients check policy status and download the compiled policy only when its version changes.
A current screen target is issued only for active authorized viewing. Recording is a separate feature and action.
If the policy service is unreachable, filtering is designed to fail open rather than silently block unrelated academic access.
Automated category signals create recommendations. A platform administrator controls final managed-catalog publication.
Deployment and integrations
Managed-browser coverage across the devices schools already use.
ChromeOS, Windows, and macOS
- Google Admin policy for ChromeOS and Chrome
- Windows registry policy for managed Chrome and Edge
- Apple MDM configuration profiles for managed Chrome and Edge
- School-specific package, update channel, and platform-aware device inventory
Linux Chrome, Edge, and Chromium
- Generated managed-policy JSON
- Browser, operating system, architecture, and extension-version reporting
- Requires pilot validation before a school-wide assignment
Google identity and Classroom
- Google sign-in for registered users
- Google Classroom class and roster workflows when configured
- Connection, refresh, disconnect, and role behavior should be pilot-tested
ClassLink
- Preview, conflict detection, reviewed import, mapping history, and report-only removals
- No public production-ready vendor-sync claim
- Require an end-to-end demonstration for the school's tenant
Browser and pilot DNS coverage are not full MDM
- No native system-wide Windows, macOS, or iOS agent
- The DNS control plane requires an authorized resolver adapter; no hosted DoH/DoT appliance is claimed
- No current Microsoft Teams, Canvas, Schoology, PowerSchool, Infinite Campus, or OneRoster connector claim
Reporting and evidence
Reports answer specific operational questions.
Which websites were used, for how long, by how many students, and which actions or problems occurred during the selected 1-, 7-, or 30-day window?
Which named websites and actions were recorded for an authorized student, how do 7-, 30-, and 90-day totals compare, and can the bounded history be exported?
Which school-scoped records match a specific student, class, group, activity, reported platform, website, and time window—and who exported that scope?
Which classifier and model versions ran, how often did systems abstain or route work to a person, and what decisions are reserved for platform, school, or teacher review?
Which schools are reporting, how do enrollment and device adoption compare, what aggregate web activity and filtering outcomes occurred, and where do integration connections still need attention?
What activity, blocks, classifications, and operational summaries should the school administrator review each month?
Who created, reviewed, assigned, escalated, resolved, dismissed, or reopened a school safety report?
Which components are currently healthy, what response measurements are visible, and what incidents have been published?
District daily aggregate history and configurable retention are available as a pilot, but this is not a predictive or application-ROI warehouse. Verified guardian summaries, scheduled delivery, after-school policy, ClassLink reconciliation, delegated district roles, and DNS control-plane interfaces require school-specific validation. A hosted DoH/DoT resolver and dedicated regulatory-compliance dashboard are not currently offered.
Published pricing
Budget without waiting for a sales quote.
Current public USD pricing uses active student email licenses. Devices are unlimited. Standard paid subscriptions use a one-year contract unless the signed order says otherwise.
Core filtering, activity records, managed game catalog, licensing controls, and scalable device services. A 501-student school with 15 teachers is about $1,082 per year.
Adds live screens, classroom tools, assessment mode, and temporary access for everyday teacher control.
Adds screen recording, Safety Center, monthly reports, and site intelligence to the complete Classroom feature set.
Purchased teacher accounts are calculated separately from active student licenses.
Optional writing-review capability. District and custom plan terms may differ.
Includes 1 million combined grading tokens per enabled teacher in a shared school pool. Unused tokens roll for up to 12 paid months; each additional 1-million-token pack is $1.50 when administrator-approved overages are enabled.
Exact base access: Starter includes 3 of 13 capabilities, Classroom includes 7 of 13, and School includes 11 of 13. Essay Detection is a $0.50 per-student monthly add-on when not already granted; Priority Support is reserved for District or custom access. Assignment Grading pricing is published for planning but is not yet available in the live estimator.
Current limits
Do not assume what is not documented.
No independent filtering, essay-accuracy, or large-district performance study is publicly claimed.
No SOC 2 or equivalent independent security certification should be inferred.
Require availability and response commitments in the signed agreement when they are procurement requirements.
The Safety Center supports school staff; it is not outsourced human monitoring or emergency dispatch.
The product does not offer keystroke logging, TLS decryption, or native application, USB, print, and full-device remote control.
Activity trends describe recorded use; they do not predict risk, infer intent, or replace authorized staff review.
Last reviewed August 9, 2026. The live platform, public legal pages, current plan configuration, and signed school agreement control when they differ from this guide.
