DRAFT — for review by an Indian advocate before publication. Not legal advice.
Last updated: [[PUBLISH DATE]]
Version: 0.1-draft
This Service Level Agreement ("SLA") describes the availability target, maintenance windows and support response targets for the services provided by [[LEGAL ENTITY NAME]] ("NexaCloudStack"). It forms part of the Terms of Service. It does not create a service credit unless a credit is expressly stated in this document.
Status:
[[CONFIRM BEFORE PUBLISH]]— do not publish an uptime percentage until monitoring and a credit process exist.
1. Scope
This SLA applies to:
- Application Hosting (the managed platform, console and deployment pipeline);
- Cloud VPS and Volumes, where offered;
- Domains, only for our own ordering and DNS-management interfaces. Domain registration and registry availability are governed by the registrar and registry, not by this SLA.
2. Availability target
[[CONFIRM: e.g. 99.9% monthly availability for Application Hosting]]
Availability is measured per calendar month, excluding Scheduled Maintenance and events described in §5. If no target is stated, we provide the Services on a commercially reasonable efforts basis and no credit applies.
3. Support response targets
| Severity | Definition | Target first response |
|---|---|---|
| P1 | Platform-wide outage or data-loss risk | [[CONFIRM: e.g. 1 hour]] |
| P2 | Major feature unavailable, workaround limited | [[CONFIRM: e.g. 4 business hours]] |
| P3 | Degraded or single-tenant issue | [[CONFIRM: e.g. 1 business day]] |
| P4 | Question or minor request | [[CONFIRM: e.g. 2 business days]] |
Support hours: [[CONFIRM support hours and channels]]. Response targets are not resolution
guarantees. Self-managed Cloud VPS operating-system issues are outside supported scope.
4. Maintenance
- Scheduled Maintenance is announced in advance where practicable and excluded from availability calculations.
- Emergency Maintenance may be performed without prior notice to protect security, stability or legal compliance, and is excluded where the emergency justifies it.
- Where possible, maintenance is performed in announced low-traffic windows (IST).
5. Exclusions
The SLA does not apply to unavailability caused by:
- your applications, code, configuration, content or resource exhaustion within your plan;
- third-party networks, providers, registrars or services outside our control;
- force majeure events;
- your breach of the Terms or Acceptable Use Policy;
- suspension or termination permitted by the Terms;
- self-managed VPS operating-system, application or security administration;
- beta, demo, trial or free features marked as unsupported.
6. Service credits
[[CONFIRM: either state the credit formula, request process and caps, or state "No service credits are offered at launch."]]
If credits are offered:
- You must request a credit within
[[CONFIRM: e.g. 30 days]]of the incident. - The request must include the affected Service, dates, times and impact.
- Credits are applied to future invoices, are not cash-refundable, and are capped at
[[CONFIRM: e.g. 100% of the monthly fee for the affected Service]]. - Credits are the sole remedy for availability failures, to the extent permitted by law.
7. Reporting an incident
Email [[SUPPORT EMAIL]] with the subject "SLA incident", the affected Service, account
identifier and timestamps. Do not include secrets or full payment details.
8. Changes
We may update this SLA with notice as described in the Terms of Service. The version and "Last updated" date above apply.
9. Contact
- Support:
[[SUPPORT EMAIL]] - Grievance Officer:
[[GRIEVANCE OFFICER NAME]],[[GRIEVANCE EMAIL]],[[REGISTERED ADDRESS]]
Draft prepared 2026-11-22. Do not publish an uptime figure or credit promise until monitoring, ticketing and the credit process are in place.