Protection updates

How protection keeps moving.

GuardianBlock protection isn't a one-time list. Every release is compiled, validated, signed, and published through the same pipeline — and this is where we show what's live, in plain numbers, without overpromising.

The current signed releasePre-release
The first signed release is being prepared.Counts appear here the moment a validated, signed release is published — never before, and never by hand. Until then there is nothing to show, and we won't invent a figure.

How these numbers are defined

What a protection release is
  • Built the same way every time

    A release is compiled deterministically from the maintained protection corpus, so the same inputs always produce the same release.

  • Validated, then signed

    Each release is checked against its own invariants and then signed with a managed key before it can be published or reach a device.

  • Counts come from the signature

    The numbers above are sealed inside the signed release and snapshotted, so what you see is provably the same as what was signed.

Recent updates

No published protection updates yet — the change feed lights up with the first significant signed release.

Protected by accountability, not guesswork.

GuardianBlock pairs a maintained protection release with a guardian who keeps you honest. Join the private beta to be part of it.