Roadmap

This page shows what we are working on next in Guard Dog, and roughly in what order.

It is deliberately light on dates. Security work has a habit of turning up something that has to jump the queue, and we would rather move an item than miss a promised date. Order can change; the list itself is honest about where each item stands.

Next

A CAPTCHA that never phones home

Every CAPTCHA Guard Dog supports today — reCAPTCHA, hCaptcha, Turnstile — sends your visitors’ data to a third party. That is a reasonable trade for a lot of sites, and those options are not going anywhere.

But it is a genuine problem for some. If you are subject to GDPR, if you have a privacy policy you actually intend to honor, or if you simply do not want a third party in your login flow, every current option asks you to accept something you would rather not.

We are adding ALTCHA: a self-hosted proof-of-work challenge. No third-party request, no tracking, no data leaving your site. Your visitors’ browsers solve a small puzzle, your server checks the answer, and nobody else is involved.

Recently added

• Templates for every email — the email customizer now covers all of Guard Dog’s emails, and can optionally style WordPress’s own password reset, new user, password changed and email changed emails. Each WordPress template is opt-in, and Guard Dog stays out of the way when another plugin already handles that email.
• GitHub, LinkedIn and Facebook sign-in — optional social providers with email confirmation before an unverified address can link or create an account. Social sign-in now follows Guard Dog’s two-factor checks by default.
• Magic Login — optional single-use email sign-in links for existing accounts, with two-factor still enforced. Useful as a passkey recovery path.
• Passkey cleanup — supporting password managers are now asked to stop offering a passkey once its owner deletes it, instead of leaving an orphaned entry behind.
• Login screen theme headers and footers — independent header and footer options for login screen customization, supporting both classic and block themes.
• Broader IP address matching — IPv4 access rules also match IPv4-mapped IPv6 visitor addresses, so a rule written for 203.0.113.0/24 matches a visitor reported as ::ffff:203.0.113.5. Genuine IPv6 addresses still need their own rule.
• Fully translatable activity log — all 121 built-in event types can now be translated, rather than only 7.

Have an opinion?

This list is shaped by what people actually ask for. If something here matters to you, or something missing matters more, we would rather hear it early than guess.

The fastest way to influence the order is to tell us which of these you would actually turn on, and why.