Ten applications.
Pick one. Or run the district on all of them.
Every product below is complete on its own — a district can adopt a single one and get full value. What changes when you run more than one is that they stop needing to be told about each other.
Atrium
The district’s 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 — and a full account, on every answer, of how it was produced.
Powered by Meridian, the suite’s governed AI service.
One question box, ten systems
Student information, attendance, truancy, staffing, facilities, board agenda, policy, audits — reachable from a single prompt.
It reads as you
Atrium inherits the permissions you already hold. It cannot open a record you could not open yourself, and it says so when it hits that wall.
The disclosure is the product
Every answer names the systems read, the systems refused, how many records you were authorised to see, and the sources behind it.
Models cleared per data class
Public, Internal, Confidential and Restricted. Each capability slot is filled by a model cleared for that class — and the choice is inspectable.
Proposals, not actions
Anything actionable arrives as a proposal with a named human who must approve it. Some decisions are configured so they can never be automated at all.
Cost and latency, every time
Which model ran, how long it took and what it cost. An AI budget becomes a number leadership can read rather than an invoice that arrives.
Omni Forge SIS
The AI‑native student information system — a ground‑up replacement for the legacy SIS rather than a skin over one. Multi‑tenant from the first table: one deployment serves many districts, and each district runs any number of schools inside it.
Cloud‑native, API‑first, mobile‑first, event‑sourced.
Enrollment & registration
Family registration, student records, programs and homerooms, with the district’s own org hierarchy underneath.
Scheduling
Course catalogue, sections, teacher assignment and student schedules across every school in the district.
Attendance & truancy
Daily and period attendance with nightly truancy evaluation that flags patterns before they become filings.
Gradebook & transcripts
Grading, report cards and transcripts generated from the record — including a print pipeline built for real district output.
Staff & portals
Staff, school and kiosk interfaces, invitations, password recovery and an issue‑reporting path that reaches a human.
Nightly operations
Projections, dashboard snapshots, asset book values and offsite backups run as scheduled jobs, not as somebody’s reminder.
Omni Forge HQ
The district’s operations console and its integration surface. HQ is where a superintendent’s office watches the whole district, and where your IT team gets a real API instead of a nightly file drop.
Cross‑school dashboards
District‑level views that roll up from every school without anyone assembling them by hand.
Public API v1
District‑scoped REST endpoints with bearer‑token authentication and a CRUD surface your team can build against.
Scoped API keys
Read‑only or full‑access keys, created by district admins, shown once, stored only as a hash, rate‑limited per key.
Browsable OpenAPI
An OpenAPI 3.1 spec with a Swagger UI, so integrating is reading documentation rather than filing a ticket.
Omni ITW
Instructional Technology Walkthrough. The tool that answers the question every district with a technology budget eventually has to answer out loud: is any of this reaching instruction?
1–4 integration rubric
A consistent scale applied the same way in every classroom, so scores can be compared across buildings and across years.
Fast walkthroughs
Built to be completed on a phone during the visit — not typed up afterwards from memory.
Coaching follow‑ups
Each walkthrough can open a coaching action with an owner and a due date, then close the loop on the next visit.
Executive dashboards
Building and district roll‑ups, trends over time, and reports a cabinet meeting can actually use.
Omni IRW
Build the review instrument once; run it every year. Omni IRW turns the recurring instructional review — classroom practice, program fidelity, building conditions — into a repeatable walkthrough with a finished report at the end of it.
Reusable templates
Author, version, lock and clone review templates so this year’s instrument is comparable to last year’s.
Scoring scopes
Score at the building level, per classroom, or per teacher — whichever the indicator actually calls for.
Indicator types
Yes/no, percentage, numeric and narrative indicators, mixed freely within one template.
Branded PDF reports
District logo, district language, generated at the end of the visit rather than written up the following week.
My Smart Study Partner
The student‑facing surface of the suite — and the one that has to earn its place with teenagers, not with a purchasing committee. Study tools students will actually open, with the oversight adults need wrapped around them.
Study tools
Flashcards, quizzes, rehearsal, notes, a planner and focus sessions — the daily mechanics of studying.
Mistake tracking
Wrong answers become the study set. Catch‑up paths are built from what the student actually missed.
Peer matching & teams
Students matched into study groups by class and subject, with teacher visibility over the whole thing.
Adult views
Teacher, parent, specialist, school and district portals over the same data — plus a published AI‑use policy page.
Omni Tutor
A complete tutoring operation, not just a scheduling page: three portals, live video, diagnostics, learning plans and progress reporting that reaches families without anyone writing an email.
Family portal
Next session, learning plan, session history, progress reports, diagnostics and messaging with the assigned tutor.
Tutor portal
Roster, today’s sessions, the in‑session video room, a session‑note builder and a weekly availability view.
Admin pipeline
Inquiry → consultation → diagnostic → matched → active, on a board, with one‑click conversion to a family.
Progress reports
Built by the tutor, published to the family, emailed automatically — and measurable against the record that prompted the referral.
Omni Forge Integrity
AI writing and plagiarism detection, designed for the conversation rather than the accusation. Integrity gives a teacher something to open a discussion with, alongside the district’s own published AI‑use policy.
Submission analysis
Signals on a piece of student writing, presented as evidence to read rather than a verdict to enforce.
Policy‑aware
Results sit next to the district’s stated position on AI use, so students and staff are held to one published standard.
Classroom workflow
Attaches to assignments in the suite instead of living as a separate tab and a separate upload.
Teacher judgement first
Nothing is auto‑escalated. The tool informs a professional decision; it does not make one.
Forge Data Warehouse
The reason the suite gets smarter as you add to it. Every application writes into one district warehouse — and you can ask that warehouse a question in plain English.
Cross‑application joins
Attendance next to walkthroughs next to tutoring hours next to review findings, already in one place.
Natural‑language Ask
Type the question the way you would say it in a cabinet meeting; get an answer from live records.
Nightly pipelines
Projections, truancy evaluation, dashboard snapshots and asset book values, computed on schedule.
Tenant‑scoped
Every query is bounded by the asking district. There is no path to another district’s students.
Omni Forge ID
One identity for the entire suite. Provision a teacher once and they have exactly the right access everywhere; when they leave, one action closes every door at the same time.
Single sign‑on
One credential across every application, with per‑district branding on the sign‑in page.
Passwordless option
Email‑code sign‑in with short‑lived, single‑use, hashed codes, attempt caps and per‑address rate limiting.
One role model
Roles and permissions defined once and honoured by every application rather than re‑implemented in each.
Clean off‑boarding
Deprovisioning is a single event — not a checklist of five admin panels and a hope.
Adopt one. Add the rest when you are ready.
Districts usually start with the product solving this year’s loudest problem, then add the next one once the identity and the data core have already paid for themselves.