Trust Centre · Reliability & data boundaries
Your school's records, safe when things go wrong.
One authoritative record for everything committed, caches that can always be rebuilt, and important work that's never silently lost.
How a change travels
From your click to a safe, finished job
One saved record, follow-up work that can't be lost, and a person when something needs deciding.
- You
A teacher saves the register
One click, one change.
- Source of truth
Record and follow-up saved together
The attendance record and the job to notify families are committed in one step—or not at all.
Cache · rebuildableWork queue · durable - Worker
Families are notified
Each attempt is recorded.
Done ✓Retried ↺ - A person
Anything unresolved is shown
An operator decides what happens next. Nothing fails silently.
Where the truth lives
One authority for committed school records
Authoritative state
PostgreSQL holds every committed school record as the single source of truth.
Disposable acceleration
Caches make things fast but never hold the only copy of anything—they can always be rebuilt.
Durable work intent
When a change needs follow-up work, the intent is saved with it, so nothing is silently lost.
Architecture direction
Simple to run, ready to grow
One platform model from a single school to a regional, isolated deployment.
Isolation
From shared hosting to a school-specific, regional deployment, on one migration-aware platform.
Backups
Not considered proven until a restore has been carried out and evidenced.
Regions
Your deployment's region is your choice, agreed and approved before go-live.
What we hold ourselves to
Recoverable, never silent
Always
- Commit the record and its follow-up work together
- Retry failures within a recorded policy
- Show anything unresolved to a person
Never
- Keep irreplaceable data only in a cache
- Drop a failed task without a trace
Recovery, proven
A backup counts only once it has been restored
Recovery is practised, not assumed.
Back up
School records are backed up on a schedule your deployment sets.
PlatformRestore
A backup is restored into a separate, safe environment.
OperationsCompare
The restored records are checked against the originals.
OperationsSign off
The result is recorded as evidence, and gaps are fixed.
Operations leadA person decides
Independent assurance
Reliability claims we can stand behind
We publish only what is independently verified. Ask us anything your review needs.
No figures we can't evidence
We don't publish uptime or recovery-time numbers until they're measured in your deployment.
No internal topology
Internal network details and security-sensitive operational information stay private.
Evaluating School Niva?
Ask the questions your review needs answered.
Security, privacy, AI or accessibility—we'll answer in writing.