It reads every record, every night.
By the time the office opens, Kestrel has named the students who need attention and attached the evidence for each one. No dashboard to remember to check. The finding comes to you, and it brings its working.
Kestrel — the student record engine
Why it exists
Your student information system was specified before the iPhone.
It holds everything and tells you nothing. The data a school needs to act on is already in there — attendance drifting, a pattern of wellbeing entries logged by staff who have never spoken to each other, a family circumstance that changes what a term looks like. Finding it means knowing to look, or asking someone to write a report and waiting a fortnight for it.
Kestrel starts from the other end. The record does the looking.
What it does
Four things no system you are running does today.
Ask it a question in plain language.
Type the question you would otherwise put in an email to the one person who can write reports. Get the rows that answer it, with the record behind every row. Leadership stops queuing.
Admissions lives on the student record.
Enquiry, tour, application, offer, acceptance and enrolment on one record, with waitlists that understand how independent schools actually rank. There is no second CRM to buy, reconcile, and pay for twice.
It is open at its edges.
A documented API with no partner gate. Named integrations rather than a logo grid. And a published boundary stating what Kestrel will never try to be — so you can see the shape of it before you commit.
And the rest of it
The things that should not need selling.
Every one of these is included. None of them is a paid module, an add-on tier, or a line item in a renewal.
The statutory returnsCensus, Address Collection, STATS and NCCD, generated from the record you have kept all year rather than rebuilt from exports each August.
Sign-inPasskeys and single sign-on against the identity provider you already run. Phishing-resistant sign-in is not an upsell.
Access and auditWellbeing, medical and child-safety records governed separately, not lumped under one permission. Who saw and changed what, queryable.
Where it runsAustralian hosting, stated residency, onshore support.
MigrationA trial run your team validates before anything is committed, history brought across rather than summarised, and a read-only archive of the system you are leaving.
Dashboards and reportsThe ones you actually need, in the price.
The architecture
One system for everything was a workaround.
It made sense when school software rarely talked to other software. Every connection was a custom project, so the student record, finance, payroll and HR went into one box. The reason for the box has gone. The box has not.
You get the average of everything. No vendor is the best at student records, finance, payroll and HR at once — and you are tied to its weakest part.
One breach can reach everything. When wellbeing notes, staff bank details and family finances share a system, one weakness can expose all of them.
You cannot replace one part without replacing all of it. Outgrow the payroll and you are shopping for a new student record. It is why systems outlast the reasons they were chosen.
One record. Everything else connects.
Kestrel does the student record — every person, every enrolment, every family relationship, and who pays for whom — and does it properly. Finance, payroll and timetabling stay with software built for exactly those jobs, and the connection runs both ways: Kestrel sends them what they need from the record, and they send back what they produce.
The boundary
We are not trying to be your finance system.
Kestrel holds the family and fee-payer model — who pays, split percentages between separated parents, sibling links, scholarships, and the enrolment events that trigger a charge. That belongs on the student record.
The ledger does not, and neither does your communications and marketing platform.
What Kestrel does and does not do is published before you sign, not discovered after.
Why now
A system with no twenty-year-old compromises in it.
Kestrel is new, and that is the point. Nothing in it was shaped around a server in a cupboard, a desktop client, a nightly batch job, or a single report writer holding the only licence that can answer a question. The record is built around what a school actually asks it, which is why the answers come back in seconds.
Passkeys, access governed per record class, queryable audit, an open API and Australian hosting are not retrofits here. They were assumptions on day one. That is also why none of them is a paid tier — you cannot charge extra for the floor you built on.
Built for the schools choosing their next system, not for the ones still living with their last one.
Kestrel.
The student record engine, for Australian independent schools. Coming.