Operations and communication
How support, maintenance, and status communication are handled.
VexylCloud uses this page to define support expectations, maintenance communication, and the operational handling of the public website and buyer-facing evaluation process.
Support channel
Sales, rollout, and product enquiries are handled through the contact and book demo workflows, with direct follow-up from the VexylCloud team.
Maintenance windows
Routine maintenance is scheduled to minimize buyer impact. Where material maintenance is expected to affect customer-facing systems, notice is provided in advance whenever practical.
Incident communication
Operational incidents are prioritized by severity. Buyers or customers affected by a material issue receive direct communication with status, mitigation steps, and follow-up as appropriate.
Response framework
- P1 critical service-impacting issue: response target within 1 hour
- P2 major issue with meaningful business impact: response target within 4 hours
- P3 normal-priority issue: response target within 1 business day
- P4 minor issue or advisory request: response target within 2 business days
Current public-site posture
The public VexylCloud marketing site is served from a single production WordPress host with backups enabled, alongside a separate password-protected staging clone for safer content and theme iteration.
This page describes the public website and buyer-facing support posture. Production customer agreements may define additional support, escalation, or service-specific commitments.