STATUS

What an outage can and cannot affect.

ZeroWrite is built so that our availability is never your security posture. Protection is local; our servers deliver improvements to it.

No incidents reported

We publish incidents affecting licensing, updates, or the website here and on our release channel. A live status feed will replace this panel once the licensing service is deployed to production.

What depends on our servers

Pre-execution protection

FULLY LOCAL

Runs entirely on your machine. Unaffected by any outage on our side.

Rule-pack updates

NEEDS NETWORK

Delivered from our infrastructure. During an outage the engine keeps using the last verified pack.

Application updates

NEEDS NETWORK

Served from GitHub Releases. An outage delays updates, nothing more.

Licence activation & refresh

NEEDS NETWORK

Needed to activate a new machine. Already-activated machines keep working offline until their token expires, with 14 days of grace on top.

Website & account portal

NEEDS NETWORK

Sign-in, licence management and billing.

The guarantee behind this table

A security service must never need a network round trip to decide whether to protect you. Entitlement is a cryptographically signed token verified on your own machine, and detection runs locally. That is a deliberate architectural constraint, not a happy accident — read more in the documentation.

Seeing something broken that is not listed here? Tell support.