UnboundCompute
Console
Overview
Interactive demo · sample data
authorized lab · 3 targets
Request access
RD
Workspace · authorized lab

Overview

An autonomous researcher that learns the boundaries your product trusts — and proves the ones that don't hold, with evidence you can reproduce.

Confirmed
3
findings, all evidenced
Critical / High
2
1 critical · 1 high
Surface reached
20/20
endpoints mapped
Proof rate
100%
zero unverified claims

Active scan

all scans →

vaultkeep.dev
complete · 3 findings proven · 0 false positives
01Recon
20 ep · alice · bob
02Hypothesis
34 leads
03Attack
34 vectors
04Oracle
3 confirmed
05Creative
1 proven

Recent activity


Pickle RCE proven by the creative agent — POST /api/config/import
25 steps
Oracle confirmed IDOR — GET /api/projects/{project_id}
×2
GraphQL introspection enabled — POST /graphql
×2
Scan complete on vaultkeep.dev · 0 false positives
done
Workspace

Scans

Each scan runs the full pipeline against one target — recon to proof — and reports only what it can stand behind.

TargetStatusSurfaceFindingsStarted
vaultkeep.devcomplete20 ep3eval run
staging.acme.devcomplete0 · cleaneval run
Scan · eval run · authorized lab

vaultkeep.dev

20 endpoints mapped · identities alice & bob · 3 findings proven.

01Recon
20 ep · alice · bob
02Hypothesis
34 leads
03Attack
34 vectors
04Oracle
verifying 18/34
05Creative
queued

Live trace

tail -f

Confirmed so far

3

Pickle RCE · /api/config/import
creative
IDOR · /api/projects/{project_id}
oracle
GraphQL introspection · /graphql
oracle
Workspace

Findings

Every finding carries hard evidence — a reproduced request and response, or an out-of-band callback. Nothing here is a guess.

AllCriticalHigh
Workspace

Targets

Authorized scopes. UnboundCompute only ever touches what you allow-list here.

HostScopeIdentitiesLast scan
vaultkeep.devvaultkeep.dev/*alice · bobeval run
staging.acme.devstaging.acme.dev/*user · guesteval run
Workspace

Integrations

Push proven findings where your team already works. Confirmed exploits, not noise.

Slack

Post each confirmed finding to a channel, with severity and a link to the reasoning trace.

● connected

Jira

Open a ticket per finding — pre-filled with repro steps and evidence.

connect →

GitHub

File issues against the right repo, mapped from the affected endpoint.

connect →

Webhook

Stream finding events to any endpoint as signed JSON.

● active

SIEM / Splunk

Forward the evidence log to your SIEM for correlation.

connect →

REST API

Pull scans, findings and proofs programmatically. Token-scoped.

view docs →
Workspace

Settings

Workspace configuration.

Out-of-band callback hostoob.unboundcompute.com
Compute budget / week$250 · hard cap
Destructive actionsdisabled · prove only