Education

One communication layer across campus

A campus is dozens of buildings full of screens that grew up separately: event boards in the commons, room schedules outside lecture halls, dining menus, shuttle trackers at stops, and donor recognition walls in the lobby. Most institutions run them on a patchwork of departmental systems — which means no single place to publish, no single view of what's actually working, and no way to reach every screen when it matters.

TelemetryOS turns that patchwork into one layer. Campus digital signage publishes events, announcements, and dining menus by building, department, or campus-wide schedule from one console. Room schedule displays read live bookings, shuttle boards show real arrival times, and wayfinding directories get visiting families from the parking lot to the right office during orientation week. Every device reports health, uptime, and proof of playback to the same dashboard.

The moment that justifies the whole system is the emergency. When something happens, an emergency alert override takes over every screen in every building in seconds — weather closures, lockdown instructions, evacuation routes — and because TelemetryOS devices play content locally, screens stay up and informative even if campus networks are degraded. When the all-clear comes, every screen returns to its schedule automatically.

A campus assistant that respects student privacy

Students and visitors increasingly expect to ask a screen a question and get an answer — where a building is, when the next shuttle leaves, how to reach the registrar. TelemetryOS Edge AI makes that practical for education: language models run entirely on the device, so a multilingual campus assistant on an interactive kiosk can answer in a student's own language without sending a single conversation to the cloud. No round-trip, no PII, no transcript of a 17-year-old's questions sitting in a third-party LLM provider's logs.

That assistant runs on Node Max, the edge-AI tier of the Node hardware family, which executes language models and computer vision on the device itself. The same hardware can count foot traffic through a commons to inform space planning, or spot a crowd forming where one shouldn't be — with all footage staying on-site. For institutions serving minors, on-device is not a nice-to-have; it's the only architecture that fits the policy.

Few campuses need AI everywhere. The common pattern is Node Mini on room schedules and menu boards, Node Pro on kiosks and large-format commons displays, and Node Max at the handful of high-traffic touchpoints where an assistant earns its keep. It's all one fleet, one console, one content pipeline.

Built for multi-building, multi-campus scale

Education deployments succeed on repeatability across buildings that were never built the same way. TelemetryOS applications are built once with the React SDK and deployed everywhere through a git-to-screen pipeline — a student developer or campus IT team pushes a change, and every screen across every building updates within seconds. Per-building content, per-department schedules, and per-campus branding are configuration, not separate installs.

For university IT and the integrators who serve education, the entire estate — kiosks, signage, and sensors on one platform — is managed from one console with fleet health, remote diagnostics, and proof of play, so a screen failing in a building across campus is a ticket, not a walk. See pricing for how device licensing scales from a single building to a multi-campus system.