Student Information System for K-12 Schools

Yes. We ship pre-built export packs for the largest state reporting systems — CALPADS (California), PEIMS (Texas), PIMS (Pennsylvania), SIRS (New York), MSIS (Mississippi), and a configurable mapper for every other state. Each export includes the file layouts, code translations, and validation rules the state agency publishes, so submissions don't bounce back during the December and June reporting windows. For states without a pre-built pack, the Ed-Fi export typically satisfies submission requirements where the state operates an Ed-Fi ODS.

Yes. The SIS supports the Ed-Fi Alliance Data Standard v3.x and exposes an Ed-Fi ODS/API endpoint for student, staff, section, attendance, grade, assessment, and discipline domains. The Ed-Fi standard is the most widely adopted K-12 interoperability standard in the United States and is what state longitudinal data systems and EDFacts submissions increasingly consume. If your state agency requires Ed-Fi certification, we provide the certification artifacts and IMS Global OneRoster export as a fallback for districts whose vendors require it.

We provide an extract template for each of the four largest K-12 SIS vendors. From PowerSchool we pull via the PowerSchool API or the standard PowerSchool data extracts; from Skyward via the Skyward Qmlativ export; from Infinite Campus via the Campus Data Extract Utility; from Aeries via the Aeries SQL views. Cumulative records, historical grades, attendance history, transcripts, and discipline records all transfer. Plan on 8–12 weeks for a single district cutover with a parallel-run period through one reporting window so state submissions aren't disrupted.

It's a guardian engagement surface, not just grades. Parents see real-time attendance (period-by-period for secondary), current grades and missing assignments, standards-based progress, behavior incidents, lunch balance, immunization status, bus route, and upcoming fees. They can sign forms electronically (field trip permission, media release, handbook acknowledgment), update emergency contacts, and message teachers. Multi-guardian households get per-guardian permission control, which is critical for split-custody situations where one parent may have read-only access or be excluded from health data.

The system is built to support a district's FERPA compliance program. Per US Department of Education guidance, FERPA places the legal obligation on the educational agency, not the software vendor, so 'FERPA compliant' is technically a property of how your district configures and operates the system. What we provide: granular role-based access (so a substitute teacher can't see IEP data), full audit logs of every record view and export, directory-information opt-out flags per student, encrypted data at rest and in transit, and a signed data privacy agreement that meets the Student Data Privacy Consortium (SDPC) National Data Privacy Agreement template used by most US districts.

Per-student licensing from the incumbents typically runs $8–$22 per student per year for the SIS module alone, before add-ons like gradebook, parent portal, state-reporting toolkits, or scheduler — many districts end up at $15–$30 all-in. Our Community Edition is $0 in license fees; you pay for hosting (or self-host on district hardware) and optional implementation/support. For a 5,000-student district, that's typically a $75K–$150K annual line item that becomes a one-time implementation cost plus modest hosting. The break-even is usually inside year two even after counting migration labor.