Student information system
One system for admissions, records and student financials.
Guardian SIS keeps one student record from applicant to alumnus - admissions, registration, grades, transcripts, billing and financial aid - on one permission model and one audit trail.
1record
Applicant to alumnus. No re-keying.
1contract
One vendor accountable.
1,498tests
The status quo
One student. Four contracts. No single answer.
Most colleges run three or four separate systems - an admissions CRM, a student information system, billing and financial aid, and often an alumni tool. Student data is re-keyed between them and permissions are reconciled system by system.
So "who has seen this student's file?" is pieced together vendor by vendor.
Contract 1
Admissions CRM
Recruits applicants. Loses the record at enrolment.
Contract 2
Student information system
Owns grades and registration. Applicant data arrives by import.
Contract 3
Billing & financial aid
Separate logins, separate reconciliation.
Contract 4 (often)
Alumni & advancement
The graduate is exported - and the trail ends.
The student exists four times - and no two copies agree.
What we do instead
One system. One contract. One audit trail.
One record
The applicant becomes a student becomes an alumnus in one system - the admissions record and the academic record are the same row.
One permission model
One matrix defines what a Registrar, a Bursar, a faculty member, an advisor and an auditor may see.
One audit trail
Every access records who opened a file and why, in one log an auditor will accept.
The product
Six journeys, one sign-in.
Every screen here is a real capture of the product - no mockups. Request access and we set it up for your institution, with your name on it.
Admissions & Registration
Online applications, decisions and deposits; registration with prerequisites, capacity and holds.
Academic Records
Grades with an approval step, sealed transcripts with public verification, GPA and degree progress.
Student Financials
Invoices, payment plans and refunds; financial aid with packaging, SAP, R2T4 and 1098-T.
Academic Structure
Programs, courses, catalog, terms, departments and grade scales.
Advising & Alumni
Advising notes and degree progress; alumni records that continue the same record.
Governance & Reporting
Configuration, roles and permissions, audit reporting, IPEDS and institutional reporting.
Security & student-data protection
FERPA-aware, and provable.
Here is what we can demonstrate about student-data protection, rather than assert.
FERPA-aware by design
A role-based permission matrix decides what each role may see, and every access records who opened a file and why.
One college's records, one locked container
A college's records live in their own locked container; one college's data can never appear in another's.
A second factor
Sign-in can require a code from their phone, or the college login they already use.
An audit trail that can only be added to
Audit entries can only be added to, never edited, so a term's history still reconciles.
What an auditor actually asks for
Who looked at this student's record, when and why - one query against one log.
Where we stand
Pre-pilot, and honest about it.
No college runs its records on Guardian SIS in production today - so we show you a working product instead.
What you can verify today
- A tenant of your own, configured for your institution
- One permission matrix, purpose-logged access, an append-only audit
- One college's data can never appear in another's
What we do not have yet
- Production customers, or reference calls
- SOC 2 or ISO 27001 - we hold no certifications
What a founding pilot is
- Your data migrated by our team
- Direct access to the people building the product
Questions your committee will ask
Straight answers, including the awkward ones.
The product runs the whole cycle today - applications, registration, grades, transcripts, billing, financial aid, degree progress and reporting. What it does not have is a college's live term behind it; the founding pilot closes that gap, with our team running the migration beside you.
Weeks, not a multi-quarter consulting project: nothing to install on campus and no outside consultant in the middle. Structured imports accept what legacy systems and spreadsheets produce, migration is part of onboarding, and we map your real exports at the walkthrough.
No - we hold no certifications and badge none. What exists is the engineering those audits sit on: a single permission matrix, access that records who opened a file and why, an append-only audit trail, and each college's records in their own locked container.
Commercials are scoped per institution and discussed on a call; no rates, tiers or per-student prices are published here, because a figure that fits every institution fits none. One system also removes the handover between two - where the re-keying, the double reconciliation and the doubled contract live.
Request a demo
Book a 30-minute walkthrough.
Registrar views, bursar views, aid, transcripts and the audit log, on your own tenant and the workflows you run. Request access with one short form; we configure a tenant with your institution's name on it and hand it over, and your 30 days start when access reaches you.
Commercials are scoped per institution and discussed on the call. This page publishes no prices, tiers or per-student rates.
Nothing was sent — so this form will not say it was.
The demo-request endpoint could not be reached from this page. Your details are not lost: send them from your own mail client, with the message already written for you.
transport: not reachable from this origin · see DESIGN-NOTES.md → Form transport
Request received.
Thank you — a person from the product team will reply within one business day. We configure a tenant for your institution and hand it over; your 30 days start the day access reaches you.