EARLY ACCESS

Campus Integration Gateway

Secure synchronization without exposing the campus database.

The planned gateway is an outbound-only Windows service that carries approved events and controlled commands between the campus and Indelo cloud services.

Network model

No public SQL endpoint. No inbound firewall rule.

Schools will not need a static public IP, router port forwarding, direct mobile SQL credentials, or a permanent VPN for normal cloud/mobile workflows.

EARLY ACCESS

Outbound-only connection

The gateway initiates encrypted communication over normal secured web transport.

EARLY ACCESS

Transactional outbox

Committed campus changes create durable integration events in the same local transaction.

EARLY ACCESS

Durable command inbox

Mobile-originated intentions are validated, recorded, retried safely, and applied by fixed Indelo handlers.

EARLY ACCESS

Idempotent retries

Repeating the same verified command must not duplicate a payment, receipt, attendance entry, or request.

EARLY ACCESS

Power-cut safety

Interrupted work resumes from durable state; local transactions either commit completely or roll back for safe retry.

EARLY ACCESS

Health and support

Authorized operations can see version, last synchronization, queue age, credential expiry, and redacted diagnostics.

Business-rule boundary

The gateway will not perform arbitrary table updates.

A mobile payment becomes a command such as PostVerifiedSchoolFeePayment. The campus applies it through the same fee ledger, cashbook, receipt, reversal, authorization, and audit rules used by local work.

Validate MessageRecord Inbox ReceiptApply Indelo HandlerCommit Audit & ResultPublish Acknowledgement

Gateway pilot

Assess the campus before provisioning cloud access.

CABS will review the supported Indelo version, SQL Server environment, Windows host, connectivity, campus identity, support ownership, and recovery practices.

Apply for Readiness Review
Chat on WhatsApp