Our institutional site engine

Why we built it

School websites are a regulated surface, not a brochure. A CBSE school has to publish a mandatory disclosure page, host affiliation and safety certificates, declare a fee structure, and name a grievance and safety contact. Most school sites treat these as an afterthought bolted onto a template, locked inside JPEG images that no screen reader can read and no search engine can index. We kept meeting the same problem, so we built one engine to solve it once.

Our institutional site engine is the in house tool the studio runs on. It takes a single configuration for a school and produces a complete, compliance grade site from it. The disclosure, privacy, accessibility, and governance scaffolding is part of the template, not a page someone remembers to add later. The engine is internal infrastructure; we do not sell it. We sell the sites it produces and the engineering that stands behind them.

How it works

The operator answers a guided sequence of stages for one school: identity and domains, brand colours and type, the factual record (address, board affiliation number, contact, location), the compliance posture, the pages and portals to enable, locale, and the search metadata. Each stage validates before the next opens, so a half configured school cannot reach the output step.

The product of that sequence is one tenant configuration. From it the engine assembles the site: the public pages, the environment file, the seed accounts with passwords hashed before they are ever written, a deployment checklist, and a signed manifest with a checksum for every file. Nothing is hand assembled per school, so two schools built a week apart get the same compliance floor and the same build discipline.

Multi tenant delivery

The engine is built for more than one school. Every school is a tenant with its own namespace, its own domains, its own brand tokens, and its own enabled feature set, all expressed as configuration rather than as a forked codebase. We have run it for more than one institution from the same engine. Adding a school is a configuration exercise, not a rebuild, which is what keeps a small team able to ship a regulated site without cutting the regulated parts.

The compliance and legal floor

This is the part that matters and the part most templates skip.

Public disclosure as structure. The mandatory disclosure page is a first class part of the template. Affiliation certificates, building safety, fire safety, the no objection certificate, water and sanitation, the school management committee, and the parent teacher association are handled as documents to be served and linked, not as flat images pasted into a page. Fee schedules and committee lists become readable, indexable content rather than a photograph of a notice board.

DPDP ready data posture. For Indian schools the engine sets a data protection posture by default: the Digital Personal Data Protection module on, a stated data retention horizon, a consent age that matches Indian law, and a strict cookie policy. Privacy policy, terms, and copyright pages ship with the site rather than waiting for a lawyer to be remembered. The engine also carries the switches for COPPA and GDPR when a school operates across other jurisdictions.

Accessibility as a default, not a retrofit. Because disclosure and fee content is rendered as real text and real documents, it is reachable by a screen reader and by a search crawler. That is the opposite of the common failure mode, where the information required by law exists only inside an image and is therefore unreadable to the people the disclosure rule exists to protect.

Performance budgets enforced at build

A school site is often opened on a low end phone over a weak connection. The engine treats performance as a budget checked at build, not a hope. Each generated file carries a checksum, the manifest is signed, and the deployment step verifies that what ships is what was built. The output is a static, portable package, so the site that reaches a parent is fast by construction rather than fast on a good day.

Why it matters for an engagement

If you are evaluating us to build a regulated, multi tenant public surface where the legal floor cannot be optional, this engine is the proof that we treat compliance as architecture. The disclosure, the privacy posture, the accessibility, and the build discipline are the load bearing parts, and they are the parts we build first. The engine is ours; the engineering behind it is what we bring to your work.