Scope
This page does not create a binding SLA. Specific uptime commitments, support response times, maintenance notice periods, escalation routes and remedies should be confirmed in the applicable customer agreement or order terms.
Availability
Service availability can depend on hosting, application code, third-party providers, internet routing, customer networks, maintenance, support coverage and security events. Any agreed availability target should be specific and measurable.
Maintenance
Planned maintenance may be required for security, performance, reliability, bug fixing and feature improvement. Customer notification should follow the agreed support and maintenance process.
Support priority
Support priority should normally consider severity, user impact, affected services, security risk, data risk, workaround availability and contractual support level.
Incident handling
Incidents should be recorded, triaged, investigated, mitigated and reviewed. Serious incidents may require customer communication, technical evidence and follow-up action.
Support communication
Support communication should be clear, proportionate and based on the severity of the issue. A critical outage, security concern or data integrity problem should be handled differently from a general product question or minor content request.
Maintenance windows
Maintenance may be planned or urgent. Planned work should be communicated according to the relevant agreement where it affects contracted services. Emergency maintenance may be needed to address security, reliability or data protection risks.
No public SLA by default
This public page does not guarantee a specific uptime percentage, response time or compensation. Any binding service level must be stated in the customer’s approved contract or service schedule.