RoundUp K12Talk to us
In development · piloting with districts

Student records that hold up on a Tuesday morning.

RoundUp K12 is a web-first records platform for K-12 districts — attendance, grades, students and schedules in one place, built for the staff who keep them accurate rather than for the demo that sells them.

Book a walkthroughSee what is built

A real roster, not a screenshot — mark a few and watch the tally. Invented students, and nothing is saved: there is no API behind this page.

willamette.roundupk12.com

English 10 · Period 3

Room 214 · Tuesday, September 15 · Day B

no exceptions
  • Amara Okonjo
  • Beckett Lyle
  • Caleb Ruiz-Vance
  • Dashiell Moore
  • Elena Vasquez
  • Frankie Nwosu
  • Greta Lindqvist
7present0absent0tardy0excused
Six modules1built2in design3scoped

The product

One module you can use. Five we are not going to pretend about.

A student information system is judged on the unglamorous half — the August schedule conflicts, the state submission window, the record a registrar corrects at 4pm. We are building toward that, and we are not going to describe it in the present tense before it arrives.

Attendance

Built

Everyone starts present and the teacher marks only the exceptions — which is the actual classroom workflow, and what makes a period a thirty-second job rather than a roll call.

  • Five days of history on every row, so a pattern is visible without opening a report.
  • Present, absent, tardy and excused, each a colour and a letter rather than a colour alone.
  • A running tally that reconciles before you submit, not after the office calls.
PresentAbsentTardyExcused

It is in the hero of this page. Go and use it.

Designed, not shipped

Gradebook

In design

Assignments, weighting and posting, built so a teacher can enter a stack of papers without leaving the keyboard.

Students

In design

The record a registrar actually works from: enrolment, contacts, programme flags and the history behind each of them.

Scheduling

Scoped

Courses, sections and the master schedule, including the part nobody demos — the fifty conflicts you resolve in August.

State reporting

Scoped

The extracts your state asks for, generated from the same records staff maintain daily rather than reassembled each submission window.

Family access

Scoped

Grades and absences for parents. A responsive route first; a phone app when push notifications are worth the store review.

How it is shaped

Web-first for staff, phone for families.

Staff work at a desk

A registrar, an attendance clerk, a counsellor and a SIS admin all sit in front of a large monitor, and the work in front of them — schedules, transcripts, reporting — is spreadsheet-shaped. So the staff product is a web app with the density that implies, not a phone screen stretched sideways. Teachers use the same app; it is deliberately not scoped as a “teacher app”, because teachers touch two of the six modules and none of the reporting the district is liable for.

Parents genuinely have no desk

Family access is the part that belongs on a phone, and it earns a real app the day push notifications matter — a grade posted, an absence in second period. Until then a responsive route serves a parent perfectly well, and we would rather ship that than an app shell with nothing behind it.

Security and privacy

Student records, with the boundaries drawn first.

These are architecture decisions made before there was anything to protect, which is the only time they are cheap.

One district per origin

Every district is its own subdomain, so districts are separated by the browser's own origin boundary and not only by our code. Nothing is shared between them in a browser — that is the point of paying for subdomains.

Authorization from the session, never the URL

The hostname decides what a heading says. The API resolves the district from the signed-in session and authorizes every request on its own, so a wrong hostname costs a mislabelled screen, never another district's records.

Google Workspace and Microsoft sign-in

Those two identity providers, pinned deliberately. Districts already run one of them, and a narrow list is a smaller thing to get right than an open one.

Student records, treated as such

Built around the FERPA obligations a district already carries, with data residency in the United States. We hold no third-party audit yet, and we will tell you exactly what we can and cannot show you.

How two districts stay apartTwo districts, willamette.roundupk12.com and salem.roundupk12.com, run on separate subdomains. Because they are different browser origins, nothing is shared between them in the browser. Both talk to one API, api.roundupk12.com, which resolves the district from the signed-in session rather than from the hostname, and authorizes every request on its own.willamette.roundupk12.comsalem.roundupk12.comseparate originsnothing shared in the browserapi.roundupk12.comresolves the district from the session,never from the hostname above it
The hostname names the district. The session proves it. A wrong hostname costs a mislabelled heading, never another district’s records.

For districts

What working with us looks like right now.

  1. 01

    A walkthrough, with your data in mind

    Half an hour on what your registrar and attendance clerk do today, and an honest answer about which parts of that we can carry now.

  2. 02

    Your own subdomain

    Onboarding a district is a database row, not a DNS change. You get district.roundupk12.com and sign in with the accounts staff already have.

  3. 03

    One building, one term

    Pilots start narrow — a single school, a single module — because that is the size at which we can fix what you find while you are still watching.

Questions

The ones worth asking early.

Can we buy it today?

No. Attendance is the only module built, and we are not selling a student information system on the strength of a roadmap. What we are doing now is pilot conversations with districts willing to shape the rest.

Is this a replacement for our SIS?

That is the destination, and it is not where we are. Scheduling, transcripts and state reporting are what an SIS is actually judged on, and those are scoped rather than shipped.

Why a web app rather than an app for teachers?

Because the people who live in this system — a registrar, an attendance clerk, a counsellor, a SIS admin — are at a desk with a large monitor, and the work is spreadsheet-shaped. Teachers use the same web app. Parents get the phone companion, because a parent genuinely has no desk.

Who owns the data?

The district does. Export is a requirement of the record layer rather than a feature on a price sheet, and an exit should be as unremarkable as an import.

Are you the same company as RoundUp for early childhood?

Yes — same team, separate product. K-12 is organised around grade, course and section, with its own schema and its own backend, because an early-childhood system organised around age in months and licensing ratios is the wrong shape for a high school.

Tell us what your district does today.

We are choosing a small number of districts to build the next modules alongside. If yours is coming up on a renewal, or you have simply had enough of the one you have, that is a good conversation for us to have.

Book a walkthroughsupport@roundupk12.com