Background agents with a full dev environment, and no bill while they wait
Promigence gives background agents a full development environment forked from a verified snapshot: your repository, its services and its build, ready when the agent starts. A long-running agent can pause while it waits on a person, a queue or a timer, and paused time is not billed.
Who this is for: Platform teams building internal background agents, and teams running vendor coding agents on their own pool.
forks in six hours, zero failures
warm fork on the box
at 200 concurrent, all served
Three things that are true of almost every team doing this
A real task needs the whole dev environment
Databases, queues and a built frontend, not just a repository. Setting that up for every task takes longer than the task.
Agents spend most of their time waiting
On the model, on a tool, on a reviewer. A sandbox billed for every second of that wait costs more than the work it does.
Secrets and network access need a boundary
An agent with production-like access must reach the hosts it should and nothing else, with credentials that are not baked into the environment.
With Promigence underneath
One snapshot of the full environment
Set up the services and the build once, verify them, and fork the finished environment for each agent run.
Pause while the agent waits
Set an idle rule and a sandbox pauses itself when nothing is happening, then wakes on the next request. Paused time is not billed.
Allow-listed network and secrets at run time
An outbound allow-list, with every refused host recorded, and secrets injected at run time, never stored in the snapshot your build produces.
# Store a credential once; it is injected at run time, never stored in the snapshot your build produces
promigence secrets set GITHUB_TOKEN --from-env GITHUB_TOKEN
# Fork the environment and let it pause itself when idle
promigence fork --snapshot devenv@9b0d3f1 --count 1 --cap 1
promigence sandbox autopause "$SANDBOX" --after 30s
# What it 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.