The questions institutions actually ask.

SquareCampus connects institutional operations on one governed system of record. Available workflows and the rollout scope are agreed with the institution; existing systems can remain authoritative during a bounded deployment.

Schools, educational trusts, multi-campus school groups and, as a governed operating layer over the systems they already run, higher-education institutions in India. It suits institutions that want operational governance, accountable ownership and leadership visibility, whether they run one campus or many. It is not designed for an institution that needs only basic attendance, fees and report cards at the lowest possible licence price.

We provide migration support, role-based training, and a dedicated success partner to configure your policies and timelines. Rollout is sequenced around your academic calendar, and the timeline is agreed during scoping based on your data complexity.

Book a guided demo. We map your workflows, share a rollout plan, and align on timelines and commercial terms. After discovery you receive a written proposal with the licence, any optional lines such as custom integrations, the training schedule and go-live milestones.

We support migration of student records, fee history, attendance data, academic records, staff information, and communication history. Our team works with you to map your existing data structure to SquareCampus and validates the migration with a parallel run before go-live. Migration is included in Pro and Enterprise. If your current system lacks data SquareCampus needs, or it is too fragmented to reconcile, we show you what cannot move before go-live.

Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. Available modules, workflows and deployment scope are confirmed before activation. A plan entitlement does not imply that an unreleased capability is available.

Where they offer a documented API, usually yes — as scoped work. SquareCampus does not publish a catalogue of pre-built connectors. Connecting another system is scoped work: we assess each tool during discovery, and what connects, in which direction, how often and at what cost is confirmed in writing before any build.

Development API access and supported interfaces are assessed during discovery. Authorisation, compliance review, commercial eligibility and delivery scope are agreed before development; a complete API surface for every workflow is not assumed.

Standard SquareCampus parent and staff mobile-app access is included in every plan at no additional charge. Supported app workflows, devices, languages and delivery readiness are confirmed before activation. White-labelled apps are a separately quoted enhancement, with founding-partner treatment governed by its own agreement.

Available workflow and form configuration is reviewed during scoping against the institution's policies. Supported options, extended branding and any bespoke engineering are distinguished in the proposal before activation.

Starter, Pro and Enterprise support multi-campus operations with campus-level administration and role-aware workflows. Advanced centralised institutional governance is a separate dimension; campus count alone does not require an upgrade. Plans differ in agreed messaging and AI allowances, analytics depth, workflow sophistication, identity and integration options, customisation and advanced governance. Standard implementation and support remain included in every plan; any custom SLA is separately agreed. Specific inclusions and consumption limits are documented in the proposal.

Updates ship continuously, covering new capabilities, performance improvements, and security patches. Releases are planned to avoid disrupting school hours, and admins are notified of significant updates through in-app announcements.

Tenant isolation, secure authentication, role-based authorisation, protection of institutional records, essential security logging and privacy safeguards are baseline requirements in every plan. Advanced identity governance and expanded audit controls are separately scoped; fundamental security is not a premium feature. Security documentation and implementation details are shared during the security review process.

The platform is designed with an India-first hosting posture, keeping institutional data in an Indian cloud region. Hosting details and backup design are documented and shared during security review.

SquareCampus is designed with privacy-by-default principles and to support institutions' obligations under the IT Act 2000, the DPDP Act and education-sector requirements. Retention, preservation and export are handled as set out on our Data Retention page, which separates what is available today from what is still being built.

The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone.

The institution owns its institutional data in every plan. We earn continued adoption through operational value, with supported data exports and documented offboarding rather than artificial lock-in. Export scope, available formats, access arrangements and assistance are confirmed for the deployment; retention and deletion follow the agreement, the DPA and applicable obligations. Export formats and timing are established before commitment. Your institution owns its data. What happens at the end of a contract is set by your agreement and the Data Processing Addendum: data is returned where export is agreed, or deleted or anonymised, subject to what the law requires to be kept. Export scope, formats, timing and any charges are agreed in the order form.

Secure authentication and role-based access are baseline requirements in every plan. SquareCampus-managed sign-in is included in the baseline plan scope; supported sign-in methods and deployment readiness are confirmed before activation. Additional verification for privileged roles is established during technical onboarding. Single sign-on is optional.

Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation. The institution chooses the sign-in mode: SquareCampus-managed credentials, subject to deployment readiness; Credentials alongside institutional single sign-on, where supported by the agreed configuration; Institution-enforced single sign-on, where the institution's policy requires it and the configuration supports it.

