PR review against a running stack.

Islo reviews pull requests against a running development stack instead of judging the diff alone.

Load related PRs on one computer with your real services, run tests, browse the app, and post review comments without local setup.

agent computer
cpu2 vCPU · 4 GB
disk10 GB SSD
staterunning
a real computer · wired to everything an agent needs
start withand more
onIslo cloudyour cloudyour customers' cloud
task

PRs #482–#489 · billing migration

boot dev env
load PRs · run tests
browse app · verify flows
post review comments
agent
pulls.get(482)
$GITHUB_TOKENplaceholder only
islo gateway
Bearer $GITHUB_TOKENBearer ••••••••4f2a
injected at egress · per-request audit
api.github.com
200 OK
key never touched sandbox memory
allowGitHub PRs#482–#489scoped
denymerge or approvehuman onlyblocked
review-stack · 4 services
postgres:5432
seeded
api:8000
PR branches
web:3000
live
browser
verifying
review-stack
$ islo use review-stack
review-stack resumed

Pay only while it runs.

this use case1h review suite · 2 vCPU / 4 GB → ≈ $0.31

Pay only while the computer runs: CPU + memory + disk. No seat licenses, no idle fees.

CPU time
$0.07/CPU-hour
per core while the env runs
Memory
$0.04/GB-hour
per GB you provision
Storage
$0.0007/GB-hour
per GB of disk
$50 free credits on signup · no card required

Common questions

Can an agent test two related PRs together?

Yes. Load related PRs on the same computer so the agent can test interactions across changes in a single running stack.

Does PR review run my actual dependencies and services?

Yes. The computer runs the same repo, deps, services, browser, config, and env vars as your laptop.

Will the review agent comment directly on GitHub?

Agents post comments and status back to GitHub on the PRs they reviewed.

Can the agent click through the app while reviewing a PR?

Yes. The review computer includes a browser and the running services, so the agent can verify user-visible behavior instead of relying only on unit tests.

Does Islo merge the PR after review?

Islo posts findings and verification evidence back to GitHub. Your repository rules and approval workflow still decide whether the pull request can merge.

Put autonomous agents to work.