Integrations

Plays well with the rest of your stack.

Bring your existing payment gateway, biometric device, GPS provider, SMS gateway, AI key. We adapt to you, not the other way round.

Adapter patternPer-school configSwap vendor in minutesNoOp adapter for off
Categories

Eight integration categories. One config screen per school.

Specific vendor adapters listed below are representative. Don't see your vendor? Most adapters take ~2 days to build given API docs.

Payment gatewaysLive

Online fee collection with receipts. Razorpay/PayU/CCAvenue widely deployed; HDFC SmartHub for high-volume schools.

RazorpayPayUCCAvenueHDFC SmartHubPaytmPhonePe
Biometric attendanceLive

Hardware-driven attendance — students and staff. Webhook + push patterns supported.

esslRealtimeZKTecoMatrix
RFIDLive

RFID-based gate entry, library circulation, bus boarding. Multi-vendor reader support.

MatrixSupremaHID Global
GPS vehicle trackingLive

Live bus location for the parent app + transporter ops. Multiple device protocols handled by the gateway service.

TeltonikaJimi (Concox)QueclinkAIS-140 compliant devices
Communication channelsLive

One engine fans out to multiple channels with consent gates and quiet hours.

Gupshup (WhatsApp)TwilioMSG91SendGridAmazon SESFCM (push)APNs
SSO / identityLive

Single sign-on for staff. Per-school configuration.

Google WorkspaceMicrosoft Entra (Azure AD)OIDC any-provider
AI providersLive

BYOK — pick your AI provider per school, per feature. NoOp adapter to turn AI off entirely.

OpenAIAnthropicGemini (Google AI Studio)NoOp (off)
Document OCR (preview)

Beyond AI vision: dedicated OCR backends for high-volume bulk admission processing. Coming in v1.5.

Tesseract (self-hosted)Azure Form RecognizerAWS Textract
How it works

Adapter pattern — swap vendors without rewriting code.

Every integration sits behind a school-level config row + an adapter interface. Switch providers in the admin UI; the code paths upstream never know the difference.

Per-school config

One row per (school, providerKind) — keys, endpoints, optional behaviour flags.

Interface, not implementation

Code talks to IPaymentGateway / IBiometricReader / ISmsProvider; never the vendor SDK directly.

NoOp by default

Every adapter ships with a NoOp impl so the system is functional out-of-the-box.

Don't see your vendor?

If you've got API docs, we've got an adapter coming. Tell us which integration you need.

Request an adapter