Home/Solutions/Municipal & Education
Municipal & Education
Serve the mission. Account for the work.
Public-sector IT is two jobs at once. There is the work — a lab that has to be ready by 08:00, a clerk who has to publish an agenda before a meeting — and there is the paperwork that follows it, because everything you do is potentially disclosable, auditable, or a line in next year's budget hearing. Seraph does the first job and produces the second as a by-product, one record per machine, ready to release.
The characteristic ticket
07:40 on a state-testing morning.
Lab B is booked for testing from 08:15. At 07:40 the readiness check comes back wrong on thirty-one of the thirty-two machines: the exam lockdown extension is not loading after last week's image update. Your district IT team is two people covering nine buildings, one of whom is currently in a different building. Nobody is going to touch thirty-one machines by hand in thirty-five minutes, and the testing coordinator needs an answer, not an apology.
- 07:42 — one typed outcome, not thirty-one tickets. The outcome is stated once: the lockdown component loads and reports active on each machine in Lab B.
- 07:44 — one authorization from a named person. Your technology director sees what will run, on which machines, with what rights, and for how long, then approves once.
- 07:44 — thirty-one operations, not one. Each machine gets its own lease, its own job, its own check, and its own record. That is the difference between a batch and a fleet you can answer questions about.
- 07:50 — thirty come back verified by the machine itself. One never answers. Its declared undo runs, it is flagged for a person, and its record seals saying exactly that.
- 08:02 — the coordinator gets a list, not a reassurance. Thirty ready, one bench machine to swap, and a reference number for each.
The second job
When your operations record becomes a public record.
In this sector an IT record is not an internal artifact. It can be requested, it can be read out at a meeting, and it can be attached to a procurement file. Most tooling logs are miserable in that moment — either they say nothing useful, or they are so full of personal and system detail that releasing them means a review nobody has time for. The way out is not redaction. It is a record that never collected the sensitive thing in the first place.
The people who ask
Four audiences, one artifact.
| Who is asking | What they actually want | What you send |
|---|---|---|
| The superintendent, before a board meeting | To not be surprised in public session | The month's operations, each with the name of who approved it |
| The clerk or records officer | A response they can release without a week of review | A period export, in a format their system accepts |
| The testing or facilities coordinator | Which machines are ready, right now, and which are not | One record per machine, including the ones that failed |
| A grant condition or insurance renewal | Evidence that privileged access is bounded and reviewed | Leases with their scope and expiry, and the authorizations beside them |
Municipal and school district IT is not one market and we do not pretend it is. A district's pressure is the calendar — testing windows, term starts, a lab that must work at 08:15. A city or county's pressure is the meeting and the file — an agenda that has to publish, a record that has to be producible. The product is the same; the reason people buy it is not, and a demo that talks about the wrong one is a waste of your afternoon. Tell us which you are when you book.
The other half of the sector
The clerk, ninety minutes before the meeting.
17:35. Council convenes at 19:00. The clerk's workstation lost its mapping to the records share after a policy change, so the agenda packet cannot be assembled, let alone posted for the public notice period.
- It is not an emergency to anyone but the clerk — until the notice period is missed, at which point it is an item at the next meeting.
- The fix is small and well-understood. A certified runbook repairs the mapping, with the check that defines success and the way back written down before it runs.
- The authorization is a person, in one click, and their name stays on the work.
- The record is the minute. When somebody asks in three months why the packet posted at 18:12, there is a reference number rather than a recollection.
This is the shape of most municipal IT: low drama, hard deadlines, and a long memory. The value of a record here is not security theatre — it is that the answer still exists after everyone has moved on.
Straight about scope
What we do not claim here.
- No FedRAMP or StateRAMP authorization. We do not hold one, we are not in process for one that we can point you at today, and no page on this site implies otherwise.
- No CJIS claim. If your estate includes systems in scope for criminal-justice information policy, treat Seraph as out of scope for those systems until we have had that conversation properly.
- No student information system integration. We do not connect to your SIS or LMS and we do not process student records. The work is at the machine, service, account and update layer.
- We supply evidence; we do not attest. Where a framework matters to you, we produce the operational record your programme needs — never an attestation about it. Our own SOC 2 position is on the trust center.
On procurement: if your purchasing rules require a specific contract vehicle or cooperative agreement, ask us on the demo and we will tell you plainly whether we are on it, rather than sending you a brochure that implies we are. On records law: retention is configurable per client and records live in your own tenant's isolated storage, but your schedule is set by your state's law and your own policy, not by us. And on privacy — student records are your obligation under FERPA and your state's student-privacy statutes; the reason we mention it is that the safest way to help you with a records duty is to not hold the records, which is how this is built.
Fifteen minutes, on a live system
Bring the last records request that took a week to answer.
We will run an operation, produce the record, and export it in the format your response would go out in.