Max
$169a month
8 agents at once and heavy builds on 8 cores
- vCPU
- 8
- RAM
- 16 GB
- disk
- 200 GB
- Internet
- 200 Mbit
- Terminals at once
- 8
The release ships while you travel
An open-source maintainer hands Claude Code the release on a Max Compute: changelog, tag, binaries for every platform, the container image. The builds finish while the maintainer travels. $169 a month.
From $39 a month · Docker and sudo included · Cancel from the dashboard any time
Releases wait for the maintainer's laptop
Users wait for the fix, and the release needs a changelog, a tag, six builds and an image push. That is an evening at the desk.
On a laptop the builds take every core, and a trip means the release slips a week.
A release from a hotel room
- 18:00
Say go
Open the dashboard on the phone and ask Claude Code to cut v4.2.0.
- 18:05
The agent writes the notes
It reads the merged pull requests and drafts the changelog in the repo.
- 18:10
Builds on 8 vCPU
Binaries for Linux, macOS and Windows and the Docker image build on your Compute while the laptop stays shut.
- 18:25
Publish
Tag pushed, image pushed, release notes drafted for a last read on the phone.
A release without the evening at the desk
Releases on your schedule
Cut a release from anywhere with a browser. The desk is optional.
Builds on real cores
Max's 8 vCPU cross-compile every target while you do something else.
Toolchains that stay installed
Toolchains you install with mise and your registry credentials stay in the project's home folder between releases, away from your everyday laptop.
The whole release, on the record
Read exactly what the agent ran before you announce the release.
The size for this job
Max · $169
8 vCPU and 16 GB build every target and the image without waiting in a queue.
- Compute
- release
- Projects
- /work/lib
- Plan
- Max · 8 vCPU · 16 GB · 200 GB · $169/mo
- Agent
- Claude Code
- Tabs
- 3
- Services
- registry:2
- Runs
- Around the clock, lid closed
Questions about this
Where do signing keys and registry tokens live?
In the project's own home folder on your Compute, out of reach of your other projects' terminals. Use tokens scoped to releases and revoke them in one place.
Does this replace CI?
No, keep CI for tests on every push. Your Compute takes what CI makes awkward: a long release, a human decision halfway, toolchains already installed.
Can it build and push container images?
Yes. Docker Engine is installed; docker build and docker push work as on any Linux server.
What this job uses
More jobs people run
The release ships while you travel
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