Service Level Agreement

Enterprise Reliability & Support

Service Level Agreement (SLA)

Defining cloud infrastructure uptime commitments, incident response timelines, automated backup standards, and technical support benchmarks for Shiksha Portals.

Product: Shiksha Portals (shikshaportals.com) Service Provider: Shilvora Software Private Limited Effective Date: November 16, 2026
Uptime Commitment 99.5% Monthly Cloud Availability
Critical (P1) Response Within 2 Hours (24×7 Monitoring)
Database Backups Automated Daily Encrypted
Standard Support Mon – Sat, 10:00 AM – 6:30 PM

01 Purpose & Covered Services

This Service Level Agreement ("SLA") forms an integral part of the Master Terms and Conditions between Shilvora Software Private Limited ("Company", "we", "us", or "our") and subscribing educational institutions ("Schools" or "Clients") utilizing Shiksha Portals (https://shikshaportals.com).

This SLA establishes measurable performance, availability, and technical support standards across our production ecosystem:

  • Cloud School Management ERP: Core web application, multi-tenant database clusters, and administrative portals.
  • Hosted School Websites: Institutional websites and admission inquiry portals deployed on our managed cloud hosting.
  • Mobile App Backend APIs: Cloud APIs powering the Student/Parent App, Staff/Teacher App, and Transport Driver App.

02 Cloud Availability & 99.5% Uptime Guarantee

Shilvora Software Private Limited commits to maintaining a Monthly Uptime Percentage of at least 99.5% for the production Shiksha Portals Cloud ERP and hosted school websites during each calendar month.

Uptime Calculation Formula:
Monthly Uptime % = [(Total Minutes in Month − Unplanned Downtime Minutes) ÷ Total Minutes in Month] × 100
("Unplanned Downtime" excludes Scheduled Maintenance windows and force majeure / third-party network failures defined in Section 8.)

03 Incident Severity Matrix & Response Timelines

Technical support tickets raised by authorized School Administrators are classified into four severity tiers with guaranteed initial response and resolution targets:

Priority Incident Definition Initial Response Target Resolution / Workaround
P1 — Critical Complete production outage; ERP login portal, fee collection gateway, or hosted school website completely inaccessible for all users. Within 2 Hours Within 6–8 Hours
P2 — High Major module severely degraded (e.g., exam report card generation error, live GPS API sync failure in Driver App, or bulk SMS queue stalled). Within 4 Business Hours Within 24 Business Hours
P3 — Medium Non-critical functional bug or UI anomaly affecting a single user role with an available operational workaround. Within 8 Business Hours Within 3 Business Days
P4 — Low General how-to queries, staff onboarding assistance, report format adjustments, or minor feature enhancement requests. Within 24 Business Hours Within 5 Business Days

04 Mobile Applications & GPS Telemetry SLA

  • API Gateway Availability: REST/JSON APIs serving the Student/Parent App, Staff App, and Transport Driver App are covered under our 99.5% cloud uptime commitment.
  • Live Bus Tracking Telemetry: Under normal cellular 4G/5G connectivity and active device GPS permissions, driver location coordinates sync to parent dashboards at intervals of 5 to 15 seconds during active school trips.
  • OS & Store Compatibility Updates: Shilvora Software Private Limited releases periodic compatibility updates to ensure active apps remain compliant with mandatory Android (Google Play) and iOS (App Store) SDK requirements.

05 Automated Backups & Disaster Recovery (RPO / RTO)

To safeguard institutional academic and financial records against data loss:

  • Automated Daily Backups: Encrypted snapshots of all production databases are generated automatically every 24 hours and replicated to geographically redundant cloud storage.
  • Recovery Point Objective (RPO): Maximum 24 hours of transactional data window in the event of a catastrophic infrastructure failure.
  • Recovery Time Objective (RTO): Target full production service restoration within 8 to 12 hours following a major disaster recovery declaration.

06 Scheduled & Emergency Maintenance Windows

  • Scheduled Maintenance: Routine server upgrades, security patches, and database optimizations are scheduled during low-traffic non-school hours (typically between 11:00 PM and 4:00 AM IST) with at least 48 hours advance notice via email or dashboard banner.
  • Emergency Security Patching: Critical zero-day vulnerability patches may be applied immediately without prior notice to protect institutional data security.

07 Custom Software Development & Post-Launch Warranty

For bespoke modules, custom school portals, and specialized third-party integrations developed under a signed Statement of Work (SoW):

  • Bug-Fix Warranty Period: All custom-developed code includes a 30-day post-deployment warranty from the date of User Acceptance Testing (UAT) sign-off, during which any defect deviating from the approved SoW specifications is resolved at zero additional cost.
  • Post-Warranty Enhancements: New feature requests, UI redesigns, or third-party API changes occurring after the 30-day warranty window are covered under an Annual Maintenance Contract (AMC) or billed per Change Request.

08 SLA Exclusions

Events Excluded from Uptime & Resolution Calculations:
  • Outages caused by the School’s local internet connectivity, internal school Wi-Fi/LAN failures, or corrupted local hardware (biometric/RFID scanners);
  • Third-party service disruptions beyond our control, including telecom SMS/WhatsApp gateway delays, TRAI DLT template rejections, RBI/bank payment gateway downtime, or Google Maps API outages;
  • GPS tracking gaps caused by disabled location permissions, battery saver restrictions, or mobile data loss on a driver’s smartphone;
  • Account suspension resulting from overdue subscription invoices or violation of our Acceptable Use Policy;
  • Force majeure events including natural disasters, government internet shutdowns, or upstream cloud data center fiber cuts.

09 Service Credits & Technical Support Desk

Service Credit Remedy: If monthly cloud uptime falls below 99.5% due to causes within Shilvora Software Private Limited’s direct control, the affected School may request a service credit within 15 days of month-end equal to 5% of the pro-rated monthly SaaS fee (capped at 15% of one month's fee), credited toward the School's next renewal invoice. Service credits represent the School’s sole and exclusive remedy for SLA shortfalls.

Shilvora Software Private Limited — Enterprise Support & NOC Desk
Product & Domain Shiksha Portals (https://shikshaportals.com)
Support & Escalation Emails info@shikshaportals.com / info@shilvora.in
Support Helpline +91 87450 64361 / +91 96679 09780
Support Hours Monday – Saturday, 10:00 AM – 6:30 PM IST (24×7 P1 Monitoring)
Corporate Office Address Tower-O-1077, 10th Floor, Gaur City Centre, Sector-4, Gautam Buddha Nagar, Uttar Pradesh – 201318, India