Synchronised load
Concurrency is not spread across the day. It is a spike at the top of each period, and your capacity plan has to be built for that shape.
Education & EdTech
Education platforms have the least forgiving load profile in software. Usage is not distributed. It arrives in a wall at the start of a lesson, from devices that are older than the students using them, over bandwidth the school cannot upgrade, and if it fails the failure happens to thirty children at once in front of a teacher who now has no lesson.
“Will it work on a school laptop, on school wifi, at the start of a lesson?”
The pressure
Concurrency is not spread across the day. It is a spike at the top of each period, and your capacity plan has to be built for that shape.
Chromebooks with four gigabytes of memory, tablets two operating systems behind, and a network shared with the whole building.
Learners and administrators want opposite things. One needs a system that gets out of the way, the other needs reporting, permissions and oversight.
The person who buys it is not the person who uses it, budgets are annual, and accessibility and data protection are gating questions rather than nice-to-haves.
The work
Four systems, all of which have to work on the worst device in the building.
Course delivery, assessment and progress that work offline-tolerant and resume cleanly when a connection drops mid-lesson.
Timed assessments that survive a dropped connection without losing a student’s work, and marking tools that give teachers time back.
Enrolment, timetabling, attendance and reporting, including the returns you are statutorily required to file.
A different audience again, on personal devices, checking one thing quickly.
The device floor
Every performance budget needs a worst case that is real. This is ours, and we publish it so you can hold us to it during procurement.
| Target | What it is | Budget | Why this one |
|---|---|---|---|
| Baseline laptop | Chromebook, 4GB RAM, 2019 class silicon | < 2.5s to interactive | The most common device in state schools, and the one that will still be in the cupboard in three years. |
| Baseline tablet | iPad 7th generation, two OS versions behind | < 3.0s to interactive | Shared trolley devices are rarely current and almost never charged. |
| Network | 4 Mbps shared, 120ms latency, 2% packet loss | < 400KB initial payload | A whole year group on one connection at nine in the morning. |
| Concurrency | 2,500 sessions arriving inside 20 seconds | 0 dropped sessions | The bell is the load test. There is no gradual ramp. |
| Interruption | Connection lost for 90 seconds mid-assessment | 0 lost answers | A student who loses work once will not trust the platform again, and neither will their teacher. |
| Accessibility | WCAG 2.2 AA, keyboard and screen reader | Pass before release | A procurement gate in this sector, checked rather than asserted. |
Non-negotiable
Where AI actually lands
Worth doing
Where we stop
Summative grading that affects a student’s record without a human deciding. The accuracy argument is beside the point; the accountability question is who answers to the parent, and it cannot be a model.
Evidence
We build platforms designed for thousands of concurrent users on school-grade bandwidth, load-tested against the start-of-lesson spike rather than an average day.
How we deliver it
Multi-tenant architecture, metering and billing designed in from the first sprint.
Fast, accessible applications that behave correctly on a bad connection.
Interface design grounded in how the work actually gets done, not how it demos.
Other sectors we work in
Next step
No discovery call with a salesperson, no deck. A senior engineer reads what you send and replies with a real assessment, including when we think you shouldn’t build it.
Certified, partnered and awarded
1/7
Start a project
A senior engineer reads every one of these, and replies within one business day. Nothing here goes to a sales sequence.
To begin
One click. It decides what we ask next.
The problem
One line is plenty. This is the part an engineer actually reads first.
Today
Pick any that apply.
Timing
A real deadline changes the design. An arbitrary one does not.
Size
A range is fine. It shapes what we propose, not what we charge.
Your side
It changes whether we lead, embed, or advise.
Last one
A senior engineer replies within one business day. No sequence, no newsletter.
How would you rather hear back?
Sent
Here is what you told us, and what happens next.