AI Risk AssessmentShadow-AI discoveryCloud PostureExploit ValidationCI/CDContinuous PlatformReportsIdentity & accessAgentic Trust & Protection Platform
Continuous Platform
One-off scans become ongoing coverage.
Register assets, put them on a schedule, watch for drift, and track risk over time. Scheduled and drift-triggered scans run the same gate → scan → billing path a manual scan does, so quota, concurrency and budget caps all still apply.
3 cadences
daily, weekly or monthly, per asset
Anchored to now
re-arming a schedule never causes a catch-up stampede
Material only
fingerprints normalize CSRF tokens, nonces and timestamps so a dynamic page cannot false-drift
Overview
GET /api/overview · CSV export org-wide
Every asset, its last scan, and what moved
A per-asset rollup: latest scan status, severity counts, the opened and resolved delta against the prior scan, and the schedule it runs on.
Assets
app.acme.com
weekly · 0C 1H 2M · +1 / −3
api.acme.com/v2
daily · drift on · 0C 0H 1M
acme/support-agent
CI webhook · 1C 2H 4M · +2 / −0
Trend, per asset
Schedules require a paid plan
Same billing path
Twelve weeks of one asset
Scheduled runs, and the two that fired because something changed.
drift
drift
week 1 — open 9weekly cadence · trigger_on_change: trueweek 12 — open 2
drift-triggered, out of cycle
scheduled, findings opened
scheduled, nothing new
What continuous means here
01
Assets
An asset is a registered target you monitor. Register it, name it, and remove it when it is gone — removing an asset also drops its CI trigger keys.
02
Schedules
Daily, weekly or monthly per asset, merge-aware: changing the cadence keeps the drift toggle and vice-versa. The next run is anchored to now when re-armed.
03
Drift detection
Between scheduled runs the platform re-fingerprints a URL or API asset, preferring its OpenAPI spec. A material change enqueues an out-of-cycle scan; fetches and re-scans are rate-limited per asset.
Endpoints behind the dashboard.
For repo assets, prefer the CI webhook pathFrom first commit to continuous coverage: one agentic security lifecycle.
It starts with the graph. Everything that follows reads from it, writes back to it, and hands its context to the next step.
Availability
The estate assessment — code, websites, agents, and one-click cloud for AWS, Azure, Google Cloud and Oracle — is live, self-serve and free. Exploit validation is live per scan. Network and detection scan types are enabled per tenant. The eBPF runtime sensor is an Enterprise add-on that detects and never blocks.
Then, on every change
Four things the graph makes possible.
Each of these reads the same estate the steps above built — which is why a change can be judged against what is already true in production.
01
New features deployment test
Test the release that changed, not the whole app again:
- A baseline per target — only what changed is re-covered
- An unchanged commit short-circuits: no scan, no charge
- Recon carryover reuses the learned architecture and endpoints
Live
02
Constrain agents
An AI agent is an identity with permissions, and most have more than anyone intended:
- Excessive-agency and tool-abuse testing
- What the agent’s identity can actually reach, through the graph
- The gap between scoped and reachable is what you constrain
Live
03
Code fix
A finding becomes a change your engineers review, never one we merge:
- A minimal patch as a draft pull request on your own repo
- Located by the identifiers the finding names — vendored and minified files excluded
- Dependency updates proposed per CVE, with VEX decisions exported
Live
04
Prevention and response
The cheapest moment to stop a risk is before it exists:
- The PR gate fails a change that would introduce an attack path
- The GitHub Action gates the build — fail-on critical, high, medium, low, or never
- A ticket in Jira or ServiceNow with the full path attached
PR gate live · runtime response roadmap
Where this does not go
Redthread is a testing tool for staging and source, not a production runtime firewall. The optional eBPF sensor detects and never blocks, kills or quarantines. Real-time endpoint prevention (isolate a host, kill a process, quarantine a file) runs through a connected partner engine — the integration is live, and it activates the moment a partner is connected to your workspace. Admission control and cloud guardrails remain on the roadmap.