I built Hound to make serious testing repeatable.
I spent years building production infrastructure, identity, platform, and operational systems. Hound comes from that view of software: real risk lives in auth, roles, state, workflows, and trust boundaries. Serious testing should be practical enough to run as the app changes.
Why it exists
Web apps change faster than security testing can keep up.
Most teams get one of two choices: a deep human pentest that's hard to schedule and hard to rerun, or a scanner that misses the logic of the app.
Hound is built for the gap between them: serious testing that can run against real app behavior, with approved accounts, guardrails, and repeatable runs.
The builder
Real systems shaped how I think about security.
Before Hound, I spent years close to the infrastructure, identity, platform, and operational layers where software gets complicated. That shaped how I think about security: the important failures usually come from how systems interact.
Associate to Principal in under four years at Fidelity
Worked on critical brokerage systems and digital assets infrastructure
Built infrastructure, data, DevOps, IAM, and platform systems
Built solo internal tools that later became team-owned systems
Built low-level Rust systems, including a custom RISC-V to x86 assembler and runtime
Product belief
Serious testing should be practical without becoming shallow.
Hound is built around a simple belief: serious testing should go deep enough to matter and stay practical enough to run again.
Risk lives in behavior.
Auth, roles, company boundaries, approvals, state, and workflows are where applications fail in ways scanners miss.
Testing should be repeatable.
Teams ship too often for security testing to be a rare calendar event. A one-off test goes stale as soon as the app changes.
Findings need proof.
A finding has to be proved, scoped, and explained clearly enough for a team to act on it without guesswork.
Product focus
Built for auth, roles, state, and workflows.
Logs in like a user
Hound uses a real browser, handles MFA, and works through the screens, flows, and permissions your application actually exposes.
Tests across accounts
Multiple approved identities let Hound test role boundaries and cross-tenant behavior safely.
Explores attack chains
The important bug often isn't one request. It's the path from one weak boundary to the next.