Service level agreement

An SLA needs measured service boundaries, not a marketing number.

The final agreement must define what is measured, how exclusions work and what remedy applies.

Draft — not effective. This page still needs the operator’s legal identity, jurisdiction and service-specific review before publication.

Covered service

Define whether availability covers the public API, event delivery, dashboard, individual chain adapters or a specific paid module.

Set the observation source, monthly calculation, latency boundaries and treatment of partial degradation.

Address scheduled maintenance, customer systems, upstream blockchain or node outages, force majeure and misuse without making exclusions unlimited.

Define incident priorities, response targets, reporting, claim process and service credits or other remedy.