Streaming infrastructure built for schools, not consumer apps.

The shortcuts that don't work

What schools try when they bolt this together themselves — and why it fails.

• DIY cameras + WhatsApp

  Public RTSP links shared in group chats. No access control, no expiry, no audit. Forwarded to whoever, forever.

• Generic CCTV portals

  Designed for security, not parents. 24/7 by default, no scheduling, no per-room access, no per-parent visibility limits.

• In-house dev

  You ship one MVP; then you're on the hook for codec changes, browser quirks, DPDP data-subject requests, and the night the cameras go offline.

What you get

• Live monitoring

  See every active stream across every branch in one operator console. Health badges, viewer counts, codec details.

• Per-school access control

  Operators see only the schools they own. Owners see all of theirs. Granular, role-based, enforced server-side.

• Health & auto-recovery

  Continuous TCP probes, codec and resolution drift detection, and a Stream Doctor to bring stuck streams back without manual intervention.

• Scheduled viewing windows

  Configure class timetables once. Parents only see streams during those windows. Mark a child absent and their stream goes dark that day.

• Audit log

  Every operator action — add, suspend, move, schedule change — is recorded and filterable by user, action, and time.

• Parent portal

  A hosted parent portal we run for you. Per-room access, mobile-first split layout, sticky player. No app store.

• Inside the app you already run

  Live classrooms in the parent app or school platform families already use. Your brand. The school still sets the window.

• Billing & analytics

  Per-stream pricing, monthly invoices, per-customer session telemetry. Know what you're selling and what people watch.