islo
DocsBlogSign inStart an agent →

Alert fires. Agent investigates.

Alert agents investigate incidents with access to the relevant logs, metrics, code, and services, then report the cause or open a fix.

Connect PagerDuty or your monitoring stack. Agents trace errors, inspect logs and metrics, and post findings to Slack or open a fix PR.

Build your first autonomous agent →Learn more
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

Elevated 5xx on checkout API

✓load incident + logs
▸trace 5xx on stack
○post findings
agent
incidents.get("checkout-5xx")
$PD_TOKENplaceholder only
islo gateway
Bearer $PD_TOKEN→Bearer ••••••••4f2a
injected at egress · per-request audit
api.pagerduty.com
200 OK
key never touched sandbox memory
allowalert APIcheckout onlyread-only
denyprod writeinvestigation onlyblocked
alert-run · 4 services
logs
checkout API
api:8000
reproducing
postgres:5432
seeded
web:3000
checkout
alert-run
$ islo use alert-run
✓ alert-run resumed

Pay only while it runs.

this use case45m investigation · 2 vCPU / 4 GB → ≈ $0.18

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

From our blog

Agent infrastructure, in depth.

View all →

Common questions

What does the agent do when an alert fires?

Islo spins up or resumes an agent computer, loads logs and metrics, traces the failure, and posts findings to Slack or your incident channel.

Can the agent open a fix PR from an alert?

Yes. When the root cause is in your codebase, the agent can patch the issue, run tests, and open a PR.

Do I have to put production keys inside the agent computer?

No. Gateway policies scope egress and inject credentials at the boundary so keys never enter the agent computer or model context.

Can the agent post its incident findings to Slack?

Yes. Give the agent scoped access to the incident channel and it can post its findings, evidence, and links to any fix pull request.

What if the alert isn't caused by a code bug?

The agent can still report the evidence it found and the most likely source of the incident without changing code or opening a pull request.

Put autonomous agents to work.

Build your first autonomous agent →how it works
© 2026 Islo
DocsBlogLLM contextAGENTS.mdTermsPrivacyRefundsSign in