ScoutSentinelScoutSentinel
Menu

Company

A more resilient internet, one customer journey at a time

ScoutSentinel exists because the question that matters during an incident, can customers still get through, is rarely the one internal telemetry answers first.

About

We started ScoutSentinel after too many incidents where every dashboard was green and customers still could not buy, sign in or reach support. The tools that exercise journeys from the outside treated them as scripts and billed by the browser minute; the tools that understood business impact had no evidence.

ScoutSentinel is an outcome-led assurance product. You describe a customer capability in plain language, we turn it into deterministic Watches, run them from controlled external locations, evaluate explicit assertions, keep evidence hashed at capture and correlate related observations into one Event that tells you the failure boundary, what still works, confidence and coverage.

We are launching narrowly around web and API journeys for regulated and transaction-heavy organisations: insurance, financial services, travel, marketplaces and software. Voice and email journeys, external exposure and, much later, evidence-backed attack paths are earned adjacencies, not a launch promise.

ScoutSentinel Ltd is a company registered in England and Wales. We are a small team of engineers who have run operations for insurers, banks and marketplaces, and we are working with a handful of design partners before general availability.

The ScoutSentinel mascot: an egg-shaped sentinel with a tie and spear

"Different perspective. Fewer surprises."

Our sentinel stands outside your stack on purpose. It sees what your customers see, and nothing else.

Product principles

  • Outcomes before probes

    The primary object in the product is the business capability. Probe mechanics stay inspectable but secondary.

  • Evidence before interpretation

    Screenshots, traces, responses and configuration snapshots support every conclusion. Summaries link back to sources.

  • Outcome and behaviour are separate

    A journey can remain achievable while becoming materially different. Both states must be visible.

  • Use the cheapest sufficient probe

    HTTP, DNS or API when they prove the assertion. A browser only when rendering or interaction is necessary.

  • Show coverage and confidence

    Every conclusion exposes what was tested, when, from where, with what evidence and what remains unconnected.

  • Keep automation reversible

    Adaptive changes are previewed, versioned and auditable. High-impact changes require approval.

  • Design for quiet operations

    Correlate observations into Events, suppress known noise and alert only when business relevance is met.

  • Say what we do not know

    No identified path, never no path exists. Unknown is a state, not a failure.

Contact

Talk to us

We answer email ourselves. For a free external journey assessment of one public path, tell us the URL and what a customer should be able to do there.

Registered office details and company number will be shown here once published. Until then, contact us by email.

Request a free journey assessment

Email us the details below and we will run one public journey from three locations and send you the evidence. No account needed.

  1. The public URL where the journey starts.
  2. What a customer should be able to do there, in one sentence.
  3. Any test data we should use (never real customer accounts).