Your agent tests against your real stack
Run docker compose up and the agent works against the Postgres, Redis and everything else in your compose file. Those services keep running after you close the browser. Docker Engine, compose and sudo come with every terminal, from $39 a month.
From $39 a month · Docker and sudo included · Cancel from the dashboard any time
Catch the bugs before staging does
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 you close the tab, so tomorrow's run in the same terminal starts with its data and caches in place.
Data that outlives the terminal
Mount the database's data folder from your project, and the data stays on your account disk when the terminal and its containers go.
sudo for the rest
Use sudo to install a system package in this terminal, or install tools into the project's home folder to keep them for its next terminals. Ending the terminal removes its system packages.
The details
- Engine
- Docker Engine with the compose plugin; your user is in the docker group
- Where it runs
- In each terminal, an unprivileged system container with nesting on
- Priority
- Docker runs at the lowest CPU and disk priority, so the shell and the agent stay quick during a build
- Network
- Public internet at 50 to 1,000 Mbit per terminal, by size; private ranges and port 25 blocked
- Disk
- Images, volumes and build cache live on the terminal's 40 GB root disk and go when it ends; a bind mount under your project stays on the account disk
- Ports
- Web services on 0.0.0.0 get a preview URL for their terminal
Jobs people run with this
Questions about this
Will my existing docker-compose.yml work?
Yes. Clone the repo and run docker compose up. The file works as it does on a Linux laptop; bind mounts point at paths on your Compute instead of your laptop.
Can I run privileged containers?
No. Containers run inside an unprivileged system container, so workloads that need host kernel modules or raw devices belong on hardware of your own. Databases, caches, queues and web apps run as usual.
Do containers come back after a reboot?
Yes, the ones with a restart policy. After a node reboot the terminal comes back by itself with its images and volumes, and Docker starts every container marked restart: always or unless-stopped. The rest wait for docker compose up.
More of what you get
Your agent tests against your real stack
Pick a size, hand the agent the job and close the tab. Come back to finished work.
Get my ComputeYour first overnight run works, or your money back · Cancel from the dashboard; it runs to the end of the paid month