Sectors · Education technology
The systems a school or university runs on.
Education is our deepest sector, and the one where we can show the most. We build the public websites an institution has to publish, the platforms that run its day-to-day work, and the engines underneath both. The same pattern holds across schools and universities: the parts the law requires and the parts the staff depend on are treated as essential from the first day, not added before an audit.
This page brings that work together. Every claim links to the full piece.
What we build for institutions
Institution-grade websites and portals. A public university or school site is a legal surface before it is a marketing one, bound by mandatory disclosure, accessibility, the Right to Information Act, and the Digital Personal Data Protection Act. We build them so the disclosure, the privacy, and the accessibility are the backbone of the site, not a links page added at the end. This is our institution-grade web design practice.
A school operating system. Arka is our K-12 school operating system, not yet launched: admissions, timetable, attendance, fees and accounts, student records, and parent messages on one login, so the same detail is never typed in twice. Its module status is published openly rather than promised.
The engines underneath. A timetabling solver and a multi-tenant platform sit beneath the products. We build the whole stack in-house, which is why the regulated parts and the day-to-day parts agree with each other instead of meeting at a seam.
The proof
The in-house timetable engine
Timetabling looks small until you look closely: qualification rules, daily and weekly caps, room capacity, curriculum rules across CBSE, ICSE, and state boards, fair workloads, and the hard rule that a teacher cannot be in two rooms at once. Off-the-shelf tools handle the easy half and fall apart on substitutes and rollbacks. We built the whole stack to show a small team can ship it: the solver, a multi-tenant database with access rules enforced inside it, a role-aware interface, and a mobile app. It is tested in production like conditions at a school that is not a paying client, and it is the engine under Arka.
Read it: the in-house timetable engine · the reasoning that preceded it: OR-Tools versus FET, a comparison
The institutional site engine
A CBSE school has to publish a mandatory disclosure page, host its affiliation and safety certificates, declare its fees, and name a grievance contact. Most school sites lock that content inside images no screen reader can read and no search engine can index. So we built one engine that takes a single configuration for a school and produces a complete, compliance-grade site: disclosure as real text, a data protection posture ready for the DPDP Act, privacy and terms shipped with the site, accessibility by default, and speed checked at build. It runs for many schools from the same engine; adding one is a configuration job, not a rebuild. We have run it for more than one institution.
Read it: our institutional site engine · the isolation pattern: multi-tenant Postgres with row level security
A CBSE school site design study
We took the public site of a CBSE school in Odisha as a real subject, reviewed it, and used it to work out how a school site should be shaped when the regulated parts are the backbone. The school is kept anonymous, and the work was not commissioned. The review found the usual problem: the fee schedule and committee lists existed only as photographs of notices, present in form and unreadable in fact. The study designs the opposite, where disclosure and fees are real, searchable text a parent can actually use.
Read it: a CBSE school site design study
The Vikram Dev University demonstration
No one asked us to build this. Vikram Dev University in Jeypore is a state public university serving four districts of southern Odisha. We built a full demonstration site for it on our own and presented it to the university. This was a demonstration, not a commissioned project, and nothing here suggests otherwise. It shows what a public university site looks like when the Right to Information, university disclosure norms, accessibility, and a DPDP aware privacy posture are designed in from the first page. It is static, works in three languages, and is built to stay readable on weak connections.
What we do not claim
We are honest about our test institutions: they let us validate the engines in production like conditions; they are not paying clients. The CBSE study is anonymous and was not commissioned. The Vikram Dev University site was shown as a demonstration, not invoiced against a contract. We would rather state the boundary than imply work that did not happen.
Run a school, college, or university?
Tell us what your site, portal, or platform owes the people who use it. We reply within one working day.