Classroom pilot FAQ
What teachers, principals, and school technology reviewers need to know about privacy, setup, devices, cost, and the difference between today's browser demo and future plans.
The current public demo is browser-local: video is analyzed on the device, and session history is stored in browser localStorage on that device. Video never leaves the device. Spoken audio goes to the browser's speech service (Google, Microsoft or Apple, depending on the browser) to make the live transcript. BrightSpeaker does not send student session data to a BrightSpeaker server in this demo path.
No. The current pilot path starts with the public browser demo, which has no student accounts and does not require a roster or teacher sign-in. Managed accounts are not part of the shipped pilot demo.
A current Chromebook running Chrome is the expected school-device path. The demo needs a modern browser plus microphone and camera permissions. Because district policies can block those capabilities, the first check should be a quick no-account demo on the actual classroom device.
There is no account or roster setup for the current demo. A teacher can open a short prompt and test the practice flow on one device before deciding whether a classroom pilot is worth discussing. The proposed pilot uses short speaking-practice sessions rather than a new grading workflow.
The current browser demo is free to try, and BrightSpeaker is exploring free classroom pilots first. Pricing is indicative: billing and paid school programs are not live, and any future school or district price would need to be confirmed in writing before a paid commitment.
Start with the live demo, the pilot overview, and the printable principal brief. Local browser session history can support a classroom conversation about prompts and feedback, but district analytics and a formal principal dashboard are not shipped features.
Available today is the public browser demo with speaking prompts, in-browser coaching feedback, and local session history. Teacher-managed classes, server reporting, district analytics, and paid rollout workflows remain future work. A pilot is for evaluating the shipped demo, not a promise that those roadmap items already exist.
No. The current demo does not include SSO, roster imports, managed class entry, or district account administration. Those capabilities should not be treated as available when a school evaluates the browser demo.
Keep evaluating
The principal brief summarizes the classroom fit, current privacy posture, and a focused 30-day evaluation path without treating roadmap features as live.