Integrations

Argus meets your stack where you build

From your repo to your live site, Argus connects over secure OAuth in minutes — no agents to babysit, no keys in your dashboard. GitHub, Vercel, Cloudflare, Firebase, Supabase, WordPress and more, each treated with the depth that platform deserves rather than a lowest-common-denominator scan.

Code

Code

Where your source and CI live. Secrets, supply-chain risk and reachable CVEs.

Hosts & build platforms

Hosts & build platforms

Where your sites and apps actually serve. Posture, headers and deploy hygiene.

Cloud & data

Cloud & data

Where your data and services run. Misconfiguration, IAM hygiene and exposure.

Cloudflarelive

Zone-level posture, WAF observability and edge-rule audits for every Cloudflare account you connect.

AWSsoon

Account-wide posture, IAM hygiene and S3 exposure checks. Connector in private beta.

Azuresoon

Subscription posture and identity-hygiene checks. Connector in design.

DigitalOceansoon

Droplet and Spaces posture checks. Coming next.

Firebaselive

Project-wide rules, Storage and Hosting posture for every Firebase project you connect.

Supabaselive

RLS, storage and exposed-key checks across the Supabase projects you ship — without a key in your dashboard.

Content & sites

Content & sites

WordPress and the platforms that publish the public web. Plugins, themes, integrity.

Builder platforms

Builder platforms

The places people prototype and ship now. Vibe-coded apps deserve real security.

Replitlive

Project secret scanning and exposed-key checks for the way you actually build on Replit.

Linearsoon

Push triaged findings into the Linear projects your team already plans against.

Integrations FAQ

Questions, answered

How long does an integration take to set up?
Most platforms take under five minutes. You authorise the connector through the platform’s OAuth flow (or paste an API token where OAuth is not available), choose what to include, and Argus starts producing findings within minutes.
What does Argus need access to?
Read-only access for discovery and findings. Argus only requests the scopes needed for the specific signals each integration produces, and the requested scopes are listed on the per-integration page so you can review before authorising.
What about platforms not listed here?
Some platforms are deliberately out of scope (Argus is not an endpoint, network or identity tool). Others are on the roadmap — the "coming soon" cards are the ones already in design or private beta. Tell us what you need from /contact and we will tell you honestly whether and when it will land.
Can I run external scans on a target I do not own?
No. Argus requires evidence of ownership before running any active probing against a target — typically a DNS TXT record or a file at a well-known path. Black-box external scanning is otherwise indistinguishable from reconnaissance, and we treat it that way.
Do integrations work across customer accounts (for agencies)?
Yes. A single Argus organisation can hold any number of connected platforms, with per-client scoping so each client only sees their own findings. Pricing is metered on AI usage, not seat or site count.

Connect your first target in minutes.

OAuth in, findings out. No agents to babysit, no keys in your dashboard.