RIVARO

The problem

School operations are split across timetabling, staffing, rooms and constraints that are usually held in separate spreadsheets. Changing one of them silently breaks the others, and nobody finds out until the day it matters.

The approach

Model the constraints once, in one place, and let every module read from that model. The platform is split into an API gateway and a web frontend so the intelligence layer can be called independently of the interface — and so a school can be given the interface without being given the engine.

The architecture

1. Nginx in front of two document roots — an API gateway and the web frontend
2. PHP application layer with a runtime autoloader and no Composer requirement in production
3. RI / VA / RO intelligence layers kept as shared platform logic behind the API
4. Mutating API routes audited through middleware into tenant and platform audit tables
5. SQL-first schema with a migrations directory
6. Browser-based installer for on-premise deployment

Result

Architecture designed around tenant isolation and auditability: every mutating route writes to an audit table, and deployment is an upload plus a browser installer rather than a manual package build.