Academic platforms
Institution-scale sites serving applicants, students and staff from one structure. Our published work includes an academic platform for NSUT.
Industry
Education & EdTech
Education platforms take a year of ordinary traffic in the first week of term.
What we build for Education & EdTech
Education software has a load profile almost no other sector shares. For most of the year the system is quiet, and then admissions or results day arrives and a year’s worth of traffic lands inside a few hours, on a date everyone knew about months in advance and cannot move.
That single fact should shape the architecture, and usually has not. Our academic platform for NSUT, published on our work page, was built around exactly this: the interesting engineering was the peak, not the feature list.
The second constraint is that education platforms have three very different audiences at once. Students, faculty and administration each need a different view of the same record, with permissions that hold up when a student is also a teaching assistant. Education software development that treats them as one user with a role flag runs into trouble in the second year.
Sector constraints
What makes this sector hard
Enrolment and results are the load test
Traffic is near zero and then everybody at once. Capacity is planned for those days and rehearsed before them, not measured afterwards.
The audience is four audiences
Applicants, students, faculty and administrators want different things from the same site. The navigation has to serve all four without becoming a directory.
Content outlives the people who wrote it
Departments publish independently and staff change. Without a structure that holds, an academic site becomes an archive nobody can search.
Deadlines are immovable
An admissions cycle does not slip because a release did. Anything touching enrolment ships well before the date or waits a year.
What we build for this sector
Peak-load architecture
Sized and tested for enrolment and results days, when a year of traffic arrives in an afternoon.
Departmental publishing
Letting departments publish on their own without the site turning into something nobody can navigate within three years.
Search and information architecture
Making a large institutional site findable by people who did not choose to be on it.
Capabilities this usually needs
Work delivered in this sector
Enterprise Academic Platform for NSUT
Engineering a Scalable Drupal Platform for a Premier Technical University
- Drupal
- PHP
- MySQL
Questions we get asked
Can the site survive results day?
That is the load it should be built for, and tested against before the day rather than during it. Capacity planned around an average is capacity that fails at exactly the moment it matters most. We run the test with you in advance, so the answer is something you have seen rather than something we have promised.
Departments want to publish their own content. Is that workable?
Yes, with a structure and permissions that hold. Independent publishing without either is what turns institutional sites into archives within a few years. The technical part is straightforward. The part that decides whether it works is agreeing what departments can and cannot change, and that conversation is worth having before the build.
Can you integrate with our student information system?
It depends what that system exposes, which we review first. Many institutional systems offer limited or awkward interfaces, and pretending otherwise at proposal stage is how projects slip. We will tell you what is genuinely possible before it goes into a scope.
Building something for Education & EdTech?
Tell us the constraints you are already aware of. Half of scoping a sector project is working out which of them are real and which are assumed.