ScoutSentinelScoutSentinel
Menu

Operational resilience, evidenced

Prove your important
business services work,
every minute.

Independent, outside-in assurance that your customers can actually buy, pay, log in and claim, with the evidence to show your board and your regulator.

Join the pilot See an example

Business services

Start with what must keep working

Buy a policy, make a payment, log in, submit a claim. Name the services your customers and your regulator care about, and prove each one as the journey a customer actually takes.

  1. 01

    Name the service

    Start with an important business service and the customer journey that proves it, in plain language. Say what success looks like, where to test from and how often.

    Customers can buy a motor policy online with a test card and receive a policy number.

  2. 02

    Approve the checks

    ScoutSentinel proposes the steps and the rules that decide success. Every rule is visible and editable, and nothing runs until you approve it.

    7 steps · 9 assertions · every 5 min · London, Frankfurt, Sydney · browser + API

  3. 03

    Know when it needs you

    Related failures become one clear Event for the service: where the journey broke, what still works and the evidence behind the conclusion.

    1 Event, 6 observations, 3 locations · payment gateway 502 · confidence 92%

Continuous assurance

Can a customer actually get the outcome?

Every service is exercised from outside your infrastructure, on web, API, email and phone, on the schedule you set. The question is whether the customer got the outcome, not whether a server answered.

Explicit rules decide what passes. A check that could not run is reported as unknown, with a reason, and never counted as your outage. AI helps plan and explain; you stay in control of changes.

  • A list of scripts and their pass/fail history

    ScoutSentinel: A business service, its health and the last time it was proven

  • Alerts on every failed check

    ScoutSentinel: Related failures grouped into one actionable Event

  • A red dot and a stack trace

    ScoutSentinel: The failure boundary, what still works, confidence and coverage

  • Billing by browser minutes

    ScoutSentinel: A predictable price per Watch, with a fair-use probe budget

  • Self-healing tests that hide change

    ScoutSentinel: Versioned repairs: review suggestions or explicitly enable verified automation

  • Infrastructure errors reported as your outage

    ScoutSentinel: An explicit unknown state, never mistaken for your outage

Evidence

What happened, from where,
and how sure we are

One Event per problem, not fifteen alerts. See where the failure begins, what still works, the confidence behind the conclusion and the screenshots and responses that support it.

CriticalOpenOutcome eventOpened · evt_01J8Q1F7N2WC

Buy online: purchase cannot be completed from any tested location

Since 04:25 UTC the payment step of Buy online fails from London, Frankfurt and Sydney. The payment provider endpoint pay.example-psp.com/v1/payments answers 502 in 30 seconds on every attempt. Steps 1 to 6 succeed and the API quote endpoint is healthy, so the failure boundary is the third-party payment gateway, not shop.example.com itself.

Failure boundary

Step
Step 7 · Complete purchase
Where
POST https://pay.example-psp.com/v1/payments
Observed
HTTP 502 Bad Gateway after 30.1s (3 of 3 locations, 2 consecutive runs)
First seen
04:25:34 UTC from London

What still works

  • Steps 1 to 6 of Buy online (homepage, search, traveller details, quote, basket)
  • POST /api/quotes: 200 in 1.3s median from all locations

Confidence

92%

  • 3 independent locations agree (London, Frankfurt, Sydney)
  • 2 consecutive runs per location, 10 minutes apart

Coverage

Tested

  • Cloudflare edge: London, Frankfurt, Sydney
  • Browser probe (Chromium 130) and API probe
  • Test card path only

Not tested

  • Apple Pay and PayPal paths
  • Mobile app checkout
  • Residential or carrier networks

Last refresh 04:31 UTC

Evidence

shop.example.com/checkout04:25:04Z
Pay £128.40
Checkout page before the payment attempt: card form and an enabled Pay £128.40 button, order total £128.40.

Step 7 at 00:00, before the payment request was sent.

  • Screenshot before payment (step 7, 00:00)sha256 3f9a1c…b27e · 184 KB · 04:25:04Z
  • Screenshot after error (step 7, 00:31)sha256 9d2e77…41ac · 177 KB · 04:25:35Z

Every artefact is timestamped, hashed and linked to the Event.

Inspect the complete Event →

Explore the full version with the change context and timeline in the interactive examples.

Resilience

Know what works.
See what changed and what needs you.

