The computers your agents work on.

A device is a real Linux machine your agents own. They check out repos, run code, store files, hit your network - without ever touching your laptop.

Nebula · devices/sf-1

sf-1

Online · us-west · 4 CPU · 16 GB

CPU2.9 of 4 cores
Memory6.6 of 16 GB
Disk9 of 50 GB

Files · /workspace

agent-memo.md4.2 KB2m
pipeline.csv118 KB9m
patch-q3.diff62 KB22m
schema.sql8.4 KB1h

Processes · 3 active

pnpm test --watch

pid 8412 · Code Review

62%412 MB

psql analytics_prod

pid 8419 · Revenue Agent

11%78 MB

git rebase main

pid 8211 · Deploy Bot

0%24 MB

sf-1 · zsh

$ code-review-agent run --pr 512

› Cloning agentlabs-dev/nebula-web…

› Running pnpm install (cached, 1.2s)

› Running pnpm test --watch

248 tests passed

! 2 lint warnings, auto-fixing

$

Not a sandbox.
A coworker's computer.

Devices give your agents the same surface a human teammate would have: a shell, a filesystem, and the network access to do real work.

01

A real computer, not a sandbox

Each device is a full Linux environment your agents can SSH into, run code on, install tools in. They're not glorified eval() boxes; they're machines that ship work.

Full shell · package install · sudo

02

Persistent storage that survives runs

Files an agent writes today are still there tomorrow. Repos stay cloned. Caches stay warm. Memory and disk persist between jobs.

Persistent volumes · git · caches

03

Multiple agents, one device

Hand the same device to a few agents and they share it like a team would: same filesystem, same network, same env. Pass work between them without re-uploading anything.

Shared FS · shared env

04

Scoped network and secrets

Pin devices to a region. Whitelist outbound hosts. Inject secrets without ever exposing them in chat. The agent gets what it needs, nothing else.

Regions · egress allowlist · secret store

From provisioned to producing in three steps.

Stand up the machine, wire it to your agents, and walk away.

01

Provision a device

Pick a region, pick a size. Nebula spins up a Linux box your agents can use within seconds.

Seconds, not minutes

02

Wire it to your agents

Attach the device to one agent or many. They share storage, env, and tools - no per-run setup.

1 device · N agents

03

Let them work

Run jobs on a schedule, on a webhook, or right out of a channel. The device is always there when an agent needs it.

Always-on · region-local

Get your agents
a real computer.

Provision a device in seconds. Pay only for the time your agents actually use.