For schools
Start with one route, not a rollout.
Kinnovar is in controlled pilots with a small number of schools. This page explains exactly who that suits, what your school gets, what we need from you to begin — and what we deliberately don't do yet.
Who the first pilot is for
The pilot is narrow on purpose. It works best for a school that can point at one real route and one real owner.
A good fit if your school…
- Runs its own transport, or works with a transport provider, on at least one route or pickup line
- Has someone who owns pickup and drop-off operationally — not just in name
- Can name one route or line to start with, rather than the whole school
- Can give a few hours across a pilot period, including a kickoff walkthrough
Not yet the right time if…
- Schools looking for academic records, exams, marks, or payments — those are not built and are not part of a pilot
- Schools needing a student-information-system integration on day one
- Anyone wanting to self-register and use a production workspace immediately
What your school receives
Four concrete things, all of them before or during the pilot — not after a contract.
A scoped pilot outline in writing
One route or one pickup line, a defined pilot period, named responsibilities on both sides, and the stop conditions — before anything starts.
A named founder as your contact
Not a ticket queue. One person who runs the kickoff walkthrough, the mid-pilot check-in, and the close-out review with you.
Answers on data before data moves
What is collected, who can see it, how long it is kept, how it is deleted, and what happens if something goes wrong — in writing, before your pilot begins.
An honest read at the end
A close-out review against criteria you agreed to. Either side can decline to continue with no further obligation.
Now, pilot, and later
What exists today — and what doesn't
Kinnovar is early. The clearest thing we can give a school evaluating us is an honest line between what is running, what a pilot covers, and what is still only intent.
Now
Discovery conversations and controlled pilot requests
What a school can do with Kinnovar today: talk to the founders about how its transport day actually runs, and ask to be considered for a controlled pilot. There is no self-service signup, and no product to log into yet.
- A 20-minute conversation about your current workflow
- A written pilot outline, scoped to one route or one pickup line
- Answers on data handling before anything is shared
Pilot scope
The workflow a pilot school actually runs
This is the validated first scope — deliberately narrow, so it can be proven in real mornings and afternoons rather than demonstrated in a meeting.
- Transport routes and assignments
- Recorded student handoffs
- Timely family notifications
- Exception handling with a named owner
- Auditable event history
- Role-based access for school, transport, and family users
Later
Broader school operations — subject to evidence and review
The longer-term intent is a school workspace that covers more of the school day. None of it is built, none of it is scheduled, and none of it is included in a pilot. Each item needs pilot evidence plus a documented privacy, security, and control review before it becomes work.
- A minimum student record, only where an approved workflow requires it
- Self-service school registration and workspace creation
- Wider school operations beyond transport
Explicitly deferred, and not part of any current offer: exams, marks, full academic records, payments, and student-information-system integrations.
Fictional product preview
See a school profile before you request access.
Explore a clearly labelled sample workspace for one route, recorded handoffs, exception ownership, family updates, and a privacy-aware directions concept. No account or live data is involved.
Open the sample schoolHow access actually works
Early school workspaces are created through a controlled onboarding process with the founders. There is no self-service registration, no account to create on this site, and no production workspace behind a login yet.
You send the request below
Business contact details and a description of your workflow. No student, guardian, route, or health information — the form says so, and we don't want it at this stage.
A 20-minute conversation
We ask how your transport day runs today and where it gets hard. You ask us anything, including the things on the Trust page.
A written pilot outline, if it fits
Scope, period, responsibilities, data rules, and success criteria — agreed with you before any workspace exists.
Founder-led onboarding
If you go ahead, a workspace for your pilot route is set up with you. This is a controlled, hands-on process today, not a self-service signup.
No account is created by this form. Kinnovar has no login, no self-service school registration, and no production student records today. Anything beyond the pilot scope above needs pilot evidence and a documented privacy and security review first.
Request school access
Tell us about your school and how your transport day runs. We reply by email to arrange a 20-minute conversation.