Networking
Wireless and campus network design sized for peak density rather than average, plus access control that can tell a student device from a staff one without a help desk queue.
Education
Load that arrives on one morning, and identity that turns over every year.
What we see in this sector
Not an industry primer — you know your sector. These are the technology pressures we are most often called in for.
- Demand that is not smooth: registration, term start and examination periods put a year's peak into a few days, and the rest of the year hides the problem.
- An identity population that turns over annually by design, with accounts, devices and access to provision and reclaim at scale.
- Campus wireless expected to work in lecture halls at full occupancy, libraries, residences and outdoor space — four different RF problems sold as one.
- Research and administrative data on the same estate as a large, young, deliberately curious user population.
Which of our domains answers what
The point of this page: from a sector pressure to the technology domain that addresses it, and the delivery model that fits how you buy.
Cybersecurity
Security work scoped for an open academic culture: segmentation and monitoring that protect administrative and research systems without turning the campus into an enterprise LAN.
Cloud
Cloud capacity for workloads that spike predictably — enrolment, results, virtual labs — where elasticity is genuinely worth paying for rather than fashionable.
Software & Platforms
Learning and administrative platforms integrated with the student record, with single sign-on that survives the annual turnover instead of being rebuilt each August.
How it is usually delivered here
Academic calendars decide everything. Implementation lands in vacation windows, managed operations carry the term, and a training workstream matters more than usual because institutional teams are small and long-serving.
Regulatory and compliance considerations
Read the labels. A named standard is a thing that exists; a question is a thing we help you establish for your organisation — and we will not tell you what your obligations are from a web page.
Student data protection
A question we help you answerObligations around student records — including minors, where applicable — differ by jurisdiction and by whether you are a public or private institution. We establish yours with your registrar and legal counsel before designing access and retention, rather than applying a general privacy assumption.
Research data and funder conditions
A question we help you answerResearch grants frequently carry their own data handling, residency and retention conditions, which can be stricter than the institution's baseline. We ask what your active grants require, because these obligations are usually held by researchers rather than by IT and are discovered late.
Accessibility standards
Named standardLearning platforms reach students with a wide range of needs, and WCAG 2.2 AA is the benchmark most institutions and their procurement teams work to. We build learning-facing work to it as standard and test it, because in education the obligation is also pedagogical, not only legal.
Acceptable use and monitoring limits
A question we help you answerHow far an institution may monitor network use, and what it must disclose, is a policy and legal question with real technical consequences for logging design. We establish your position with your general counsel first, then build the telemetry to match it — not the reverse.
Nothing on this page is legal or regulatory advice, and it names no article numbers, effective dates or authority determinations. Your obligations depend on your licence, your jurisdiction, your data and your regulator's current position — which is exactly what the assessment establishes, in writing, before any design work starts.
Continue reading
Start with an assessment
The fastest way to a useful answer is a short, scoped look at what you already have.