Skip to main content
Ludwitt

Service Level Agreement

Last updated: March 20, 2026

1Uptime Guarantee

Ludwitt guarantees 99.9% monthly uptime for the platform, measured as the percentage of minutes in a calendar month during which the core services (authentication, learning modules, gradebook, and API endpoints) are available and responsive.

Monthly UptimeMax DowntimeStatus
≥ 99.9%~43 minutes/monthTarget
99.0% – 99.9%~7.3 hours/monthService credit: 10%
95.0% – 99.0%~36 hours/monthService credit: 25%
< 95.0%> 36 hours/monthService credit: 50%

2Scheduled Maintenance

Scheduled maintenance windows are excluded from uptime calculations. Ludwitt will provide at least 72 hours advance notice for planned maintenance. Maintenance is typically performed during off-peak hours (Saturday 2:00 AM – 6:00 AM EST).

3Incident Response

SeverityDefinitionResponse TimeResolution Target
Critical (P1)Platform completely unavailable15 minutes4 hours
High (P2)Major feature degraded (auth, grading)1 hour8 hours
Medium (P3)Non-critical feature impacted4 hours24 hours
Low (P4)Minor issue, workaround available1 business day5 business days

4Support Tiers

TierAvailabilityChannelsIncluded In
StandardMon–Fri 9AM–5PM ESTEmail, help centerAll plans
PriorityMon–Fri 8AM–8PM ESTEmail, chat, phoneProfessional+
Enterprise24/7Dedicated account manager, phone, SlackEnterprise

5Data Protection

  • Daily Firestore exports retained 30 days
  • Recovery targets: 4 hours to restore service (RTO) and at most 24 hours of data loss (RPO), per the disaster recovery runbook. Point-in-time recovery is not enabled.
  • Data encrypted at rest and in transit by the hosting providers (Google Cloud, Vercel)
  • Hosted on infrastructure providers that hold SOC 2 Type II reports (Google Cloud, Vercel)
  • FERPA and COPPA controls for student data: Controls in place; no independent audit yet

6Service Credits

If monthly uptime falls below 99.9%, affected institutional customers are eligible for service credits applied to the next billing cycle. Credits are calculated as a percentage of the monthly license fee according to the table in Section 1. Service credits must be requested within 30 days of the incident.

7Exclusions

This SLA does not apply to:

  • Scheduled maintenance windows (with 72-hour advance notice)
  • Force majeure events
  • Issues caused by customer's network, hardware, or software
  • Beta or preview features explicitly marked as non-production
  • Third-party service outages beyond Ludwitt's control (when communicated promptly)

8Status Page

Current platform status is published at /status, which checks each core service when the page loads. Incidents that Ludwitt logs are listed at /api/status/history; there is no longer-running uptime record beyond that log. Application errors are tracked with Sentry. Ludwitt emails institutional contacts about P1 and P2 incidents.

9Contact

For SLA-related inquiries or to request service credits:

This SLA is part of the Ludwitt Master Service Agreement and applies to all institutional license holders.