Habeo
Product
ComparePricingPartnersBlogPress
Sign inSign upBook a demo
Legal · Service Level Agreement

The uptime we promise — and the credits if we miss.

A real SLA with monthly Uptime targets by tier, a published incident-response ladder, and a service-credit table that lands in your invoice rather than your inbox.

Effective May 1, 2026Last updated May 17, 2026Version 1.3
On this page
  1. Scope
  2. Definitions
  3. Uptime commitments
  4. Service credits
  5. Incident response targets
  6. Exclusions
  7. Maintenance windows
  8. How to claim a credit
  9. Changes to this SLA

Section 01Scope

This Service Level Agreement (“SLA”) is part of the agreement between Habeo LLC (“Habeo”) and the customer institution identified in the relevant Order Form (“Customer”). It applies to paid subscriptions to the Habeo platform.

It does not apply to trial accounts, the live-demo workspace at /onboarding/try, beta features explicitly labeled “Beta” in the Documentation, or any free tier.

Capitalized terms not defined here have the meaning given in the Terms of Service.

Section 02Definitions

  • ServiceThe production environment of the Habeo platform — the web application, the public REST and webhook APIs, and the mobile scanner backend — accessed via the production hostnames listed in the Documentation.
  • UptimeTotal Minutes − Downtime Minutes, divided by Total Minutes, expressed as a percentage, measured per calendar month.
  • DowntimeAny consecutive period of at least three (3) minutesduring which more than 5% of authenticated production requests to the Service return an HTTP 5xx response or fail to complete due to a fault attributable to Habeo, as measured by Habeo’s external synthetic monitor.
  • Excluded DowntimeTime excluded from Downtime under section 6 (Exclusions) below.
  • Service CreditA monetary credit, calculated as a percentage of the monthly fee equivalent (annual fee ÷ 12) for the affected Service, applied against Customer’s next invoice.

Section 03Uptime commitments

Habeo will use commercially reasonable efforts to make the Service available at the following monthly Uptime targets:

TierMonthly Uptime targetMax Downtime / 30-day month
Small College99.5%≈ 3h 36m
College99.9%≈ 43m 12s
Research University99.95%≈ 21m 36s
System99.95%≈ 21m 36s

Real-time and historical Uptime, latency, and incident history are published at status.usehabeo.com. The dashboard is driven by the same external synthetic monitor used for SLA measurement.

Section 04Service credits

If Habeo fails to meet the monthly Uptime target for Customer’s tier, Customer is entitled to Service Credits as follows. Credits are calculated against the monthly fee equivalent for the affected Service.

Monthly UptimeService Credit
Below target, but ≥ 99.0%10%
≥ 95.0% and < 99.0%25%
< 95.0%50%
< 90.0%100%

Service Credits in any single calendar month are capped at 100% of the monthly fee equivalent for the affected Service. Service Credits are Customer’s sole and exclusive remedy for any failure by Habeo to meet a commitment under this SLA.

Section 05Incident response targets

Habeo’s on-call team triages issues using the severity ladder below. Response time is measured from acknowledgment in our ticketing system or Slack-Connect channel.

SeverityDefinitionInitial response — CollegeInitial response — Research U.Initial response — System
SEV-1Service down or unusable; data integrity at riskNext business day4 hours, 24/71 hour, 24/7
SEV-2Major feature impaired; viable workaround1 business day8 business hours4 business hours
SEV-3Minor issue or question; no business impact2 business days2 business days2 business days

For Small College subscribers, P1 initial response is 2 business days; SEV ladder otherwise mirrors College targets. Updates on active SEV-1 and SEV-2 incidents are posted to status.usehabeo.com at least every 60 minutes until resolution.

Section 06Exclusions

The following time is excluded from Downtime for purposes of measuring Uptime and calculating Service Credits:

  • Scheduled maintenance.Windows announced at least 72 hours in advance, occurring within the standard maintenance window of Sunday 03:00–06:00 U.S. Eastern Time. Habeo limits scheduled maintenance to no more than two windows per calendar month.
  • Emergency maintenance. Maintenance required to address a material security risk; Habeo provides as much notice as practicable.
  • Customer-caused issues. Downtime caused by Customer actions (including misuse of the API), Customer-controlled configuration, or unsupported Customer integrations.
  • Force majeure.Events outside Habeo’s reasonable control, including denial-of-service attacks not capable of being mitigated by commercially reasonable means, internet backbone outages, and acts of governmental authority.
  • Third-party services. Failures of third-party services that Customer chooses to integrate with the Service and that are not Habeo subprocessors.
  • Beta features.Any portion of the Service expressly labeled “Beta” in the Documentation.

Section 07Maintenance windows

Habeo publishes scheduled maintenance on status.usehabeo.com and to a webhook feed at POST /webhooks/status. Customers may subscribe to email notifications via the status page.

For the Research University and System tiers, Habeo will avoid scheduling maintenance during Customer’s declared blackout periods (e.g., student registration, semester start, fiscal year-end) provided those periods are declared at least 30 days in advance.

Section 08How to claim a credit

To receive a Service Credit, Customer must submit a written claim to sla@usehabeo.com within 30 days after the end of the month in which the Uptime target was missed. The claim must include:

  • the calendar month being claimed,
  • a description of the impact observed (timestamps, affected workflows), and
  • the subscription and Order Form reference number.

Habeo will validate the claim against its synthetic-monitor data and, if confirmed, apply the credit to Customer’s next invoice. If Customer has pre-paid for the full Subscription Term, Habeo will issue a credit memo redeemable at renewal or, at Customer’s option, refund the credit by ACH or check within 60 days of confirmation.

i
Good standing. Service Credits are only payable to Customers whose account is in good standing (no overdue invoices, no material uncured breach of the Agreement) at the time the claim is submitted.

Section 09Changes to this SLA

Habeo may update this SLA from time to time. Material changes that reduce the commitments above apply only to renewals beginning on or after the effective date of the change. Material improvements take effect on the date posted and apply automatically to existing customers.

Questions about this policy?

For legal questions write to legal@usehabeo.com. Privacy requests, data-subject access, and FERPA-related inquiries go to privacy@usehabeo.com and are routed to our Data Protection Officer.

Contact legal
More legal documents
Customers & visitorsPrivacy PolicyMaster agreementTerms of ServiceGDPR · FERPAData Processing AddendumUpdated listSubprocessorsUptime & creditsService Level Agreement
Habeo

The institutional system of record for everything a university holds.

HECVAT 2024 · Published

Product

  • Copilot
  • CMDB
  • Discovery
  • Lifecycle
  • Why Habeo
  • Replace ServiceNow

Compare

  • All comparisons
  • Habeo vs ServiceNow
  • Habeo vs Asset Panda
  • Habeo vs EZOfficeInventory
  • Habeo vs Snipe-IT
  • Habeo vs Lansweeper
  • Habeo vs Freshservice

Developers

  • Developer hub
  • API overview
  • API reference
  • OpenAPI 3.1 spec
  • Webhooks
  • Quick start

Resources

  • Pricing
  • Blog
  • Technology partners
  • HECVAT response
  • Trust center
  • Book a demo

Company

  • About
  • Press
  • Contact
  • Privacy
  • Terms
  • DPA
  • Subprocessors
  • SLA
© 2026 Habeo LLC · usehabeo.com
Habeo. We hold.