Our availability commitment, stated honestly.
Three sentences, no asterisks: there is no formal SLA during early access. We publish live status on independent third-party monitoring instead of asking you to take our word for it. A credit-backed SLA ships together with paid plans — and the proofs you anchor today don’t wait for either.
No formal SLA yet — and no number we won’t stand behind.
Satsignal is in early access, onboarding design partners. We run the service to be up, and the status page shows what an independent monitor sees — but we do not promise an uptime percentage today, and we won’t print one until it comes with credits behind it. If a stretch of downtime would hurt you, tell us what you need at hello@satsignal.cloud — availability riders are part of the design-partner conversation.
A credit-backed SLA ships with the paid tiers.
When the paid Starter and Pro tiers open (they are planned, not yet self-serve), they will carry a formal, credit-backed SLA on the anchoring service. The headline we are engineering toward is 99.5% monthly availability on paid tiers. Treat that as the published target it is: it becomes a contractual commitment when the paid plans launch with their SLA terms, not before.
Your existing proofs don’t depend on our uptime.
This is the structural difference from a hosted log: a Satsignal
anchor is a real Bitcoin SV transaction, and your downloaded
.mbnt bundle is everything a verifier needs to tie your
payload’s fingerprint to it. The bundle’s internal
integrity checks fully offline; confirming the transaction exists
on-chain works against any public BSV explorer, with or without
Satsignal. The verifier
is a single static HTML file you can save, audit, and run offline.
An outage on our side affects the service, not the proofs:
Interrupted by an outage
- Anchoring new proofs (dashboard and API)
- Downloading a bundle still in server-side retention
- Sealed-mode selective reveals via
/unseal /lookup_hashre-binding, if you never downloaded your bundle
Unaffected by an outage
- Verifying any
.mbntbundle you hold — offline integrity check plus any public BSV explorer - The on-chain anchors themselves — the chain is operated by independent miners, not by us
- A saved copy of the static verifier file — its checks are embedded and run locally (the one exception: on-demand PDF text re-extraction fetches a library from us)