Hub-and-Spoke Topology
Teacher spokes, campus hubs, and HQ consolidation preserve daily continuity while keeping authority, validation, reporting, and governance in the right tier.
Architecture
Indelo is designed for African operating reality: imperfect connectivity, distributed campuses, sensitive records, teacher-side work, and long-duration institutional responsibility.
Teacher spokes, campus hubs, and HQ consolidation preserve daily continuity while keeping authority, validation, reporting, and governance in the right tier.
Teacher laptops operate on a scoped working set tied to assignments — not a full school replica — while campus hubs remain the operational authority.
Explore synchronizationTeacher spokes use encrypted local SQLite/SQLCipher working stores. Campus hubs and HQ run on Microsoft SQL Server — standard infrastructure DBAs already administer, back up, and trust.
User actions pass through business-rule validation, durable local storage, sync journaling, package verification, central validation, and SQL Server institutional authority.
Sync moves through portable media or customer-controlled networks. Connectivity is an optimization, not a dependency.
Academic structures, grade bands, terms, examination bodies, region labels, currency, and formats are treated as configurable data.
Indelo is built for Nigeria-first adoption and piloting with multi-campus school-group realities while preserving Anglophone African expansion readiness.
Packages carry migration-level information. Machines must converge on compatible application and database versions before synchronization proceeds.
Sync applies through the same business-rule repositories as local entry. Imported data cannot bypass guards, ranges, locks, approvals, or institutional controls.
Synchronization discipline
Packages are chained, signed, version-aware, and applied through the same business-rule validation as local entry — sync cannot bypass institutional controls.
Chained, verified synchronization packages detect and refuse silent modification, replay, gaps, out-of-order imports, and unsafe version drift. The goal is not merely to exchange data; it is to preserve confidence that campus history was not silently rewritten.
View Sync ArchitectureEnterprise deployment
Discuss academic records integrity, administrative governance, offline-first operations, teacher-spoke synchronization, SQL Server hub/HQ deployment, and multi-campus requirements.