Every service in one view, with Events linked to the releases, suppliers and infrastructure changes around them, and reports you can take to a risk committee.

  • Outcome and behaviour, separately. A journey can still succeed while becoming materially different. You see both, so a change is reviewed before it becomes an incident.
  • Change and supplier context. Releases, certificate and DNS changes and the providers a service depends on sit beside its Events.
  • Reports per service. Assurance, incident and supplier reports today. Tracking against each service's impact tolerance is being built with our pilot customers.

Events arrive where your team already works: email, Slack, PagerDuty, Jira Service Management and signed webhooks. All integrations.

Pricing

A clear price for peace of mind.

Pay per Watch, not per browser minute. Each Watch checks one customer capability, with evidence included on every plan.

  • Starter

    …Loading price

    Small SaaS or a single digital team

    • 5 Watches
    • 15-minute minimum interval
    • 30 days of evidence
    • Email and webhook alerts
    • Cloudflare edge locations
    Join the pilot

  • Team

    Most teams

    …Loading price

    Product operations and SRE teams

    • 25 Watches
    • 5-minute minimum interval
    • One year of history
    • Slack, PagerDuty and GitHub
    • Role-based access
    Join the pilot

  • Business

    …Loading price

    Transaction-heavy mid-market organisations

    • 100 Watches
    • Cross-channel allowance (voice and email)
    • Longer evidence retention
    • SSO (SAML and OIDC)
    • Regional runners (named cloud and region)
    Talk to us

  • Enterprise

    …Loading price

    Regulated or large organisations

    • Custom Watch policy and service levels
    • Private locations (customer-hosted probes)
    • Audit controls and evidence export
    • Data residency options
    • Security integrations and SIEM export
    Talk to us

These prices are launch hypotheses we are testing with design partners, not a final commitment. Anyone who starts during the pilot keeps their price for twelve months. Full comparison and FAQ.

Trust

Evidence you can stand behind

Assurance is only as good as the evidence behind it and the care taken with your data.

Visit the trust centre
  • Verifiable evidence. Every artefact is hashed when it is captured. Before the pilot we are adding a signed, independently timestamped ledger, so an auditor can check offline, with an open verifier, that evidence has not changed since it was sealed.
  • Credentials stay private. Encrypted at rest and scrubbed from evidence, logs and AI prompts.
  • Recognisable test traffic. Documented identifiers and a marker you control for allowlisting. Read the policy.
  • Your organisation, isolated. Organisation-scoped data with row-level security as a second line of defence.

Pilot

Join the pilot

We are onboarding a few organisations at a time. Leave your address and we will be in touch when your account is ready, and we will set up your first business service with you.

We use your address only to contact you about early access and, if you tick the box, to tell you when we launch. No newsletter, no sharing with anyone else, and you can ask us to delete it at any time at privacy@scoutsentinel.com. See our privacy policy.

Want to tell us more first? The full form asks which journey you would watch.

Start with one important business service

Name the service your customers and regulator care about most. We set up the first journey with you, you approve every check, and the first evidence arrives within minutes.

Join the pilot Request a free journey assessment

Interactive example

Replay an example journey

Watch ScoutSentinel step through "Buy online" with per-step timings and deterministic assertions, then switch to the failing run to see where the boundary is.

Buy online

Complete a purchase on shop.example.com

London, UK (Cloudflare edge) · started Passed
  1. Load homepage2.1s

    https://shop.example.com

    • HTTP status is 200passed
    • Search form is visible within 3spassed
    not started
  2. Accept cookies0.8s

    click: [data-testid=cookie-accept]

    • Step completed without errorpassed
    not started
  3. Search product4.2s

    type: Lisbon, 2 travellers, 14 nights

    • At least 1 result renderedpassed
    not started
  4. Enter traveller details12.6s

    fill: name, date of birth, email

    • Step completed without errorpassed
    not started
  5. Get quote7.3s

    POST /api/quotes → 200 in 1.3s

    • POST /api/quotes returns 200passed
    • Premium between £40 and £400passed
    not started
  6. Add to basket4.1s

    click: Add to basket

    • Basket total equals quotepassed
    not started
  7. Complete purchase10.8s

    test card 4242, expect confirmation

    • Payment request returns 2xxpassed
    • Confirmation number matches /^ORD-\d{8}$/passed
    not started
Total 41.9scf-edge · chromium 130 · probe 0.1.0
shop.example.com

Step 1 of 7

Adventure starts here

Search form visible, hero rendered, 0 console errors.

Not started.

Want the full explanation? Read the example Event with the failure boundary, what still works, confidence and coverage.