OhAuthCat Service Level Agreement
Version: 1.0. Effective and last updated: 1 November 2026
This Service Level Agreement ("SLA") forms part of the OhAuthCat Customer Agreement in Terms of Service (the "Agreement") between Generic Technologies Private Limited ("OhAuthCat", "we") and the Customer ("you"). Capitalised terms not defined here have the meanings given in the Agreement. If this SLA conflicts with the Agreement, this SLA prevails on service levels and credits; an Order Form prevails over both.
1. Scope #
1.1 Plans covered. This SLA applies only to Production Environments on the Business and Enterprise Plans while the subscription is paid and in good standing. It does not apply to the Free or Pro Plans, to Sandboxes, or to Beta Features.
1.2 Commitment. For each covered Production Environment, we aim for 100% availability of the Covered Services in every calendar month. For every minute of Downtime, you are eligible for a Service Credit calculated under clause 4.
1.3 Covered Services. The SLA covers two services:
(a) Sign-in: the single sign-on broker endpoints that complete a sign-in (authorisation, SAML assertion consumer service and OIDC callback, and token and profile exchange), including those endpoints when served on a custom broker domain; and
(b) SCIM: the SCIM 2.0 endpoint that receives provisioning requests from identity providers, including when served on a custom SCIM domain.
1.4 Not covered. The Dashboard, the management API, the Portal, webhook delivery, log streaming, the MCP server, the compat/workos API outside its support window, the Hosted Test IdP, the Free Tools and the status page are not Covered Services. We describe our targets for them in the Documentation, but no credits apply.
2. Definitions #
2.1 "Probe" means a synthetic request sent by OhAuthCat's external monitoring system to a Covered Service through the public internet and Cloudflare, from at least 5 geographically separate vantage points outside our AWS account, at least every 30 seconds per vantage point. Sign-in Probes complete a full test sign-in against a monitoring connection; SCIM Probes perform an authenticated SCIM read and write against a monitoring directory.
2.2 "Failed Probe" means a Probe that receives no response within 10 seconds, receives an HTTP 5xx response, or receives a response that does not complete the sign-in or SCIM operation, for a reason within our control.
2.3 "Downtime Minute" means a one-minute interval, for a Covered Service, in which more than half of the vantage points record only Failed Probes. A Downtime Minute counts only if it is part of a run of at least 2 consecutive Downtime Minutes; isolated single minutes do not count.
2.4 "Downtime" means the total of Downtime Minutes in a calendar month for a Covered Service. If Sign-in and SCIM are both down in the same minute, that minute is counted once.
2.5 "Partial Downtime". Where the Probes show the Covered Service is available but you show, from your own logs and our sign-in timelines, that more than 5% of valid requests to that Covered Service in your Production Environment failed with a server error caused by us during a minute, that minute also counts as a Downtime Minute, subject to the same minimum duration. Our measurement records and logs prevail in case of disagreement, unless you show they are wrong.
2.6 "Minutes in the Month" means the number of minutes in the calendar month (for example 43,200 for a 30-day month and 44,640 for a 31-day month).
2.7 "Monthly Fee" means the Fees attributable to the affected Project for the month in which the Downtime occurred, excluding taxes and Add-ons other than those that support the Covered Services. For annual subscriptions, the Monthly Fee is one twelfth of the annual Fees for that Project.
2.8 "Multi-Region Go-Live" means the date on which we announce in writing, and on the status page, that the Covered Services for your Enterprise Production Environment are served from more than one region with automatic failover. At the date of this SLA, the Service runs in one region (AWS ap-south-1, three availability zones), and Multi-Region Go-Live has not occurred.
2.9 "Service Credit" means a credit against future Fees calculated under clause 4.
3. Measurement #
3.1 Source of truth. Downtime is measured by our external Probes. We publish availability for Sign-in and SCIM on the status page at https://status.ohauthcat.com. The status page is hosted outside Cloudflare and outside our AWS account so that it stays reachable during an outage.
3.2 Records. We keep Probe records for at least 90 days and will share the records for a claimed period on request.
3.3 Changes to monitoring. We may change how Probes are run if the change does not reduce their coverage or sensitivity.
4. Service Credits #
4.1 Formula. For each calendar month, the Service Credit for a Production Environment is:
Service Credit = (Downtime Minutes ÷ Minutes in the Month) × Monthly Fee × Multiplier
4.2 Multipliers.
| Plan | Before Multi-Region Go-Live | After Multi-Region Go-Live |
|---|---|---|
| Plan: Business | Before Multi-Region Go-Live: 1× | After Multi-Region Go-Live: 1× |
| Plan: Enterprise, Standard SLA tier | Before Multi-Region Go-Live: 1× | After Multi-Region Go-Live: 10× |
| Plan: Enterprise, Premium SLA tier | Before Multi-Region Go-Live: 1× | After Multi-Region Go-Live: 25× |
The Enterprise SLA tier is set in the Order Form. The higher multipliers apply only from Multi-Region Go-Live for that Enterprise customer, as stated in clause 2.8.
4.3 Cap. The total Service Credits for a calendar month cannot exceed 100% of the Monthly Fee for the affected Project.
4.4 Worked examples.
(a) Business, 30-day month. Monthly Fee US$499. Downtime 54 minutes. Credit = 54 ÷ 43,200 × 499 × 1 = US$0.62.
(b) Enterprise Standard after Multi-Region Go-Live, 30-day month. Monthly Fee US$3,000. Downtime 54 minutes. Credit = 54 ÷ 43,200 × 3,000 × 10 = US$37.50.
(c) Enterprise Premium after Multi-Region Go-Live, 31-day month. Monthly Fee US$5,000. Downtime 300 minutes. Credit = 300 ÷ 44,640 × 5,000 × 25 = US$840.05.
(d) Cap reached. Enterprise Premium, Monthly Fee US$3,000, 30-day month, Downtime 2,000 minutes. Uncapped credit = 2,000 ÷ 43,200 × 3,000 × 25 = US$3,472.22; the credit is capped at US$3,000.
4.5 Currency. Credits are calculated in the currency of your Fees. For customers billed through a Merchant of Record, credits are applied as a discount to future charges, or as the MoR's terms allow.
4.6 Application. Credits are applied to the next invoice or charge after the claim is approved. They have no cash value, cannot be transferred, and are not refunded if the Agreement ends, except that if the Agreement ends for our breach we will refund unused approved credits. If you are billed through a Merchant of Record, we apply an approved credit as a discount on your next renewal charge processed by that Merchant of Record. If no further charge is due, we may instead extend your paid term by a period of equal value. Credits are never paid out in cash through a Merchant of Record.
5. Claim process #
5.1 How to claim. To receive a Service Credit, an owner or admin of your Account must submit a claim to support@ohauthcat.com or through the Dashboard within 30 days after the end of the month in which the Downtime occurred. The claim must include:
(a) your Account and Project identifiers and the affected Production Environment;
(b) the dates and times (with time zone) of each Downtime period claimed; and
(c) for Partial Downtime under clause 2.5, request IDs or logs showing the failed requests.
5.2 Review. We will review the claim against our Probe records and logs and reply within 30 days. If we reject any part of the claim, we will explain why and share the relevant records.
5.3 Missed deadline. A claim not made within the period in clause 5.1 is waived.
5.4 Good standing. Credits are not available while undisputed Fees are overdue.
6. Exclusions #
Downtime does not include, and no Service Credit is due for, unavailability or failures caused by:
6.1 the Customer Organization's or your identity provider, SCIM client or directory, including their outages, misconfiguration, expired certificates or rate limits;
6.2 your applications, hosting, networks, DNS or internet connections, or those of Customer Organizations or Users;
6.3 misconfiguration by you, an Account Holder or a Customer Organization administrator, including expired or wrong certificates, wrong redirect URIs, policies or rules that refuse sign-ins, and revoked or rotated keys or tokens;
6.4 your use of the Kill Switch for an Environment;
6.5 suspension of your Account, Project or Environment under clause 8 of the Agreement;
6.6 Beta Features, Sandboxes, the Hosted Test IdP, and the compat/workos API outside its support window;
6.7 Force Majeure under clause 23 of the Agreement;
6.8 scheduled maintenance that we announce at least 72 hours in advance on the status page and by email to owner contacts, up to 4 hours per month; we aim to perform maintenance without Downtime;
6.9 emergency changes required by clause 3.7 of the Agreement (security), where the Service deliberately refuses a sign-in it cannot fully validate;
6.10 traffic exceeding the documented rate limits or Plan limits, or use in breach of clause 5 of the Agreement;
6.11 a refusal by the Service, as designed, of an invalid, expired, replayed or unsigned request; or
6.12 failures of Third-Party Services not under our control, including outages of our hosting and network providers, Amazon Web Services and Cloudflare.
7. Sole remedy #
7.1 Service Credits are your sole and exclusive remedy for any unavailability, Downtime or failure to meet this SLA.
7.2 Chronic failure. As a narrow exception, if Downtime for a Covered Service exceeds 0.5% of Minutes in the Month in each of three consecutive months, or in any four months of a 12-month period, you may terminate the affected subscription by notice within 30 days after the last such month, and we will refund any prepaid Fees for the remaining term.
7.3 Service Credits count toward the limitation of liability in clause 21 of the Agreement.
8. Changes #
We may update this SLA under clause 29 of the Agreement. No change will reduce the multipliers, the cap or the claim period for an Enterprise customer during the current Order Form term, or for a Business customer during the current billing period.