background map

Holstr Documentation

Build clear evidence. Faster.

Holstr helps teams capture user flows, analyze web risk, and generate polished documentation artifacts from a single desktop workflow.

Holstr is a WinUI desktop application designed for structured capture and reporting.

Product Guide

Capture, Analyze, and Export With Confidence

What is Holstr?

Holstr is a WinUI desktop application designed for structured capture and reporting. It combines three core capabilities:

  • Captr - Record user interactions with clear, traceable event steps.
  • Cybr - Analyze web content and security-relevant findings.
  • Export - Produce shareable HTML and PDF outputs for audits, reviews, and handoffs.

Quick Start

  • 1. Open Holstr and create a new session.
  • 2. Choose a capture mode:
  • WebAppCaptr
  • BrowserCaptr
  • DesktopAppCaptr
  • 3. Perform the workflow you want to document.
  • 4. Review event tiles and annotations.
  • 5. Run analysis in Cybr (Cybr / Mapr / Injectr modes).
  • 6. Export your session as HTML or PDF.

Captr: Event-Based Workflow Capture

Captr records meaningful user actions in a structured format.

Each event tile includes:

  • Action
  • Name
  • Role
  • Date/Time

Use Captr when you need reproducible workflow evidence for QA, security review, compliance, or training documentation.

Cybr: Security and Content Analysis

Cybr provides focused analysis views for different investigation tasks:

  • Cybr Mode - General scan and summary findings.
  • Mapr Mode - Visual mapping and navigation of analysis context.
  • Injectr Mode - Payload and request/response-oriented investigation support.

Use Cybr outputs to support triage, validation, and reporting across engineering and security teams.

Export and Reporting

Holstr export is designed for enterprise-ready delivery:

  • Structured HTML output for internal portals and sharing.
  • PDF output for stakeholder distribution and archival.
  • Consistent branding and layout for repeatable reporting.

Exports are suitable for incident records, assessment reports, and implementation handoff packages.

Best Practices

  • Capture one scenario per session for cleaner evidence trails.
  • Use clear session names aligned to ticket or incident IDs.
  • Add annotations as you work to reduce post-processing time.
  • Validate findings in Cybr before final export.
  • Keep exported reports with source artifacts for traceability.

Troubleshooting

If results are not as expected:

  • Re-run the scenario in a fresh session.
  • Confirm the correct capture mode is selected.
  • Verify required permissions for desktop and browser interaction.
  • Export to both HTML and PDF to compare output formatting.

Need Help?

For implementation support, issue triage, or rollout guidance, contact your Holstr platform owner or internal engineering support channel.