SHO App.

The internal tool HACA staff use to run batches and track each student's attendance, work and wellbeing.

RoleDeveloper, then Tech Lead
Built forHaris & Co Academy, Kozhikode
SinceFeb 2026
StatusIn daily use
React 19TypeScriptExpressMongoDBPuppeteerRedis
sho-app.vercel.app
SHO App staff dashboard on laptop and phone

Every role at HACA opens the same app and sees only what it needs, scoped to its own schools and batches.

  • SHOs and SSHOs: daily student follow-up
  • Mentors: attendance, assignments and class logs
  • Academic leads and heads: curriculum, class planner and quality
  • Leadership and Business Heads: dashboards for admissions, payments and targets
  • Admins: users, roles and system health

Everything staff need,
in one app.

Attendance

Attendance per batch and class, with class logs.

Assignments and exams

Assignment review and module exams, linked to the LMS.

Verification and agreements

Student verification and agreement signing, with PDFs generated on the server.

Feedback and reviews

Complaints, feedback, monthly NPS and Google Reviews tracking through the Business Profile API.

Class planner

Class planner and curriculum templates for each batch.

Business Head dashboard

Admissions, payment status and sales target vs. collection for each school.

454commits on the SHO App
19user roles, each scoped to its schools or batches
517API endpoints shared with the LMS
16scheduled background jobs

Counted from the code and git history.

What took the most thought.

01

Access for 19 roles

Each role sees only its own schools or batches, with audit logs and user activity logs on the server.

02

Agreements as PDFs

Verified students sign their agreement in the app. The PDF is rendered on the server with Puppeteer, so it looks the same on every device.

03

Business Head dashboard

One view that combines admissions, payment status and sales targets for each school, reading Batch Ascent data from the same database.

04

Keeping it running

Automated reports, backups and a System Health page, with rate limiting backed by Redis.

Frontend
React 19, Vite 7, TypeScript, Tailwind CSS, Radix UI, React Router, Recharts, Framer Motion, GSAP, react-hook-form, zod
Backend
Node.js, Express, JWT and bcrypt, Helmet, express-rate-limit with Redis
Database
MongoDB Atlas with Mongoose
Other
Puppeteer for PDFs, Google Business Profile API, Resend, Web Push
Hosting
Vercel (frontend), Render (backend)

Three apps, one backend.

The SHO App, HACA LMS and Batch Ascent run on the same Express server and the same MongoDB database, so there is one backend to run instead of three. Together the three apps have about 700 daily active users.

Server
One Express server on Render serves /api (SHO App and LMS) and /ba/api (Batch Ascent)
Database
One MongoDB Atlas database shared by all three apps
Frontends
Each app is its own Vercel project
Integrations
Bunny Storage and Stream, Resend email, Web Push, Google Business Profile and Sheets APIs, Gemini, AWS S3 SDK, Puppeteer for PDFs

Built it, and now lead it.

I wrote the SHO App and its backend from the first commit in February 2026, and I own it as Tech Lead since August 2026.

Used at HACA.

The SHO App is an internal tool, so it opens to a staff login.

Open sho-app.vercel.app