MyPortal

An MIS that belongs to your school.

MyPortal is an information management system for UK schools — attendance, behaviour, exams, timetabling and reporting. One pupil record, one permission model, one audit trail, hosted wherever your data belongs.

UK schools Twelve modules Cloud or self-hosted

The MyPortal staff interface, showing a class attendance register

Why MyPortal

An MIS holds everything a school knows about a child.

That is a good reason to be careful about how it works.

Your data stays yours

Your data sits in SQL Server in a documented schema, and you can export all of it at any time at no charge. Migrating in or out is a database job with a documented procedure, and we will walk your team through it either way.

Permissions are the architecture

An MIS holds safeguarding notes, SEND plans and behaviour records. Access control and auditing are enforced centrally on every request, so the decision is made server-side each time rather than re-implemented module by module.

Hosted where you want it

Run MyPortal in our UK cloud, or deploy the same build inside your own tenancy so the data never leaves your infrastructure. Where it lives is a decision for your school and its DPO, and both deployments are supported the same way.

Modules

The whole school day, modelled properly.

Each module stands on its own, and every one of them shares a single permission model, a single audit trail, and a single source of truth.

  • Attendance

    Statutory session and lesson marks, registers, and absence follow-up.

  • Behaviour

    Incidents, sanctions, achievements, and the reporting behind them.

  • Exams

    Entries, seating, access arrangements, and results.

  • Assessment

    Marksheets, grade sets, and progress tracking across a cohort.

  • Curriculum & timetabling

    Subjects, classes, teaching groups, and the school timetable.

  • Students

    Registrations, contacts, addresses, and the full pupil record.

  • Staff

    Employment records, roles, and the permissions that follow them.

  • SEND

    Provisions, plans, and the review cycle around them.

  • Profiles & reporting

    Report cycles, comment banks, and published reports.

  • Admissions

    Applications, offers, and the route from applicant to on-roll.

  • Documents

    Attachments and file storage bound to the records they belong to.

  • Administration

    School configuration, academic years, terms, and system settings.

Who it is for

Three audiences, one database.

Staff, students and parents are served by the same system through role-based routing, so all three views read from one pupil record and stay in step by design.

  • Staff

    Teachers, tutors, pastoral leads and administrators each get a view built around what their role actually does, with permissions to match.

  • Students

    Timetable, assessment, behaviour points and documents, in a view appropriate to their age and to what the school chooses to share.

  • Parents and carers

    Attendance, reports and school communication, without a separate app to buy and a separate database to keep in sync.

Architecture

Boring technology, deliberately.

None of this is exotic. A school IT team should be able to read the stack, host it, back it up, and restore it without learning a new ecosystem first.

How it fits together
Backend
ASP.NET Core 8 Web API C#, long-term support release
Frontend
Angular 20 SPA Staff, students and parents, role-routed
Database
SQL Server 2019+ Versioned migrations, further providers planned
Auth
OAuth 2.0 / OpenID Connect Bring your own identity provider

Where we are

Under active development, and not yet holding live school data.

Core services and the foundational modules are in place, and the rest is being built out. We would rather tell you that now than sell you a timetable we cannot meet. If you are planning a change of MIS and want to shape one while it is still being built, this is the point at which that is worth doing.

Moving across

Leaving your current MIS is the hard part.

Every school we speak to has been burned by a data migration, or has heard from someone who was. So we treat it as a project with a named owner and a rehearsal.

  1. A conversation

    Tell us what you run now, your roll, and when your current contract ends. We will be straight with you about whether MyPortal fits yet.

  2. An environment of your own

    We stand up a private instance so your team can work through the modules that matter to you, hands on and at their own pace.

  3. A rehearsal migration

    Your real data, extracted from your current MIS and loaded into that instance, so mismatches surface now rather than in September.

  4. Cut over

    A scheduled switch at a point in the calendar that suits the school, with the old system kept readable behind you.

What that looks like in practice depends on what you are running now — tell us and we will be specific.

Bring us your hardest question.

Timetabling edge cases, a decade of historic attendance, a federation with shared staff — the awkward requirements are the interesting ones. Tell us what your school actually needs and we will tell you honestly whether MyPortal does it yet.