Try the live demo

A web page, not a deployment.

Here's what MorningCount needs from your network, your devices, and your SIS. It's a short list.

Any device with a modern browser.

Interactive panels, teacher laptops, desktops, tablets. Touch is great; a mouse works just as well.

A device in each cafeteria with a browser.

Tablet, laptop, or phone.

A roster export from your SIS.

CSV with first name, last name or initial, student ID, teacher, grade, and building. A teacher ID column is recommended. We keep only the last initial.

Network access to one domain.

That’s the whole allowlist.

  • Nothing installs on devices or servers
  • No app
  • No agent
  • No database on your side

Three things per shared device.

  1. A persistent browser profile

    Not InPrivate, incognito, or guest mode, which wipes the device unlock every session.

  2. The board URL pinned

    Pinned or bookmarked, so the morning starts one tap from the home screen.

  3. The one-time device code

    Entered once. The screen stays unlocked for about six months.

Built for 8:30 AM.

Teacher laptops need nothing special: open the board and enter the code once. If your classroom panels run in kiosk or assigned-access mode, we send a short guide for keeping the profile persistent.

  • Every tap saves instantly and appears on the cafeteria report. Submit just marks the classroom done.
  • Offline picks queue locally and replay automatically when the connection is back, with randomized timing so 100 boards coming back at once don't pile on.
  • Boards detect the date change and roll over on their own. A pick left over from a previous day is never allowed to land on today's board.
  • The report reads live data. No host or edge cache can serve a stale count.

Load-tested on production · 100 classroom boards · 25 selections each · 20 minutes · 5 dashboards polling

95th-percentile write time
412 ms
Server errors
0
Latency, start to finish
Flat

Each building's traffic is constant no matter how big the district is, so scaling is a hosting-tier question, not an architecture question.

Works with the export you already have.

Upload a CSV from your SIS weekly, or whenever rosters change. Column names are matched flexibly. Student ID is the only match key; teacher ID keeps classroom identity stable through renames and building moves. Every import previews first, and large files apply in batches with resume. A command-line import is available for scripted workflows. If your SIS exports something unusual, we build the import to fit it.

  • PowerSchool
  • Infinite Campus
  • Skyward
  • eSchoolData
  • SchoolTool
  • any SIS with a CSV export
  • Automatic roster sync is on the roadmap; we build those connections in the order districts ask.

One settings screen.

Everything an administrator touches lives in a single admin console.

  • Master device code
  • Per-school report passwords
  • Revoke all devices
  • Tile-locking toggle
  • Meal options
  • Analytics toggle
How access and data are protected

Questions for the engineer?

Ask anything about hosting, rostering, capacity, or device setup. The person who built it answers.