Is your software patched? Is anything exposed?
Current findings by severity, the posture of each site and server, and the per-site changelog for the period the pack covers. This is the half the scanner has always produced.
StackHound watches the sites and servers you run, trains your staff, and records which version of your policy they agreed to — then assembles both halves into one dated document for an insurer, a client, or an assessor. Every row is an observation with a date on it. Nothing in it claims you are compliant.
One document, generated on demand, for the reader who will spend four minutes on it — an underwriter working a renewal, an account manager processing a vendor review, or an owner filling in a form.
Is your software patched? Is anything exposed?
Current findings by severity, the posture of each site and server, and the per-site changelog for the period the pack covers. This is the half the scanner has always produced.
Are your staff trained? Have they acknowledged your policies?
Per person: which modules they completed, which version, on what date, with what score — and which version of your handbook they agreed to, with the exact words they agreed to.
It never prints the sentence “you are compliant.” If you want to assert that, you assert it — StackHound supplies what you assert it from. That distinction is deliberate, and it is worth losing a prettier document over.
“Rebecca Hall completed Phishing and the three tells (v1) on August 14, 2026, scoring 90%.” Not “Acme Plumbing meets the standard.”
A single number for the whole pack is a verdict wearing a statistic’s clothes, and it is the first thing a reader would quote back at us. Counts and dates instead.
Unmonitored sites, staff with no record, controls we cannot see. A pack silent about its own blind spots is the failure we exist to avoid, in a nicer typeface.
Each pack and certificate carries a verification code that reads back the organization, the dates and the status — and discloses nothing about your staff.
Enroll colleagues by email; each gets a magic link, reads a short module and answers questions that are graded on our side, so the answer key never reaches the browser. On finishing, they can send the record to whoever asked for it. Learners are not billable users and never consume a seat.
Three modules, about five minutes each — phishing, paying the right people, and telling someone when it goes wrong. The record states what was completed, never that a requirement has been met. See the course →
Add your staff handbook or acceptable-use policy. Staff agree to the exact text, and the acknowledgment is recorded against that version’s SHA-256 — so it proves which words they saw, years later, even if you have lost the file.
Publish a new version and old acknowledgments are never silently re-pointed at it. The pack reports that eleven of fourteen staff are on the current version and three are not, which is the honest gap rather than a hidden one. The annual clock runs per person from their own date.
Policy acknowledgment and staff training are free on every plan, Free included — and the staff you enroll are not billable users, so a one-person workspace can still run acknowledgment across the whole team. The evidence pack itself is on Solo and above: you pay when someone actually asks you for the document.
StackHound does not replace the tools admins already use. It reads them, correlates them, and grades what it finds — so the answer you hand over is the same one you work from every day.
StackHound detects exposed secrets in your public site assets — without storing or validating the secret. Known prefixes plus an entropy floor, not regex alone. It is the one website-only finding that comes back confirmed rather than possible.
Watch domains, headers, TLS, WordPress fingerprints, exposed services, DNS, third-party scripts, and public vulnerability matches.
Bring in package versions, WordPress core and plugin versions, SSH configuration posture, Fail2Ban events, and ClamAV hits — with a Servers, Controls, and change-timeline view on Solo and above.
See why a finding was ranked, what matched your stack, whether it is confirmed or only possible, and what to do next.
Built first for WordPress operators, agencies, and server admins who need clarity without a full security operations team.
Free is free and takes no card. Solo and Agency start with a 14-day trial, which does take a card — you are not charged until it ends, and you can cancel before then. Enterprise is still a conversation, because its limits are set per customer rather than sold off a page.
$0
One site, watched for free. No card, no account gymnastics.
$12 /month or $120 a year
For a freelancer or small team watching a handful of sites and one server.
$99 /month or $990 a year
The wedge tier — built for WordPress maintenance agencies running a client estate.
Larger fleets and security teams. Still a conversation — its real terms are a bespoke limit set, which a fixed price cannot express.
Free, Solo and Agency you can start yourself. This is for Enterprise, or for anything that does not fit a plan — tell us about your sites and servers and a person will answer.