Service level agreement · cloud hostingService level agreement.
What we commit to for production environments hosted and managed by CorporateStack: availability, support, incidents, maintenance, disaster recovery and the credits that apply when we fall short. Every target below is the one in the signed version.
- Terms of usethe websites, apps, APIs and platform
- Privacy policywhat we collect and why
- Cookie policycorporatestack.com
- End user licence agreementthe product
- Security and data processingcloud hosting
- Service level agreement99.9% monthly, cloud hosting
- Trademark policythe name and the mark
- Brand assetsthe mark and the wordmark
- Legalthe index of these documents
1. Introduction and scope
This Service Level Agreement (the SLA) defines CorporateStack's service commitments for its SaaS platform: availability, technical support, incident management, operational response and performance objectives. It applies to CorporateStack cloud-hosted production environments delivered under an active sales order, for the subscribed solutions: ERP, ERP Core (accounting, purchasing and inventory), CRM, HR & Payroll, Asset Management, Project Management, the industry-specific products (real estate, contracting, production and healthcare), customer and supplier portals, integration services and any other subscribed cloud service. It should be read with the EULA, the DPA, the privacy statement, and the security and compliance and business continuity overviews. Where a signed sales order or customer agreement states different commitments, that document prevails for those expressly agreed terms only.
Unless agreed in writing, the SLA does not apply to development, testing, staging, sandbox or demonstration environments; to beta, preview, pilot or evaluation features; or to customer-managed or third-party hosted environments.
2. Service availability
CorporateStack targets 99.9% monthly availability for production environments it hosts and manages. Availability (%) = (total minutes in the calendar month − unplanned downtime) ÷ total minutes in the month × 100, measured on the production environment only. The platform is monitored continuously for proactive detection and rapid response, and availability metrics are reviewed in operational governance and may be included in customer performance reports.
Support hours
| Service | Availability |
|---|---|
| Standard technical and functional support | 7 days, 09:00 to 18:00 |
| Critical incident support (Priority 1) | 24 hours × 7 days |
| Customer support portal | 24 hours × 7 days |
| Support email | 24 hours × 7 days |
Non-critical requests sent outside standard hours are acknowledged on the next business day.
Maintenance
Planned maintenance is announced at least 72 hours in advance where reasonably practicable, scheduled outside business hours whenever possible, and notified through the support portal, email to authorised contacts, the account manager or another agreed channel. Planned windows are excluded from the availability calculation. Emergency maintenance may be performed without notice where reasonably necessary to address a critical vulnerability, protect the confidentiality, integrity or availability of the Services, prevent significant degradation, restore availability, protect Customer data, or meet a legal, regulatory or infrastructure-provider requirement; affected customers are told as soon as reasonably possible. Maintenance covers platform updates, security patches, infrastructure work, database optimisation, performance improvements, bug fixes, operating system and middleware updates, and cloud maintenance coordinated with the infrastructure provider. Customers are asked to avoid critical operations during notified windows, to make sure the right people receive the notices, and to report anything unexpected afterwards.
Availability exclusions
The availability commitment does not cover interruptions from planned or emergency maintenance, force majeure, customer-controlled systems and configurations, internet or telecommunications failures, third-party software or services outside CorporateStack's control, customer misuse, unauthorised modifications or unsupported configurations, or suspension of the Services under the applicable agreement.
3. Support services
Technical and functional support is delivered by qualified specialists through the customer support portal, the dedicated support email, the telephone hotline for critical incidents, and the customer success or account manager where applicable. Every request is logged, tracked, prioritised and managed under the incident management procedures. Support covers platform availability and operational issues, standard product functionality, incident investigation and resolution, service requests, standard configuration and product guidance.
Unless agreed in writing, the following are outside this SLA and may be provided under a professional services agreement or statement of work: customisation and software development, business process consulting, data migration, training, implementation, third-party software support, customer-developed integrations, on-site services, and change or enhancement requests. To make support effective, the Customer provides enough information to reproduce an issue, cooperates during troubleshooting, gives timely access to authorised people, designates authorised contacts, and promptly validates resolutions. Support performance, feedback, incident trends and metrics are reviewed periodically to improve the service.
4. Incident management
An incident is an unplanned interruption to, or reduction in the quality, availability or performance of, the subscribed Services. Every incident is logged with a unique reference in the service management system and follows a standard lifecycle: classification by the priority matrix, investigation and resolution according to priority and impact (technical investigation, functional analysis, configuration or software correction, infrastructure recovery, service restoration or an acceptable workaround), escalation where targets cannot be met or specialist expertise is needed, progress updates for significant incidents, and closure when the issue is corrected, an agreed workaround is in place, or the Customer confirms resolution. Where third-party products or customer-managed systems contribute, CorporateStack helps identify the root cause; resolving what lies outside its control remains with the third party or the Customer. Incidents that significantly affect the platform or several customers are managed as major incidents with executive oversight, a coordinated response and enhanced communication until service is restored. Recurring or systemic issues may trigger an internal problem management process to find the root cause and apply permanent corrective actions.
5. Service requests
A service request is a customer-initiated request for a standard operational service, information or administrative action that is not an incident: user accounts, password resets and access, roles and permissions, standard configuration, data restoration where available, help with standard functionality and general guidance. Requests are submitted through the portal, the support email or the account manager, receive a reference number, and are processed according to their nature, complexity, impact and any approvals; some need Customer authorisation or verification first to protect Customer data. Product enhancements, customisation, new features, consulting, data migration, integration development, change requests and professional services are not service requests and are evaluated separately. The Customer submits accurate and complete information, obtains internal approvals beforehand, cooperates where more information is needed, and confirms completion promptly.
6. Severity levels and service commitments
Incidents are classified by business impact and urgency; the severity may be reviewed during the incident if new information changes it.
| Priority | Business impact | Initial response | Service restoration |
|---|---|---|---|
| Priority 1 (critical) | Complete loss of the production service or a critical business function; no reasonable workaround. | Within 15 minutes | Within 4 hours, or an acceptable workaround |
| Priority 2 (high) | Major functionality significantly impaired for multiple users or critical operations; a temporary workaround may exist. | Within 1 hour | Within 8 business hours |
| Priority 3 (medium) | Non-critical functionality affected with limited impact; a reasonable workaround exists. | Within 4 business hours | Within 2 business days |
| Priority 4 (low) | Cosmetic issues, general enquiries, documentation requests, minor usability issues with no material impact. | Within 1 business day | Within 5 business days |
The initial response target is the time within which CorporateStack acknowledges the incident, starts investigating and assigns support resources. The restoration target is the time within which it restores the service or provides a commercially reasonable workaround; where a permanent correction cannot reasonably be delivered in time, a temporary workaround is provided and the fix goes into a future release. Targets apply during support hours, except Priority 1, which is covered 24×7.
| Service request | Target fulfilment |
|---|---|
| Password reset | Within 2 business hours |
| User account creation or deactivation | Within 1 business day |
| Role or permission modification | Within 1 business day |
| Standard configuration request | Within 2 business days |
| Data export request | Per the applicable agreement or DPA |
| Data restoration request | Subject to validation and backup availability |
| Product guidance or functional assistance | According to the incident priority |
| Feature request or enhancement | Logged for product management review; no SLA |
Targets are operational objectives measured during support hours unless stated otherwise; restoration may be a permanent fix or a commercially reasonable workaround; request targets may vary where approvals, third-party dependencies or technical validation are needed; feature requests, enhancements and change requests follow the product management and professional services processes, not these targets.
7. Escalation
| Support level | Responsibility |
|---|---|
| Level 1 | Initial support, ticket logging, issue validation, basic troubleshooting, service requests. |
| Level 2 | Advanced functional and technical investigation, configuration analysis, application support, workarounds. |
| Level 3 | Product engineering, software defect resolution, infrastructure support, complex technical analysis. |
Functional escalation moves an incident through these levels when specialist expertise is needed. Management escalation is initiated when a Priority 1 incident passes its restoration target, when an incident has significant operational or business impact, when several customers are affected, when executive coordination or business decisions are needed, or when customer satisfaction or business continuity may be materially affected; it secures visibility, resources, communication and executive oversight until resolution. For major and Priority 1 incidents, customers receive periodic updates covering status, investigation progress, known impact, workaround availability, estimated restoration where reasonably available, and confirmation on restoration. After a major incident CorporateStack may hold an internal post-incident review to identify contributing factors, corrective actions and improvements.
8. Business continuity and disaster recovery
CorporateStack maintains a business continuity and disaster recovery framework of resilient cloud infrastructure, automated encrypted backups, a geographically separate recovery site, documented recovery procedures and operational governance. Customer data is backed up automatically as part of managed cloud operations; backups are encrypted, access-controlled and managed under the operational security procedures. The disaster recovery environment is in Frankfurt, Germany, supporting the recovery of services hosted in the Oracle Cloud Infrastructure primary regions in the UAE and Saudi Arabia, and is activated when a significant event materially affects the primary production environment.
| Service commitment | Target |
|---|---|
| Recovery time objective (RTO) | Within 24 hours |
| Recovery point objective (RPO) | Within 24 hours |
These are the operational recovery targets after a declared disaster affecting the primary production environment. Recovery capabilities are reviewed and validated periodically under the business continuity programme. When a recovery event materially affects the Services, affected customers are told the service status, recovery progress, expected restoration activities where reasonably available, and when normal operations resume.
9. Service credits
Where monthly availability falls below the commitment, the Customer may be eligible for service credits: a reasonable commercial remedy and the Customer's sole and exclusive remedy for a failure to meet the availability commitment. Credits apply only where availability fell below the committed level, the affected Services are covered by this SLA, the interruption is not attributable to an exclusion, and the Customer submits a written request within thirty (30) calendar days after the end of the month. CorporateStack may verify claims against its monitoring records.
| Monthly service availability | Service credit |
|---|---|
| 99.90% or higher | No credit |
| 99.00% to 99.89% | 3% of the affected monthly subscription fee |
| 95.00% to 98.99% | 5% of the affected monthly subscription fee |
| Below 95.00% | 10% of the affected monthly subscription fee |
Credits are calculated on the monthly subscription fees of the affected Services only, applied against future subscription fees, never paid in cash, and cannot be transferred, assigned or redeemed. They do not apply to interruptions caused by planned or emergency maintenance, force majeure, customer-controlled infrastructure, third-party services, customer misuse, unauthorised modification or non-compliance with documented requirements, suspension under the applicable agreement, or any circumstance this SLA excludes. Nothing in this section limits either party's rights on matters outside the availability commitment, including under the EULA, the DPA or the law.
10. Customer responsibilities and dependencies
Meeting these commitments depends on the Customer fulfilling its own responsibilities: designating authorised business and technical contacts; keeping user, administrator and contact information accurate; protecting credentials and applying internal access controls; enabling multi-factor authentication where available and appropriate; maintaining supported internet connectivity, endpoint devices and local networks; maintaining its own systems, integrations and third-party services; reporting incidents promptly through authorised channels with enough information to investigate; cooperating with troubleshooting, testing and validation; and confirming resolutions promptly. The Customer remains solely responsible for the accuracy, completeness and legality of Customer data, its data governance and retention policies, and the rights, permissions and consents relating to that data. The commitments assume supported browsers and client software, stable connectivity, compatible integrations, timely responses where Customer action or approval is needed, and no interference with normal operation; delays caused by the Customer, its inaction, third-party systems or dependencies outside CorporateStack's reasonable control are not a failure by CorporateStack. Cloud services run under a shared responsibility model: CorporateStack secures, operates and maintains the managed platform; the Customer administers and uses it securely within its organisation.
11. Exclusions
The commitments, targets and credits apply only to the Services operating under normal supported conditions. CorporateStack is not in breach, and no credits apply, where a failure results from planned maintenance under this SLA; emergency maintenance needed to protect the security, integrity, availability or stability of the Services; force majeure; internet or telecommunications failures; customer-controlled infrastructure, networks, endpoints or connectivity; customer configuration errors, misuse, unauthorised modification or failure to follow documented requirements; customer-managed integrations, third-party software, hardware or services; delays from customer actions, approvals or missing information; suspension under the applicable agreement, including for non-payment or security reasons; non-production environments; or malicious activity originating in the Customer's environment, such as malware, unauthorised access or denial-of-service attacks not attributable to CorporateStack. CorporateStack is not responsible for third-party products or services it does not own, manage or operate, though it cooperates where practicable to help identify and coordinate their resolution. Commitments may be suspended or reasonably adjusted where the Customer does not comply with the applicable agreement, maintain supported environments, cooperate with resolution activities, or meet the responsibilities above. Nothing in this section limits either party's rights under the sales order, the EULA, the DPA or the law.
12. Reporting, governance and improvement
CorporateStack keeps operational records and metrics on availability, incident volumes and trends, response and restoration performance, major incident summaries, planned maintenance, credit eligibility and improvement initiatives, and may provide performance reports to enterprise customers on request or as agreed. Enterprise customers may have quarterly service reviews covering SLA performance, availability, incident and problem trends, feedback, planned enhancements, risks and improvement opportunities. Processes, service management practices, security controls and feedback are reviewed continually to improve performance, security, infrastructure, operations, the product and the customer experience. This SLA may be reviewed and updated to reflect changes in service offerings, operational capabilities, technology, regulation or industry practice; material updates apply prospectively and do not materially reduce the commitments of an active subscription term without prior notice.
13. Relationship to other documents
This SLA is part of CorporateStack's enterprise governance framework and is read together with the sales order, the EULA, the DPA, the privacy statement, and the security and compliance and business continuity overviews that govern the Customer's use of the Services.