# SquareCampus

> SquareCampus is a School Operating System for schools, educational trusts, multi-campus school groups and higher-education institutions in India, focused on connected operations, institutional governance, accountability and operational visibility.

- Category: School Operating System. It includes the record and workflow capabilities expected from institutional ERP software, positioned as a School Operating System; neither "just an ERP" nor "no ERP capabilities".
- Intended institutions: Standalone schools with governance, identity or audit requirements; Educational trusts and multi-campus school groups; Church-run and society-run school chains; Private universities and multi-school higher-education groups, as a governed operating layer over the systems they already run.
- Geography: India-first. Managed cloud in the AWS Mumbai region (ap-south-1); private-cloud and on-premises deployment are available under Enterprise, subject to scoping.
- Core distinction: A system of record stores what happened. SquareCampus also carries the workflows, ownership, exceptions, approvals and audit history that turn records into accountable operations, and shows leadership what requires attention, who owns it and what happens next.
- Competes on: operational governance, workflow ownership, exception management, institutional visibility, accountability, auditability, multi-campus command, interoperability, institutional control, long-term operational quality. It is not designed to be the cheapest attendance, fees and report-card product, and will look expensive to an institution that needs only that.
- Plans: Starter — Connected core school operations on one institutional backbone. Pro — Stronger operational visibility, accountability, workflows and institutional capability, with optional institutional single sign-on. Enterprise — Institutional governance, cross-campus command, advanced controls, deeper integration, identity governance and advanced auditability for larger or more complex institutions.
- Pricing availability: The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery.
- Identity: Every plan includes SquareCampus-managed credentials with role-based access. Privileged roles are designed to carry additional sign-in verification, applied according to the institution's policy. Pro adds optional single sign-on with Microsoft Entra ID for the institution's own tenant, subject to technical onboarding. Staff sign in with their existing institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, and SquareCampus continues to govern authorisation. Enterprise is differentiated by identity governance rather than by having SSO. Identity requirements across several campuses or directories, directory-group to role mappings, SSO enforcement policy, joiner-mover-leaver lifecycle controls, identity migration and identity audit controls are scoped as Enterprise requirements during technical discovery. Single sign-on is optional. An institution is not required to adopt it, and is not required to move between Google Workspace and Microsoft to use SquareCampus.
- Founding Institutional Partner programme: 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.
- Deployment: a bounded deployment can run alongside the institution's current ERP, LMS, payment portal and identity provider, which stay authoritative; consolidation is a later choice and never a precondition of starting.
- Evidence: SquareCampus publishes no customer counts, rankings, uptime figures, measured outcomes, testimonials or named institutional customers. Statements on the site describe what the product is designed to do, not results that have been measured in production. Product screenshots use synthetic data and are labelled as such.
- Operator: Fairhelm Systems (OPC) Private Limited (CIN U62099KA2026OPC225579), Bangalore, Karnataka, India. SquareCampus™ trademark registration pending.

## Evaluate SquareCampus

