AI pentest agents that attack a fresh copy of the target every time
Promigence lets an offensive-security agent fork the same prepared target as many times as it needs, so every exploit attempt starts from an identical, clean state, behind an outbound allow-list.
Who this is for: Teams building AI penetration-testing and offensive-security agents.
warm fork on the box
at 200 concurrent, all served
forks in six hours, zero failures
Three things that are true of almost every team doing this
Every attempt changes the target
An exploit that half-worked leaves the target in a state the next attempt did not expect, and results stop being comparable.
Parallel attempts need parallel targets
Rebuilding the target for each attempt is slow, so attempts run one after another.
An attacking agent must not reach the wrong hosts
An agent with open network access is a liability. It has to reach the target and nothing else.
With Promigence underneath
Fork the prepared target
Build the target once as a verified snapshot and fork a fresh copy per attempt. Each starts identical and isolated.
Many attempts at once
Forks start warm, so dozens of attempts can run side by side from the same starting point.
An outbound allow-list
An outbound allow-list, every refused host recorded, and a sandbox's egress can be cut at once.
promigence snapshot create --image debian:12 \
--setup "apt-get update && apt-get install -y git" \
--setup "git clone https://github.com/your-org/target-app /work/app && git -C /work/app checkout <40-char sha>" \
--setup "cd /work/app && ./provision.sh" --verify "cd /work/app && ./healthcheck.sh" \
--alias target-app --wait --wait-timeout 10m
promigence fork --snapshot target-app --count 20 --cap 5
# What a copy may reach, and every host it was refused
promigence sandbox network "$SANDBOX"
Run your own workload on it, free
Send a repo and the command you run against it, whatever that is: an eval suite, an RL rollout, a CI job, a queue of coding tasks. We build the environment once, run it a thousand times, and send back the timings, the failures and an exact price. Free, once, on your real workload.
- 1,000 runs of your own command, on your own repo
- What each one cost in wall clock, and anything that failed
- Whether a failure was your code or the environment
- An exact price for your real volume
Not ready to hand over a repo? Read the quickstart or check the numbers first.