This document is not yet effective. Everock’s operator details and final legal terms must be completed before it is used as an agreement or production notice.
Current beta status
Everock does not currently make a contractual uptime commitment through this page. The beta has no promised availability percentage, response time, recovery time, or service-credit schedule. This is a draft framework for a future written agreement.
A pricing tier, a green status indicator, or an observed service-health history is not an SLA. This document becomes contractual only when finalized, completed with the operator’s details, and expressly accepted in an applicable agreement.
What a future SLA would cover
A final SLA must name the Everock-hosted production services it covers, such as the collector, dashboard, or evidence API, together with the subscribed period and applicable plan. It must distinguish full unavailability from partial degradation.
Customer applications, independently operated endpoints, selected AI agents, and self-hosted installations are outside a hosted-service SLA unless expressly included. An alert about your own service does not establish downtime of Everock.
Measuring availability
The proposed monthly calculation is: eligible minutes minus confirmed downtime minutes, divided by eligible minutes, multiplied by 100. Concurrent outages of the same covered function must not be counted twice.
Before offering a guarantee, the agreement must specify the measurement source, time zone, partial-month rules, covered functions, and treatment of delayed ingestion, queues, dropped events, and replay availability. This draft deliberately supplies no invented percentage.
Maintenance and exclusions
A final agreement must define advance notice and any allowance for scheduled maintenance, emergency security work, and failures outside the operator’s reasonable control. Exclusions must be specific rather than an unlimited ability to disregard an outage.
Configuration errors, revoked permissions, exhausted agreed quotas, missing consent, and unsupported instrumentation can explain absent telemetry without a collector outage. Each incident still needs to be evaluated against the covered function.
Credits and incident reports
No automatic service credits or refunds arise from this draft. Any paid SLA must state its credit schedule, claim process, evidence requirements, submission window, and any termination right before the customer subscribes.
Report a platform outage with its impact, start time, affected project, and any available request identifiers. A support priority is an intake classification, not an uptime calculation or a guarantee of repair.
Separate security and data duties
Service availability does not replace confidentiality, privacy, or incident-notification obligations in a final agreement. Keep your own recovery plans, backups, and monitoring appropriate to the importance of your application.
Discuss any required production guarantee before relying on Everock for a critical workload. A bespoke commitment requires a final written agreement; it is not created by the usage calculator.
