The software is finished. The evidence is not.
Everything is built and tested. I am seeking initial-phase pilot schools — there is no completed pilot yet, and what the software has never had is a real building full of real kids. That is the only thing left I cannot do on my own.
What a pilot involves
- How much
- One building, one semester, the whole thing. You do not get a cut-down version.
- Your data
- Stays on your machines as shipped, and leaves with you in open JSON if you walk.
- Stopping
- Yours to end whenever. Nothing to decommission, nothing held hostage.
- What is missing
- No completed pilot yet, no SOC 2 audit, no penetration test.
How a pilot runs
- Before it is approved
- Readiness is checked and the success criteria are set with your directors rather than handed to them, so the pilot is judged on what you chose. Candidate schools are identified and teams see the software before anything is signed.
- Once approved — onboarding
- Teams train in a sandbox before any of your student data is loaded. Administrator configuration and rostering preparation happen here, and the data-protection agreement is in place before go-live rather than alongside it.
- While it runs
- Operational use across the school year under the NDPA, with coaching rather than a support queue. Deadlines run live from the first day, which is the part a pilot is really testing.
- After it ends
- A summative evaluation against the criteria set at the start, then a go or scale decision that is yours. Reversible at any point before that, and your data leaves with you.
What we can show you, and what we cannot
As shipped, student records stay encrypted on your hardware, and nothing is sent anywhere unless two things your district controls are true at once: a destination you configured, and a data-protection agreement recorded in the system. The privacy page sets out the cryptography and both conditions in a form your IT director can check.
A SOC 2 report tells a district how a vendor protects the data it holds. In a pilot I hold none — which does not make the audit unnecessary, but it does change what you are exposed to while we run one.
What is not done: no completed pilot; the SOC 2 readiness artifacts are prepared and the audit is not yet booked; there has been no penetration test. You should hear that from me first. You can check the software today — open it, set your own passphrase, and walk a referral through to a plan.