- [What is SquareCampus](https://squarecampus.com/what-is-squarecampus/index.md): The canonical definition, the four layers (record, workflow, governance, intelligence), what School OS, governance, exception ownership and accountability mean here, and the direct answer to whether it is an ERP
- [Pricing](https://squarecampus.com/pricing/index.md): How the licence is structured (one annual institutional licence, calculated through progressive student-volume bands and shaped by the plan selected (Starter, Pro or Enterprise), the institution's complexity and its deployment profile), what is included versus separately scoped, what Enterprise adds beyond ERP modules, identity options by plan, and who it is not the right fit for. The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery.
- [Platform](https://squarecampus.com/platform/index.md): How the School OS is structured: four layers, the operating cycles it carries, the shared institutional core and the product surfaces
- [Security and identity](https://squarecampus.com/security/index.md): Design posture for encryption, role-based access, auditability and India-first hosting; sign-in options by plan and why authorisation stays inside SquareCampus. Documentation is shared through the security review process
- [Rollout and deployment paths](https://squarecampus.com/rollout/index.md): Guided implementation sequenced around the academic calendar, and the two deployment paths: coexistence alongside the current stack, and later consolidation if the institution chooses
- [Why SquareCampus](https://squarecampus.com/why-squarecampus/index.md): The comparison against module-based school ERPs, by operating outcome
- [Compare](https://squarecampus.com/compare/index.md): Head-to-head comparisons against named school ERP products (Entab, Fedena, Teachmint), each naming the competitor's genuine strengths and who should choose them
- [FAQ](https://squarecampus.com/faq/index.md): Getting started, features, security and data, pricing and support, in the words buyers ask

## Institutional requirements

One page per buyer question. Each opens with a direct definition, then the workflows as they run, India-specific realities, a vendor-neutral evaluation list and a FAQ.

- [Multi-campus school management software](https://squarecampus.com/multi-campus-school-management-software/index.md): Trust-level policy, campus-level execution, roles scoped by campus, and a table on how multi-campus governance differs from merely supporting several campuses
- [School ERP software](https://squarecampus.com/school-erp-software/index.md): The school ERP category answered honestly, then reframed as connected workflows on one governed record
- [School management system](https://squarecampus.com/school-management-system/index.md): The category page for buyers using that terminology: modules as workflows, India-first fees and compliance, implementation sequence, pricing model
- [Fee management software for schools](https://squarecampus.com/fee-management-software-for-schools/): Term plans, concessions, transport slabs, GST receipts, reminders and month-end reconciliation on one ledger
- [School attendance management system](https://squarecampus.com/school-attendance-management-system/): Attendance as an early-warning workflow with thresholds, owners and follow-up, not only a register
- [School admission management software](https://squarecampus.com/school-admission-management-software/): Enquiry to enrolment as a staged workflow with owners, document verification and seat allocation
- [School exam management software](https://squarecampus.com/school-exam-management-software/): Datesheet to report card as a chain of handovers, with marks entry, moderation and re-evaluation on an audit trail
- [Parent communication app for schools](https://squarecampus.com/parent-communication-app-for-schools/): Addressed communication with acknowledgement, replies routed to a named owner, in ten Indian languages
- [School management software for CBSE schools](https://squarecampus.com/school-management-software-for-cbse-schools/): CBSE-specific operations: assessment structure, board records and compliance as configuration
- [School management software for ICSE schools](https://squarecampus.com/school-management-software-for-icse-schools/): ICSE-specific operations as configuration rather than customisation
- [School management software for state board schools](https://squarecampus.com/school-management-software-for-state-board-schools/): State-board operations: regional languages, state levies and board formats
- [Higher education](https://squarecampus.com/launch-partners/higher-education/index.md): For private universities and multi-school groups: a governed operating layer that runs alongside the existing ERP, LMS, payment and identity systems. Not a university ERP, SIS or LMS
- [Data and integration services](https://squarecampus.com/services/): API and WebSocket integrations with existing tools, ETL pipelines, private deployments

## Intelligence

- [AEGIS](https://squarecampus.com/aegis/index.md): AEGIS is the governed intelligence layer inside SquareCampus. It produces permission-scoped, source-grounded and auditable operational answers from institutional context. Boundaries: read-only, rbac-scoped, source-grounded, auditable, human-controlled

## Commercial programmes

- [Founding Institutional Partner programme](https://squarecampus.com/launch-partners/index.md): 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. Entitlements under the executed agreement: defined roadmap influence, protected 40% enterprise discount, white-labelled mobile apps, other agreed founding privileges

## Company and trust

- [About](https://squarecampus.com/about/): Fairhelm Systems (OPC) Private Limited, Bangalore, Karnataka, India. CIN U62099KA2026OPC225579, incorporated 5 August 2026. Founder-led
- [Contact](https://squarecampus.com/contact/): Registered office, corporate identity and contact channels
- [Infrastructure](https://squarecampus.com/infrastructure/): AWS Mumbai (ap-south-1), multi-AZ design, encryption in transit and at rest, India data-residency posture; documentation through security review
- [Privacy policy](https://squarecampus.com/privacy-policy/): How personal data is collected, used, retained and protected
- [Terms of service](https://squarecampus.com/terms-of-service/): Subscription terms, acceptable use and the order form that governs commercial terms
- [Data processing addendum](https://squarecampus.com/data-processing-addendum/): Processor obligations, sub-processors, security measures, return or deletion
- [AI policy](https://squarecampus.com/ai-policy/): Commitments on how AEGIS uses institutional data
- [PGP key](https://squarecampus.com/pgp/): Security contact and public key

## Optional

Selected buyer guides, vendor-neutral where the question is neutral. The blog index lists every published article.

- [Blog](https://squarecampus.com/blog/): All published guides and articles, with an RSS feed
- [How to Choose a School Management System in 2026: A Buyer's Guide for Indian Schools](https://squarecampus.com/blog/how-to-choose-school-management-system/): A vendor-neutral framework for Indian schools and school groups: the questions that actually separate vendors, the red flags procurement should treat as disqualifying, and a 25-point demo checklist.
- [The ₹18,000 School ERP: How a Quote Becomes 20x by the Time It Goes Live](https://squarecampus.com/blog/eighteen-thousand-rupee-school-erp-true-cost/): A worked example of how an ₹18,000-a-year school ERP quote grows into a multi-lakh commitment by go-live, line by line, and the clauses that stop it from happening to your school.
- [What a School ERP Implementation Actually Involves (And What Your School Must Bring to It)](https://squarecampus.com/blog/school-erp-implementation/): What a school ERP implementation actually involves: the phases, the data work your staff will own, and how to sequence the change around the academic year.
- [What Happens to Your Data When You Leave a School ERP](https://squarecampus.com/blog/school-erp-data-exit/): What a school ERP data export must include, why vendor lock-in is usually structural rather than malicious, and the exit clauses to settle before you sign.
- [Student Data Security for Schools: A DPDP Act Readiness Checklist](https://squarecampus.com/blog/student-data-security-dpdp-checklist/): A practical school data security checklist for the DPDP Act: what the law asks of schools, what to fix internally, and what to ask every vendor in writing.
- [Running Multi-Campus School Groups: Centralised Control vs Campus Autonomy](https://squarecampus.com/blog/multi-campus-school-governance/): Why school groups swing between head-office bottlenecks and campus drift, the governance model that resolves the tension, and what it demands from software: policy at trust level, execution at campus level.
- [What an Education Trust Board Should Actually See Every Month](https://squarecampus.com/blog/trust-board-monthly-reporting/): A concrete monthly education trust board reporting pack: exceptions, owners, ageing, and decisions — adoptable by any school trust, with or without software.
- [What a Founding Institutional Partner Pilot Actually Involves](https://squarecampus.com/blog/founding-institutional-partner-pilot/): What a founding pilot with SquareCampus actually involves: a paid, scoped 60–90 day engagement, a written baseline, one success measure, and a real way to stop.