§ 09 · Engineering
Three years of research, one product.
Before we wrote a line of product code, we spent three years studying how institutions actually work — their data, their downtime, their audit requirements. This page is the engineering behind that research: the data model, the architecture, and the papers that came first.
From the team
Engineering notesAsk Infocing
A chatbot that knows your institution. Ask it anything — last term's fee collection, today's attendance, next week's timetable — and get an answer in plain language.
From 47 steps to one
Fee collection used to mean queues, receipts, reconciliation and spreadsheets. We rebuilt the entire pipeline so a parent walks in, pays, and walks out — and the books balance themselves.
Payroll runs itself now
Three people, four days, one error-prone process. We automated the whole thing — attendance to payslip to bank file — so nobody touches a button and nobody misses a salary.
What 40,000 rows look like when you don't lie
Most systems show you a page of data and call it a report. We built operations that let you filter, aggregate, export and act on tens of thousands of records without the number at the bottom being wrong.
§ Current build
v188
build 2026.08.28 · release candidate
What changed recently.
- RBAC Granurality
- UI improvements
- Bugfixes
- Tutorial features
- Animated, live tutorial mapping
- Expanded and custom dashboards
- Reporting engine ease
- Reports everywheres
Appendix — try the build