OUTSIDE
Back to overviewSign inStart a pilot

For managed service and security providers

Watch every client's external surface from one place.

Your clients' public infrastructure changes without telling you. A staging host appears, a certificate lapses, a service opens a port between two audits. OUTSIDE watches all of it continuously, tells you what changed and why it matters, and gives you the evidence to show the client.

Start a pilotScan a client domain first

Passive by default · No agents · No client credentials to begin

What this replaces

The gap between two audits is where exposure lives.

Point-in-time reports go stale immediately

A quarterly assessment describes the surface on the day it ran. Everything a client's developers deploy afterwards is invisible until the next one.

Client inventories are never complete

The hosts you were told about are not the hosts that exist. Forgotten subdomains and shadow services are exactly what an outsider finds first.

Proving the work is manual

Showing a client that a problem is genuinely resolved usually means screenshots and a written explanation, assembled by hand, every time.

How it works

One workflow, however many clients.

  1. 01
    Add client domains

    Each client becomes its own isolated workspace. Ownership is verified by DNS record or a hosted file before anything active runs.

  2. 02
    Monitoring runs continuously

    Scheduled scans compare each client's external surface against the last one and separate real change from background noise.

  3. 03
    Change arrives with context

    Every alert names the observation behind it, its confidence, and what to do next — routed to Slack, Teams, Jira or your ticket queue.

  4. 04
    The client gets proof

    White-label reports carry the evidence, the change history and, where OUTSIDE applied a fix, the check that confirms it from the public internet.

The Guardian workspace for one client domain
One client, one workspace: what changed, what it means, and what to do next. Every provider you add gets its own. Synthetic demonstration data — never a customer's surface.

What you get

Portfolio view

Every client, their open items and their drift, ranked so the urgent one is obvious.

White-label reporting

Client-ready documents under your own brand, on your own domain.

Isolated tenants

One client's data is never reachable from another's workspace. Roles, groups and portals are enforced server-side.

Evidence that holds up

Each finding traces to a recorded observation, so a client question has an answer rather than an opinion.

Pilot programme

Try it on real clients, not a sandbox.

Pick a handful of client domains and we will set them up together. You keep the reports whatever you decide afterwards.

  • Up to ten client domains under full monitoring
  • Personal setup — domains imported and alerts configured with you
  • A client-ready report you can actually send
  • Direct line to the person who builds the product

In exchange we ask for one honest conversation at the end about what worked and what did not.

Start with one client.

Run a passive snapshot on a single client domain and see what comes back before committing to anything.

Scan a client domain first