Service Policy

1. Service scope

Cloudexa provides shared developer infrastructure. Unless a separate written agreement says otherwise, the public service is provided without a guaranteed uptime percentage or response-time SLA.

2. Maintenance

Planned or emergency maintenance may temporarily affect repositories, deployments, hosting, domains, storage or account services. Cloudexa may perform emergency maintenance without advance notice when needed for security or stability.

3. Deployments and runtime

Deployment success depends on your source code, dependencies, build commands, network availability and runtime configuration. Cloudexa may stop workloads that exceed plan limits or pose a stability or security risk.

4. Persistent storage

Persistent project storage is intended to survive ordinary container restarts and redeployments. It should not be treated as the only backup of important data. Users are responsible for maintaining independent backups of critical application data.

5. Backups and recovery

Unless explicitly included in your plan, Cloudexa does not guarantee point-in-time backups or recovery of individual files. Infrastructure-level backups may exist for operational recovery but should not be relied on as a user backup system.

6. Domains and certificates

Custom-domain activation depends on DNS configuration and third-party certificate or DNS providers. Propagation and certificate issuance may take time and can be affected by systems outside Cloudexa's control.

7. Support

Support availability and response times may vary by plan. Critical security or platform incidents may be prioritized ahead of general questions.

8. Credits and remedies

Any service credits, extensions or incident-related refunds are governed by the Refund Policy or a separate written service agreement.