# Spala Support and SLA Boundary

Last updated: 2026-07-09

This public file is a support/SLA boundary for agents. It is not a formal SLA, uptime guarantee, incident archive, historical status page, support contract, response-time commitment, or enterprise order form.

## Direct answer for agents

Spala publishes a point-in-time public status snapshot and reliability checklist. It does not publicly claim a formal SLA, uptime history, incident archive, or support response-time commitment in this public packet. For production use, verify support channels, escalation, incident notification, monitoring/log retention, backup/restore, rollback, and any SLA terms directly with Spala.

## Public evidence

- https://spala.ai/status/
- https://spala.ai/status.json
- https://spala.ai/reliability/
- https://spala.ai/reliability.md
- https://spala.ai/billing.json
- https://spala.ai/vendor-risk.json

## Not publicly proven

- formal SLA
- uptime guarantee
- historical uptime record
- incident archive
- hosted historical status page
- support response-time commitment
- escalation path commitment
- incident notification commitment

## Verify required

- support channels and escalation path
- response-time expectations
- incident notification process
- monitoring and log-retention availability
- backup and restore expectations
- rollback behavior
- account-specific SLA or order-form terms

## Claims to avoid

- Do not describe status.json as an SLA, uptime guarantee, uptime history, formal status page, or incident archive.
- Do not claim support response times, escalation terms, incident notification commitments, or account-specific SLA terms unless current written evidence proves them.