Skip to main content
Software Engineering

Full-Stack School ERP

Designed and shipped a full-stack ERP end-to-end — from requirements through deployment — consolidating student records, attendance, finance and communication, with notification, messaging and authentication capabilities serving the whole institution.

Professional Work2024 – 2025Tags: ERP, Full-Stack, Notifications
Context

What was happening.

A school running on paper registers, disconnected spreadsheets and after-the-fact reporting needed one system for student records, attendance, finance and communication.

The problem

What needed to change.

  • Student, attendance, finance and communication data lived in separate tools with no single source of truth.
  • Administrative and teaching staff spent hours on repetitive data-entry and follow-up tasks.
  • Software releases were manual and error-prone, and infrastructure costs were not controlled.
  • Parents and staff had no reliable channel for notices, payments and urgent updates.
The approach

How it was done.

Architecture

A modular full-stack system — student records, attendance, finance and communication as connected modules over shared data. RESTful APIs with PostgreSQL/MySQL schemas designed around daily school operations.

Modular application over shared data — RESTful APIs, one source of truth
Notifications & messaging

Real-time push, in-app alerts and multi-channel messaging across mobile and web, with event triggers, delivery confirmation and channel fallback logic. A real-time chat subsystem handled presence and read receipts at institutional scale.

Event trigger → channel fan-out → confirmation → fallback
Authentication

Password-based login and on-device biometric verification secured access to sensitive institutional data, with session and account-lifecycle management.

Password + biometric, gated behind session and account lifecycle
Infrastructure & delivery

Azure cloud managed end-to-end. Containerised services on Docker and Kubernetes. Bash automation and CI/CD pipelines replaced manual releases. TrueNAS storage architecture held 10TB+ of institutional data with redundancy.

Azure · Docker · Kubernetes · TrueNAS, releases through pipelines
Operations

Proactive monitoring, scheduled maintenance and disciplined incident response with root-cause analysis kept the system at 99.9% uptime through a school year.

Measured results — monitored and maintained through a school year
Measured results

The numbers that came out.

99.9%
Uptime

Through proactive monitoring and disciplined incident response.

20%
Cloud cost reduction

Azure resources re-allocated and optimised end-to-end.

45%
Deployment error reduction

Manual releases replaced by Bash scripts and CI/CD pipelines.

15+ hrs/week
Automation savings

Reclaimed through scripted and pipelined operations.

50%
Internet downtime reduction

Network and failover improvements across the institution.

90% fewer
ISP support tickets

Root-cause fixes stopped recurring external-support calls.

Outcomes

Where it landed.

  • One system now holds student, attendance, finance and communication data for the institution.
  • Teachers and administrators work from a live, connected record instead of reconciling spreadsheets.
  • Notifications reach parents and staff through channels that confirm delivery.
  • Releases deploy through pipelines instead of manual, error-prone steps.
Stack & tools
C#PythonTypeScriptReact / Next.jsPostgreSQLMySQLAzureDockerKubernetesBashTrueNASLinux
Start a conversation

Your situation probably looks different — but the method doesn't.

Understand the work, decide the approach, deliver and measure. A free conversation establishes whether it applies to your problem.

or email joseph.gitau.c@gmail.com