04 · Limits

Your hardware is the ceiling. Hitting it is fine.

We built this for heavy, sustained, unattended work. Inside the CPU, RAM and disk of your plan, your usage is unmetered — the only resource carrying an allowance is outbound bandwidth. The authoritative version of everything here is the Acceptable Use Policy.

What each plan gives you

Plan	vCPU	RAM	Disk	Monthly egress
Lite	1	2 GB	10 GB	250 GB
Plus	2	4 GB	20 GB	500 GB
Pro	4	8 GB	40 GB	1 TB
Ultra	6	12 GB	60 GB	2 TB
Max	8	16 GB	80 GB	4 TB

CPU, RAM and disk are physically fixed by the virtual machine. You cannot exceed them, and using every bit of them is allowed. One workstation per customer, unlimited projects on it — a project is just a folder, and disk is a single shared quota you spend however you like.

Explicitly allowed

You never need to ask permission for ordinary heavy development. That expressly includes:

Running one or more AI coding agents, including long-running, unattended, overnight loops.
Compiling, building, and running large test suites and workloads.
Legitimate browser automation and headless-browser work for your own development and testing.
Keeping the machine busy for long stretches, day after day.

If a support person ever tells you to use your machine less because you're using it a lot, they are wrong and you should quote this page at them.

The one allowance: outbound bandwidth

Egress is the single resource the machine itself doesn't cap, so it carries the monthly fair-use figure in the table above. It exists to stop abuse, not to ration development. Package installs, deployments, agent traffic, and normal pushes and pulls will not come close to it — the smallest allowance on the ladder is 250 GB a month.

If you do approach it, we email you first. Normally that means suggesting a larger plan. Throttling and suspension exist in the policy, but they're for deliberate abuse, and a legitimate spike is treated as a legitimate spike. Nobody's box goes dark because a build got chatty.

What you may not run

Short version, in your own words rather than legalese — the AUP is the version that binds:

Crypto mining or equivalent proof-of-work.
Denial-of-service attacks or deliberate flooding.
Bandwidth-shifting services — seedboxes, torrent or media distribution, file-sharing relays, CDNs, VPN or proxy exits for other people.
Spam or bulk unsolicited mail, and open relays.
Pirated software or media, and circumventing copy protection.
Illegal content or activity. CSAM is absolutely prohibited and is reported and terminated immediately, without notice.
Malware, botnet C2, phishing kits, or credential harvesters aimed at others.
Breaking out of your machine toward the host, our infrastructure, or another customer — and attacking or probing us. You may run security tooling against systems you own or are authorized to test; you may not point it at us or at third parties.
Sharing one workstation between several people to avoid paying for seats. Using your own box from your laptop, your desktop and your phone is entirely fine — that's the product. Team use runs on a separate signed agreement.
Reselling your workstation as a service without written permission.

Unauthorized scraping is on that list too, in the specific sense of scraping that breaks a target's terms or the law. Automation against systems you own or are authorized to reach is normal work and is fine.

If something goes wrong

The escalation ladder in the AUP is deliberately gradual: we contact you, then throttle, then suspend while we investigate, and termination is the last step, reserved for serious or repeated abuse. The exception is content like CSAM, which is immediate and unconditional.