Skip to content
ApexSutra

Industry

Education software.

Education software has a load profile unlike almost anything else: near-zero for months, then every student in the institution logging in during the same ninety-minute enrolment window. Add student data protection and a standards landscape older than most of the products in it, and the constraints are specific.

What shapes the architecture

Constraints that are specific to this sector.

These are the things that would be wrong or meaningless if written about a different industry. They are design inputs, not compliance paperwork added at the end.

  • 01

    Load is seasonal and brutally peaked

    Enrolment, results day and assignment deadlines concentrate a term of traffic into hours. Capacity has to be planned against the calendar, not an average — averages hide the only moments that matter.

  • 02

    Student records carry statutory protection

    FERPA in the US and India's DPDP Act both restrict who may see a student record and what may be disclosed to a parent versus an adult learner. Age of majority changes access rights mid-enrolment, which belongs in the data model.

  • 03

    The standards are old and must be honoured

    LTI for tool launch, SCORM or xAPI for course packages, OneRoster for rostering. They predate modern API design and cannot be improved on — they have to be implemented as specified, behind an adapter.

  • 04

    Assessment integrity is adversarial

    Any system that grades is a system some users will try to defeat. Timing, attempt limits and answer ordering have to be enforced server-side; a client-side timer is decorative.

Systems we build

Typical work in education.

  • Learning management platforms
  • Student information systems
  • Online assessment and proctoring
  • Admissions and enrolment workflows
  • Fee collection and scholarships
  • Parent and faculty portals
Integrations

What it has to talk to.

  • LTI 1.3
  • SCORM / xAPI
  • OneRoster
  • SAML / Shibboleth SSO
  • Payment gateways

Integration surfaces are where most sector projects actually fail. We treat each one as a boundary with its own translation layer, rather than letting an external format leak into the domain model.

Start here

Tell us the problem.
We'll be honest about the fit.

A first conversation costs nothing and is useful even if you go elsewhere — you'll leave with an architecture opinion and a realistic sense of scope.

  • Reply within 24 hours
  • No sales sequence