Built for school leadership
One system for operations, ownership, and leadership visibility. Every exception gets an owner. Every change stays governed.
Admin & trust command centre
AEGIS governed intelligence
Illustrative product preview using synthetic data.
What institutions actually feel
Recurring school cycles break in predictable places. Each one has a hidden cost, a remedy, an accountable owner, and something a pilot can measure.
Fee reconciliation
Collection records, bank statements and spreadsheets each hold part of the picture.
Finance spends the first week of every cycle rebuilding a number that should already exist.
One governed fee cycle carrying reconciliation state, ownership and escalation on the same record.
Attendance drift
Patterns are noticed once they have already become a term-level problem.
Intervention happens after the point where it would have changed the outcome for the student.
Threshold-based detection, routed ownership and follow-up recorded against the student record.
Report-cycle delay
Compilation, correction, approval and publication collapse into the same fortnight.
Senior staff are pulled into chasing rather than reviewing, every single cycle.
Explicit stages, named owners, deadlines and exceptions that block publication.
Decision latency
Leaders spend their time assembling context before they can decide anything.
The institution reacts at the speed of its reporting, not the speed of its problems.
Governed operational context with an explicit next-action layer behind it.
Record versus decision
A system of record stores what happened. A decision layer shows what requires attention, why it matters, who owns it, and what happens next.
SquareCampus helps school leadership know what requires attention today, who owns it, and what happens next.
The command centre
Illustrative product preview using synthetic data.
Leadership reads live signals across campuses instead of waiting for stitched reports assembled after the fact.
Attendance by grade
Synthetic dataFee collection
Synthetic dataGovernance model
Fee rules, approval chains, academic calendars, and access boundaries are defined at the trust level — not re-invented per campus.
Principals and campus teams run their day inside clear guardrails, with local variation where the institution allows it.
Attendance drift, fee exposure, and stalled approvals escalate to the right desk while they are still small.
Approvals, overrides, and edits land on one auditable timeline — who, what, when, and in which campus context.
The cost of fragmentation
What fragmentation costs
What one governed system changes
Three connected journeys
One record from first inquiry to final transcript.
01
Inquiry and application captured with documents and status
02
Enrolment flows into sections, timetable, and attendance
03
Assessments, remarks, and results build one academic history
04
Promotion and records stay audit-ready year over year
Every rupee traceable from fee plan to audit.
01
Fee plans, concessions, and transport slabs set by policy
02
Invoices, reminders, and online payments run on schedule
03
Receipts and reconciliation happen on the same record
04
Approvals and refunds carry a complete audit trail
From signal to action while the problem is still small.
01
Live signals across attendance, fees, and academics
02
Exceptions flagged against policy, not discovered at term end
03
Reviews run on shared numbers, not competing exports
04
Actions and follow-ups tracked to closure
Sovereignty
Parent-facing flows run in ten Indian languages while the institution keeps consistent controls, reporting, and audit-ready records underneath.
Preferred language
Parent-facing updates flex by audience without fragmenting the institutional record.
Structured underneath
Circulars, dues, acknowledgements, and audit history stay attached to the same student and family context.
Managed cloud on AWS Mumbai by default, private single-tenant deployment for strict segregation, and BYOC — your own cloud account — coming soon.
The platform is designed to keep institutional data in an Indian cloud region, with the posture documented in writing during evaluation.
Role-scoped access and audit trails while you operate — and complete exports in standard formats if you ever decide to leave.
Deployment details
Managed cloud, private deployment, and the BYOC early-access list live on the services page.
Governed intelligence
Because AEGIS works from the same permissions, timelines and live records, it can surface exceptions, suggest next steps and answer leadership in plain language, with governance, tenant boundaries and auditability built in. As simple as asking. For a 300-student school or a 30,000-student group.
Role graph
Trustees, principals, finance, teachers, parents
Admissions
Applications, documents, offers, enrollment
Attendance
Classroom signal, staff follow-through, exceptions
AEGIS · Governed intelligence
Nothing is exported, copied, or re-keyed. AEGIS reads each record where it already lives, inside the same permissions and audit trail as the rest of the School OS.
Governance checks
LiveFinance ledger
Dues, receipts, concessions, approval history
Communication
App, WhatsApp, circulars, acknowledgements
Leadership view
Campus health, branch risk, cross-team visibility
Rollout & trust
Migration, role-based training, and go-live are sequenced around admissions, fee cycles, and exam windows — with named counterparts, not ticket queues.
Critical workflows run in parallel with your current systems until finance, academic, and admin teams trust the numbers.
Role-based access, encryption in transit and at rest, and audit trails are product design — and security documentation is shared in writing on request.
The outcome that matters: fee deadlines, inspections, and board reviews handled from one system, without the end-of-term scramble.
Founding institutional partners
There are exactly two Founding Institutional Partner positions, ever: one school or eligible school institution, and one university. Once both positions are allocated, the programme closes permanently. A Founding Institutional Partner is not an ordinary customer. The position involves a strategic capital commitment under a separately executed agreement, material participation in product validation, and structured roadmap input.
01
One school or eligible school institution and one university. When both are allocated, the programme closes permanently; it is not a launch programme or an early-customer discount.
02
A protected 40% discount on Enterprise commercial terms, set out in the executed Founding Partner agreement.
03
Structured, written consideration of the partner's operating requirements in roadmap planning, and material participation in product validation.
04
The parent and staff apps published under the institution's own branding and store listings, without the standard white-label charge.
05
A named counterpart maps the workflow, coordinates implementation, and validates the result alongside your team.
06
Parallel validation, scoped migration, and coexistence with current systems until the institution trusts the new operating model.
A strategic commitment, not a subscription
Founding partnership is for an institution with an executive sponsor, a measurable operating bottleneck, and the willingness to make a strategic capital commitment under a separately executed agreement and take part in product validation. This is not a free trial, a launch discount or an unlimited custom-development programme.
Scope, success measure and commercial terms are agreed in writing before work begins.
Next move
Bring your current stack. We will map it against the governed operating model and walk through rollout, controls, and institutional fit — without reducing the conversation to a card wall of features.
