Omni Forge Software is a single, connected platform for K‑12 — student information, district operations, instructional walkthroughs, compliance auditing, tutoring and student learning. One sign‑on. One data core. One AI layer that can read across all of it.
Every product a district buys is defensible on its own. It is the space between them that costs the year — the exports, the re‑keying, the four logins, the report that has to be rebuilt every board meeting.
Attendance lives in the SIS. The walkthrough that would explain it lives somewhere else. The tutoring hours that should have followed it live in a third system. Nobody can put the three side by side without a spreadsheet and a Thursday.
Separate logins, separate rosters, separate permission models. Onboarding a teacher means touching five admin panels, and off‑boarding one means remembering all five.
Board packets, state filings, grant reporting, program evaluation — each one reassembled by hand from exports that were stale the moment they were pulled.
An assistant inside a single product can only answer questions about that product. The questions worth asking are the ones that cross all of them.
Each one is a complete product a district could buy on its own. Together they share an identity, a data core, and a set of records that never has to be exported.
The district’s front door to everything else. Ask a question in plain English and get an answer drawn from the systems you are already permitted to see — with a full account of what was read, what was refused, and what it cost to answer.
The AI‑native student information system. Enrollment, scheduling, attendance, gradebook, transcripts, discipline and truancy — a ground‑up replacement for the legacy SIS, built multi‑tenant from the first table.
The district operations console. Cross‑school dashboards, support workflow, and the district‑scoped public API with scoped keys, rate limiting and a browsable OpenAPI surface.
Instructional technology walkthroughs on a 1–4 integration rubric, with coaching follow‑ups, building and district roll‑ups, and executive dashboards that show whether the technology spend is actually reaching instruction.
Instructional Review Walkthrough. Build the review instrument once, run it every year; score by building, by classroom or by teacher; yes/no, percentage, numeric and narrative indicators; branded PDF reports that come out finished.
The student‑facing side of the suite. Assignments, flashcards, quizzes, a planner, focus sessions, mistake tracking and peer matching — with teacher, parent, specialist and district views over the top.
Tutoring delivered and managed end to end: family, tutor and admin portals, diagnostics, learning plans, live video sessions, session notes and progress reports published straight to families.
AI writing and plagiarism detection built for classrooms rather than for accusations — designed to open a conversation about a piece of work, with the district’s own AI‑use policy attached.
Every application writes into one district warehouse. Ask it a question in plain English and it answers from the real records — no export, no analyst, no waiting for the next board cycle.
One identity across the whole suite. A teacher is provisioned once and has exactly the right access everywhere; when they leave, one action closes every door.
This is the part a district never sees on a demo and feels every day afterwards. The suite is not ten products with connectors bolted between them — it is one platform that happens to present ten faces.
One sign‑on, one role model, one provisioning event across every application.
District → school → program. Isolation enforced in the query layer, the database views and the route guards.
Every meaningful change is an event, so history is reconstructable and nothing is silently overwritten.
The governed AI layer behind Atrium — policy checked before and after retrieval, models cleared per data class.
Nightly pipelines and live projections feeding dashboards, reporting and plain‑English queries.
District‑scoped REST with scoped keys, rate limits and an OpenAPI spec your team can browse.
Atrium is the front door to the whole suite: one place to ask a question in plain English and get an answer assembled from live records across every application. What makes it adoptable is not the answer — it is everything printed underneath it.
Atrium is only as good as what sits behind it. Because every application in the suite writes into the same district warehouse, attendance, instruction, tutoring, reviews and outcomes are already in one place and already joined — so the questions a cabinet actually asks stop being research projects.
Five applications’ worth of records already related, with no export step in between.
Projections, truancy evaluation, dashboard snapshots and asset book values, computed on schedule.
Board packets and program evaluations rebuild themselves instead of being reassembled by hand.
Every query is bounded by the asking district. There is no path to another district’s students.
The same student, the same identity, the same history — from the day the family enrols to the day the transcript is issued.
Families register once. The record propagates to every application in the suite immediately.
Scheduling, attendance and grading run in the SIS, with the student’s own study tools attached.
Technology walkthroughs and instructional reviews attach to the same schools and staff records.
Diagnostics, plans and live tutoring — measured against the attendance and grades that triggered them.
Transcripts, board reporting and program evaluation generated from the record rather than assembled from it.
Built multi‑tenant from the first table · not retrofitted
We will walk your district through the applications you actually care about, show you the data core underneath them, and be straight with you about what is mature and what is new.