Somewhere in every school, one person's spring belongs to the master schedule.
nOS exists for that person.
We are a small company in North Carolina. We build two things: a scheduling platform that places thousands of course requests and shows its reasoning, and a read-only assistant that answers questions about a schedule you already have.
The thing we care about most is that the schedule explains itself. Any program can produce a timetable. Very few will tell you what they could not do and why, or admit when a better answer exists and they did not find it. That is the difference between software you check and software you trust.
We do not publish customer names, logos or testimonials. Schools tell us things in confidence and we would rather keep it that way. What we will do is build against your real data on a call, in front of you, and let that be the evidence.
What we hold to.
The schedule should explain itself
Every unplaced request gets a reason. Every rule gets a price. Every build gets a ceiling to measure against.
Nothing changes without you
Changes stage before they commit, and sends preview before they write. There is no path where software edits your school's records on its own.
Say the limits out loud
There is a page on this site listing what nOS does not do. It is there because finding out in week three is worse.
Come and break it.
Bring the schedule you think is impossible. We will tell you honestly whether nOS can do it.