1. Uptime commitment
Construction OS targets 99.9% Monthly Uptime for the production Service on paid tiers, measured as:
Monthly Uptime % = (Total Minutes − Downtime Minutes) / Total Minutes × 100
2. Definitions
- Downtime means the customer’s production workspace returning consecutive 5xx errors on core API endpoints for more than five (5) consecutive minutes.
- Total Minutes means the total number of minutes in the calendar month.
3. Exclusions
Downtime does not include unavailability caused by:
- Scheduled maintenance announced at least 48 hours in advance (capped at 4 hours per month);
- Emergency security maintenance;
- Force majeure events (natural disasters, war, government action, large-scale internet outages, upstream cloud provider outages);
- Customer’s acts or omissions, including misconfiguration, exceeding rate limits, or violation of the Acceptable Use Policy;
- Beta or preview features.
4. Service credits
| Monthly Uptime | Service credit |
|---|---|
| < 99.9% and ≥ 99.0% | 10% of monthly fees for the affected workspace |
| < 99.0% and ≥ 95.0% | 25% of monthly fees for the affected workspace |
| < 95.0% | 50% of monthly fees for the affected workspace |
Credits are the customer’s sole and exclusive remedy for any failure to meet the SLA and are applied against future invoices. Credits do not accrue as cash refunds and expire on termination.
5. Support response targets
| Severity | Description | Target response |
|---|---|---|
| P1 — Critical | Production Service unavailable | 1 business hour |
| P2 — High | Major feature unusable, no workaround | 4 business hours |
| P3 — Normal | Non-blocking issue or question | 1 business day |
6. Claiming credits
To claim a credit, email oracle@inifye.tech within 30 days of the end of the affected month with: (a) the affected workspace, (b) the dates and times of the incident, and (c) any relevant logs. Construction OS will verify against internal telemetry and apply approved credits to the next invoice.
