CSPM · IAM graph · container and IaC scanning

Your scanner found 900 problems.
Three of them can end you.

Osprey correlates misconfiguration, identity reach, network exposure and CVEs into the handful of combinations an attacker can actually walk — and it does it on your laptop, against your account, without sending a byte to a vendor.

Download See what it finds
Time to first report
< 5 min
Correlation rules
25 built in
Data sent to a vendor
None

Findings are noise. Combinations are incidents.

A public bucket is a ticket. An over-permissive role is a ticket. A critical CVE is a ticket. They sit in three different tools, get three different owners, and each one is triaged as low priority because, alone, each one is.

An internet-facing service, running an image with that CVE, carrying a role that can pass any role, is not a ticket. It is an account takeover — and nothing in your stack is looking at all three at once.

  • 1 Internet-facing service
  • 2 Container escape in its image
  • 3 Role may pass any role
  • = Full account compromise

What you get, five minutes after installing

One local scan of a demonstration account. No agents were installed, nothing was written to the account, and nothing left the machine.

The osprey console showing a critical toxic combination, with the evidence lines that made it fire.
Every combination shows why it fired — the grant, the path, the finding. You can check the tool's reasoning instead of trusting a score.
Privilege-escalation paths listed hop by hop, from a role to a wildcard grant.
Escalation paths, hop by hop. Cut any single hop and the path is gone — so you can see the cheapest fix, not just the longest list.
The findings table with severity filters, showing CVE and IAM findings side by side.
The full inventory is still there when an auditor asks. It is just not what greets you first.

How it works

  1. Read, never write

    Osprey uses the AWS credentials already on your machine, or a read-only role it generates for you. Every call is a configuration-plane read: no agent, no data-plane access, no snapshot.

  2. Build the graph

    Principals, policies, resources, trust relationships and internet exposure become one property graph, then CSPM and container findings are attached to the resources they belong to.

  3. Correlate, then explain

    25 deterministic rules find the combinations. Optionally, a model on your own key ranks and narrates them — reading a pseudonymized digest, never your ARNs.

The part your security team will ask about

Your cloud metadata never leaves your machine. There is no vendor backend to send it to, no account to create, and no telemetry. The only outbound calls are to your own cloud provider — and, if you turn them on, to the scanner engines and the model endpoint you chose.

This is why osprey gets through review at companies that will not put cloud metadata in a SaaS: there is nothing to review. No data processing agreement, no sub-processor list, no breach surface, because the vendor operates no servers at all.

What it deliberately will not do

Download

One archive per platform, holding the CLI, the console it serves and — everywhere but Linux arm64 — the desktop window. Nothing is entered here and no account is made: the 30-day trial starts at your first scan and is counted on your own machine.

The macOS builds are not notarized and the Windows builds are not signed. Both systems say so the first time you launch one, both let you continue, and the wording and the clicks are below.

Or install the CLI from a terminal

# read it first — served from this domain
curl -fsSL https://osprey-hq.com/install.sh | less
# then, if you are happy with what it does
curl -fsSL https://osprey-hq.com/install.sh | sh

install.sh works out your platform, takes the archive above and that release's checksums.txt, stops without installing anything if the sha256 does not match, and copies one binary — osprey — into /usr/local/bin when that is already writable and ~/.local/bin when it is not. It never calls sudo, and it does not install the desktop window: putting an application into /Applications is something you should choose, not a side effect of a pipe into a shell. --dry-run prints the plan and downloads nothing.

Check what you downloaded

Every release publishes checksums.txt. Save it next to the archive and check the bytes yourself: 

sha256sum --ignore-missing -c checksums.txt

macOS ships shasum instead: shasum -a 256 --ignore-missing -c checksums.txt. The flag is there because checksums.txt covers all five archives and you took one of them; without it, the four you did not download are reported as failures.

What your operating system will say

macOS. The app is not notarized, so Gatekeeper stops the first launch: "Apple could not verify that Osprey is free of malware" on macOS 15, "the developer cannot be verified" before that. Open System Settings, then Privacy & Security, and click Open Anyway in the line about Osprey; on macOS 14 and earlier, Control-click the app and choose Open. The CLI that install.sh puts in place is unaffected — curl does not attach the quarantine flag that a browser download carries.

Windows. The executables are not signed, so SmartScreen shows "Windows protected your PC" and names the publisher as unknown. Click More info, then Run anyway.

Linux. Nothing checks and nothing warns. The desktop window needs libwebkit2gtk (Debian and Ubuntu: libwebkit2gtk-4.1-0); without it osprey-desktop falls back to a browser window.

Notarization and an authenticode certificate are bought, not earned, and neither is in place yet. Until they are, the checksums are the thing to check — and they are published for every release, signed or not.

Pricing

One product, one price

30 days freeeverything included, no card

then $199 per user, per year

The trial starts the first time you run a scan and is counted on your own machine. There is no account to create, nothing to cancel, and no server of ours that knows you tried it.

Download
  • Every scan: CSPM, IAM graph, containers, IaC
  • All 25 correlation rules and escalation paths
  • HTML and JSON reports
  • Scheduled worker with Slack and Teams alerts
  • The console and desktop app you see above
  • AI review on your own key, or a local model
  • One-click Terraform pull requests
  • Multi-account views

When the trial ends, scanning and AI stop. Every scan you already ran stays readable — the combinations, the paths, the findings — and osprey report keeps exporting them. Nothing you have already collected is locked away.

You pay your own cloud-API and model-token costs directly. There are no servers between you and them to mark up.

Before you buy it, or when the 30 days run out

A licence key is what keeps scanning and AI analysis running after the trial, and mail is how you get one. Ask before that if you want to know whether osprey covers something you run — sometimes the answer is no, and it costs less to hear that from a person than to find it out on day three.

hello@osprey-hq.com

A person answers. We do not run a mailing list, and there is nothing to unsubscribe from.