Scoped connectors
Where a tool offers a documented API — a biometric device, payment gateway, LMS, accounting package or government portal — we assess whether and how it can connect, and scope the bridge before anything is built.
Integration, data & deployment services
Your existing tools don’t have to be dead ends.
Beyond the School OS, we scope connections to the systems you already run, unify their data into one dashboard, and deploy on our managed cloud or a dedicated Enterprise environment.
Biometric
Payments
Accounts
LMS
Messaging
Spreadsheets
ETL / ELT engineClean · map · reconcile
One dashboard
Collections
Attendance
Illustrative · each source scoped separately
Systems integration
Connect the fragmented tools you already have
Agreed direction and frequency
Each integration states which system owns which record, which way data moves, how often, and how errors are validated and retried — agreed in writing rather than assumed.
Built as workflows
Integrations are designed around your operating logic — for example, an admission confirmed in one system starting fee setup in another — where both systems allow it.
Development APIs for your own apps
Institutions that want their own portal, frontend or mobile apps can scope access to SquareCampus development APIs. Access follows the same role-based permissions and audit trail, and is granted after a compliance review.
In plain words: if your fingerprint machines, fee gateway or accounts software offer an API, we can scope a bridge between them. Each one is assessed and quoted on its own.
Integration status
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.
- Sign-inBy plan
- SquareCampus-managed credentials in every plan; Microsoft Entra ID single sign-on from Pro, subject to technical onboarding.
- Payment gateway, SMS and WhatsAppScoped service
- Payments run through your institution's own gateway account, and SquareCampus never handles the money. SMS and WhatsApp come with a monthly allowance; usage beyond it is prepaid.
- Accounting software, biometric devices, LMS and government portalsScoped service
- Assessed tool by tool. There is no pre-built connector; each one is scoped, quoted and confirmed in writing.
- Development APIs for the institution's own appsScoped service
- Scoped per institution and granted after a compliance review, inside the same role-based permissions and audit trail.
Before any integration is built
- The other system must offer a documented API or a data export the institution is licensed to use.
- Vendor access, vendor-side charges and the vendor's own limits remain the institution's.
- Sync direction, frequency, error handling and ownership of each record are agreed per integration.
Data engineering
ETL/ELT pipelines and one dashboard that answers to leadership
ETL / ELT pipelines
We extract from your fragmented sources — legacy ERPs, spreadsheets, standalone apps — transform them into one consistent model, and keep them flowing on schedule.
One custom dashboard
Leadership gets a single dashboard built around your institution's questions: collections, attendance, academics, operations — not a generic BI template.
Your servers or our cloud
Pipelines and the dashboard run on our Microsoft Azure setup in India or on infrastructure you already own, as agreed in the scope.
In plain words: the numbers from the tools in scope, in one screen your principal can read with morning tea.
Deployment options
SquareCampus runs where your governance says it should
Default
Managed cloud
SquareCampus on our Microsoft Azure infrastructure in India, operated and maintained by us. Every plan starts here.
Scoped service
Enterprise private deployment
A dedicated SquareCampus environment on AWS, in a private cloud or on premises, for institutions with strict segregation requirements. Enterprise only; scope, responsibilities and charges are agreed in writing.
Not offered today
Your own cloud account (BYOC)
Running SquareCampus inside the institution's own cloud account is not offered today. If your governance requires it, raise it during scoping.
In plain words: our cloud by default, or a dedicated Enterprise environment on AWS, a private cloud or your own premises.
Same role-based access and audit design in every modelHosted on Microsoft Azure in India by default
Start with an integration audit
Bring your current tool list. We’ll map what connects.
In one session we identify which systems can integrate, what the pipeline looks like, and which deployment model fits your institution’s governance.