Skip to content
Learning PlatformsD-07Live in production

Digital Campus

The operating system for an institution — admissions through graduation on one platform

Timeline
2026 — present
Availability
dc.zyntlow.com
Repositories
1
Role
Product specification, architecture, data model and full-stack implementation
Summary
A multi-tenant platform that runs a whole institution: admissions, student records, programmes and courses, timetables, attendance, a full classroom with live classes, examinations, results and transcripts, finance, HR and payroll. Every institution gets its own address, its own brand and a database that refuses to hand its rows to anyone else.
28
API modules
admissions and academics through payroll
54
Portal areas
one per thing a role actually does
240
Database tables
every one tenant-scoped
146k
Lines of TypeScript
measured across apps and shared packages
1,188
API routes
registered across the modules
46
Specification areas
written before the code, in docs/product-spec.md

What we built

Digital Campus, in use

Sample data, real screens. The product itself is atdc.zyntlow.com.

Choose the semester’s courses against the credit window. Prerequisites, clashes on the timetable and fees are checked before the registration goes to the advisor.

What it is

Digital Campus is what a university or college runs on, live at dc.zyntlow.com. An applicant applies on a public page. An admissions officer makes an offer. The applicant accepts and the same account becomes a student portal — registration, timetable, attendance, results, transcript. A lecturer teaches in a classroom with materials, assignments, quizzes, discussion and a live room. A finance officer bills and collects. A registrar signs the transcript at the end.

It is built for Ghana first, which shows up in the parts that usually get retrofitted: fees collected by Mobile Money, notices that reach a parent on WhatsApp or SMS rather than only email, certificates that print Ɛ, Ɔ and Ŋ correctly, and an app that still opens when the connection is poor.

The hard parts

Tenancy that does not depend on a careful developer. Each institution lives at its own address — northridge.campus.example — with its own brand, roles and data. The isolation is enforced in PostgreSQL by row-level security under a dedicated database role, not by a where clause someone might forget. A session cookie belongs to one institution’s address, so an account cannot sign in at another’s. The front door hands you to your own address with a single-use code that expires in two minutes.

Permissions an institution can actually explain. A dean sees one faculty, a head of department one department, a lecturer their own classrooms. That comes from one shared permission catalogue and role templates used by both the API and the portal, so a screen and the endpoint behind it can never disagree about who may do what. Everything consequential is written to an audit log.

A classroom that is a real classroom. Live classes run on LiveKit, and attendance comes from its webhook — who was actually in the room, not who clicked a link. Recordings are transcribed, and a summary, study notes and practice questions are drafted from each transcript for the host to share. External tools register over LTI 1.3; SCORM packages play inside a course.

Notices that arrive. Email through Resend, SMS through Hubtel, WhatsApp through Meta’s Cloud API with an approved template, plus Web Push to installed phones. Each institution chooses what it offers and each person chooses what they get. Delivery reports come back by webhook into one delivery log, so “they never got it” is a question with an answer.

Architecture

A pnpm workspace: a Fastify modular monolith, a React portal, and one shared package holding the permission catalogue, role templates and schemas both sides import.

  • API — src/core for database, request context, permissions and audit; src/modules/* for the 28 domains, from admissions and academics to procurement, HR and payroll.
  • Portal — src/ui is the design system, src/app the shell, and src/features/* the 54 areas a role can be in.
  • Data — PostgreSQL 16, 240 tables, migrations that create the restricted application role and the row-level policies along with the schema.
  • Files — local disk in development, S3-compatible storage in production (R2, B2 or MinIO all work).
  • Delivery — every integration degrades to something usable: payments to a sandbox, live classes to a development room, email and SMS to a delivery log, the assistant to offline answers. The platform runs end to end before a single API key is set.
Next product
Solara

A coding school for every age — live small-group classes, self-paced lessons and certificates