You run engagements. Recon, exploitation, evidence collection, reporting — and a timeline that's always too tight. We built two tools for different parts of that cycle, and they talk to each other through the platform.
StrikeKit
The engagement workstation. When you're running a pen test from planning through the final report, this is where you live.
- Plan and scope — define objectives, map targets, track credentials, and build your attack plan with an AI assistant that actually knows the domain
- Execute and track — log evidence, map findings to kill chain phases and MITRE ATT&CK techniques, manage C2 operations, and keep a timeline of everything
- Report — generate deliverables from the data you've already collected, not from scratch in a word processor at 2am
- Collaborate — checklists, notes, and shared engagement state so the whole team sees the same picture
Get started with StrikeKit →
Read the docs →
Pick
The headless recon agent. Drop it on any system and control it remotely — no GUI needed, no heavy install.
- Scan and discover — port scanning, device discovery, and network mapping from wherever you deploy it
- Capture traffic — packet capture and analysis without needing a separate tool
- Execute remotely — run tools on target systems through Pick's remote execution capability
- Stay light — single binary, deploys anywhere, controllable from StrikeHub or remotely via the platform API
Get started with Pick →
Read the docs →
How these fit into the platform
Both StrikeKit and Pick are connectors that plug into Prospector Studio — the AI backend. That means agents can orchestrate scans, correlate findings across engagements, and help with analysis. They run inside StrikeHub on your desktop, or headless via the API. For the full picture, see How It All Fits Together.