Your whole compose file, running next to the agent
Docker Engine with the compose plugin and sudo on every box, with 50 to 200 GB of disk by plan. The agent tests against real services, and they keep running after you leave. From $5 a month.
From $5 a month · Docker and sudo included · Cancel from the dashboard any time
What Docker on the box gets you
Real services, real tests
The agent runs migrations and integration tests against the databases your app actually uses.
Warm by morning
Containers keep running after the tab closes, so the next run starts with data and caches in place.
Disk that fits images
50, 100 or 200 GB by plan, for images, volumes, seed dumps and build cache.
sudo for the rest
apt install whatever the project needs. It is your box.
The details
- Engine
- Docker 29 with compose 5; your user is in the docker group
- Where it runs
- Inside your box, an unprivileged system container with nesting on
- Network
- Public internet at 50, 100 or 200 Mbit by plan; private ranges and port 25 blocked
- Disk
- Images and volumes share the plan's 50, 100 or 200 GB
- Ports
- Web services on 0.0.0.0 get a preview URL; anything else over SSH forwarding
Jobs people run with this
Questions about this
Will my existing docker-compose.yml work?
Clone the repo and run docker compose up. The file works as it does on a Linux laptop; bind mounts point at paths on the box instead of your laptop.
Can I run privileged containers?
Containers run inside an unprivileged box, so workloads that need host kernel modules or raw devices belong on a machine of their own. Databases, caches, queues and web apps run as usual.
Do containers come back after a reboot?
Images and volumes stay. Containers with a restart policy start again when the box does.
Your whole compose file, running next to the agent
Start a box, hand the agent the job and close the tab. Come back to finished work.
Start my boxCharged when the box starts · Cancel from the dashboard; the box runs to the end of the paid month