Government and Education: Records and learning platforms, kept secure
We build and move the systems that public bodies and colleges depend on, from document workflows to e-learning, with citizen and student data protected.
What we build for public bodies and colleges
Online services stay open and quick on the busiest deadline day.
Students apply, upload papers and enroll online, at any hour.
Approvals keep moving from office to office, even at peak times.
Every record stays complete, searchable and in the region you choose.
Learning platforms grow for term time and fit each college’s courses.
People queued at offices for simple forms. With it, they apply online.
Admissions meant piles of paper. With it, students apply and enroll online.
Files waited on desks for a signature. Now they move on approval.
Old records took days to find. With it, staff open them in seconds.
The platform slowed at the start of term. Now it grows with students.
- Your usersThe people you serve, on any device
- Content delivery networkPages served close to each visitor
- Load balancerTraffic spread across servers
- Servers that scaleAdded for a rush, removed after
What it means for the people you serve
- Shorter queuesPeople apply online instead of waiting at an office.
- Faster decisionsFiles reach the next desk the moment they are approved.
- Records found in secondsStaff open old records without a trip to the archive.
- Learning that keeps upThe platform grows with students at the start of term.
Where we did this
A government body needed its file system to process documents faster.
Faster document processingGovernment file systemGovernmentRead the story: Government file system (opens in a new tab)A college needed its Moodle platform to take more users and protect student data.
A Moodle platform on AWSAustralian Global CollegeEducation, e-learningRead the story: Australian Global College (opens in a new tab)
Questions
Can our data stay in our own country?
Where your cloud has a region in your country, we keep the data there and write that choice into the design.
Who can see our records and students’ data?
A few named engineers, with access you approve under a written agreement, and removed when the service ends.
Will it cope with enrolment day or a deadline rush?
We size it from your real peaks, then review where it slows, as we did for a government file system that slowed at peak traffic. We promise no uptime figure.