No. Standard Microsoft Entra ID sign-in is used to authenticate identity. Access to email, files, Teams, SharePoint or other Microsoft Graph data is not required for sign-in.

No. Single sign-on authenticates users. Automated provisioning, deprovisioning and joiner-mover-leaver lifecycle controls are identity governance requirements scoped under Enterprise rather than part of SSO.

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. The identity provider establishes who a person is. SquareCampus decides what that person may do: institution membership, campus scope, roles, workflow privileges, record access and operational permissions are governed inside SquareCampus and are never derived from an email address or domain alone.

Institutions on Starter, Pro or Enterprise may request optional single sign-on with Microsoft Entra ID as a separately quoted enhancement, subject to technical onboarding. Once configured, staff use their institutional accounts under the institution's own MFA, Conditional Access and user-assignment policies, while SquareCampus governs authorisation. Availability and commercial terms are confirmed before activation.

Initial launch outreach focuses on Kotdwara and surrounding areas. Enquiries are reviewed individually; this outreach focus is not a published geographic eligibility restriction. Modules, workflows, deployment coverage, institutional counterparts and documented success criteria are agreed before activation.

Where availability and eligibility are confirmed, an enhancement can be quoted separately. Included entitlements, additional consumption, professional services and any eligibility conditions are distinguished in the proposal. Contact sales to assess your requirement.

The licensing model is published on the pricing page; figures are issued in a written proposal after institutional discovery. One annual institutional licence, calculated on progressive student-volume bands and shaped by the plan (Starter, Pro or Enterprise), the institution's complexity and its deployment profile.

Every plan includes the complete generally available core operational platform. Essential school operations are not unlocked by upgrading from Starter to Pro or Enterprise. The licence covers the plan's platform capability, the standard SquareCampus parent and staff mobile apps, self-serve reporting, implementation and support, and a monthly usage allowance. Pro and Enterprise also include data migration. Migration on Starter, custom integrations and engineering, fixed-format documents made for one institution, private-cloud or on-premises deployment, a custom SLA and usage beyond the allowance are quoted as their own lines, not folded into the licence. There is no hidden module wall inside the licence, and every separately scoped line appears in the proposal before you sign.

Billable enrolment is the active enrolled students agreed in the order form. The per-student rate falls as enrolment moves up through the volume bands; growth is reconciled through an agreed true-up, and reductions are normally considered at renewal.

Usually not. SquareCampus is priced for institutions that want governance, workflow ownership, exception management, visibility and auditability. To one that needs only the cheapest attendance, fees and report-card product it will look expensive — and that reading is correct.

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. Under the executed agreement a Founding Partner receives defined roadmap influence, a protected 40% discount on Enterprise commercial terms, white-labelled mobile apps without the standard white-label charge, and any other privileges explicitly agreed.

No. The SquareCampus parent and staff mobile apps are included in every plan at no additional charge. A white-labelled Android and iOS build, published under your institution's own branding and store listings, carries a single charge that covers the entire agreed term, whether that is one year or many. Founding Institutional Partners receive the white-labelled build without the standard white-label charge.

You get a named success partner, live chat/email support during business hours, and proactive health checks. We help with new session rollovers, audits, policy tweaks, and any questions that arise. Implementation and support are included in every plan; only a custom SLA, such as 24×7 cover, is quoted.

SquareCampus publishes no measured outcomes. A pilot is designed to measure one agreed metric against a written baseline: for example, days between an attendance threshold breach and a recorded follow-up, or the time from collection close to a reconciled position. The value case is specific to the institution and is judged on that evidence, not on a vendor's percentage.

Eligible, approved launch institutions may join a 90-day complimentary pilot. The platform subscription, standard onboarding and reasonable operational support are included for the agreed pilot scope. Participation requires institutional approval and an agreed scope; submitting an enquiry does not activate a pilot. This is a selected launch programme, not an unrestricted global free trial. Messaging, AI, storage, integrations and external-service consumption have defined boundaries agreed before activation. Custom development, bespoke integrations and unrestricted engineering support are not included. Any separately chargeable work or consumption must be agreed in writing. Subscription pricing is communicated before pilot activation, with a commercial review before the 90-day pilot expires. At completion, the institution chooses to subscribe or discontinue. The complimentary launch pilot is separate from the standard paid subscription and from the Founding Institutional Partner programme. Launch-pilot participation does not confer founding status or its negotiated privileges.