VettedWP Start free trial

A management tool that can't be used against you

A tool that manages your sites is the most dangerous software you install: it can reach every one of them. We've spent our careers protecting systems that can't afford to fail. Here is exactly what ours can and cannot do, including the parts we will not claim.

Start free trial

What your site holds

  • Only our public key: it can check, not sign
  • Every request signed; a captured one can't be replayed
  • Every reply signed with the site's own key

Who builds it

Built by people who keep critical systems running

VettedWP is built by an infrastructure and security team with more than 16 years running large platforms that millions of people rely on every day. We've led vulnerability response under pressure, patched systems that couldn't go down, and answered to auditors for every change.

We built VettedWP to bring that same discipline to the WordPress sites you and your clients depend on: nothing changes without a way back, every backup is checked, and every action leaves evidence.

About us

Your site holds nothing that can sign

The plugin carries our public key. It can verify that an instruction came from us; it is mathematically incapable of producing one. There is no shared secret on your site to steal, so compromising one site does not yield anything that works against another.

Every request is signed over its method, route, connection, timestamp, a one-time nonce and a hash of its body. Stale timestamps and reused nonces are refused, so a captured request cannot be replayed.

The signed channel between the platform and your site The platform holds the private signing key and sends signed requests. Your site's plugin holds only the platform's public key, which can check a signature but cannot make one, and signs its replies with its own key. The platform Private signing key Checks every reply Your site's plugin Public key only: can check, cannot sign Own key for replies Signed request time, one-time nonce, body hash Signed reply, bound to the request

The public-key design describes the WordPress plugin. It is not a claim about any other kind of site. We do not claim that any competitor is currently vulnerable; where we mention a past CVE, we mean the class of design that made it possible.

What else protects your sites

  • Your site can prove its answers

    At pairing, your site generates its own keypair and keeps the private half; we only ever receive the public one. Its replies are signed and bound to the exact request that asked for them, so an old answer cannot be replayed and nobody in the middle can alter one.

  • We can change our key without touching your site

    The platform's signing key can be rotated across every site without touching any by hand: each site is handed the new public key over the channel it already trusts, and we only switch once every site has confirmed it holds the new one.

  • What we encrypt

    • Credentials and secrets, at rest. No WordPress admin password is ever stored: the channel uses signatures, not passwords.
    • Backups, before they leave your site.
    • Reports and screenshots, before they are stored.
    • Client report links expire, can be revoked and can take a password.

A rotation is authorized by the key it replaces. That covers a suspected compromise, key aging and ordinary hygiene, but not a confirmed, active compromise of the signing key: an attacker holding it could rotate too, and that case means re-pairing. There is one platform key, rotatable, held in an encrypted secret store; we do not claim hardware key custody or a separate key per customer. Every change is recorded in the audit log, but immutability is not enforced at the database level, so we do not claim an immutable log.

Try it on your own sites

Read it, then test it.

Start free trial

14 days of every Business feature on up to 5 sites. Cancel before it ends and you pay nothing.