Resize computer
Change CPU, RAM, disk, bandwidth, or auto-stop on a running computer.
running. The response reports the values the computer actually accepted, not the ones you asked for: a dimension that failed to apply comes back with its previous value. A computer that runs by the hour follows its own rules: see A computer that runs by the hour.
Path parameters
Body parameters
vcpus and mem_gb together, as on create: small, medium, large, xl, or 2xl. A vcpus or mem_gb sent beside it wins. Any other value returns 400 with code: "INVALID_SIZE". Omitted leaves both alone.0.5, 1, 2, 4, 6, 8, or 16, as a JSON number. Any other value returns 400. Growth past 6 (XL) returns 403 with code: "CONTACT_US_FOR_SIZE" unless Orgo has set your account up for computers past XL. On an account that is, a value above 8, the per-computer cap, returns 403 with code: "PER_COMPUTER_CPU_CAP". Growth past what the account’s vCPU pool leaves this computer returns 403 with code: "VCPU_ADDON" and max_cpu. A computer keeps the vCPU threads it booted with until it restarts, and a change past them fails in results until you restart it: GET /computers/{id}/resize reports them as vcpu_threads. Sending the current value changes nothing. Omitted leaves CPU alone.4, 8, 16, or 32, as a JSON number. Growth to 64 returns 403 with code: "CONTACT_US_FOR_SIZE" unless Orgo has set your account up for computers past XL. Any other value returns 400. On an account that is set up past XL, a resize still tops out at the host’s boot-memory ceiling, 32 GB by default: 64 returns 400 unless the fleet is configured above that ceiling, so a 64 GB computer is otherwise reachable only at create time. A value above what your other computers leave of the account’s total RAM returns 403. Shrinking a Linux computer below what it is using returns 409 with code: "RAM_IN_USE". Omitted leaves RAM alone.400. A value below 1 or above this computer’s ceiling also returns 400, with max_disk_gb in the body. Omitted leaves the disk alone. Call GET /computers/{id}/resize to read the ceiling first.400. 0 is accepted but leaves the cap unchanged. Omitted leaves the cap alone.0 means always-on. Omitted leaves the current setting alone. This is applied separately from the four hardware dimensions and is not reflected in results. Orgo does not check the value before resizing: a value the host rejects, such as a negative number or more than 43200 (30 days), returns 500 after any hardware change has already applied.Response
Returns the effective configuration after the resize attempt.true when the computer’s ports or VNC password changed. Re-fetch the computer’s connection details before reconnecting.true when the resize restarted the computer, false when it applied live. null when the host does not report it.api_port, novnc_port, vnc_password, ssh_host_port, or ip. Empty when nothing changed or the host does not report changes.C: was extended to fill it. { "status": "resized" | "noop" | "blocked" | "pending" | "error", "detail": string }. pending means Orgo is still extending it in the background. Absent otherwise.vcpus or mem_gb changed: true, since a GPU computer restarts for that change. Absent otherwise.restart_required: what the new size costs: monthly_usd, yearly_usd, hourly_usd, and lines, one per part. Shown, not charged.{ "dimension": "vcpus" | "mem_mb" | "disk_gb" | "bandwidth_mbps", "requested": number, "applied": number, "ok": boolean, "error"?: string }. This is an array, not an object keyed by dimension. Iterate it and switch on dimension. A dimension sent at its current value has no entry. Absent when the request included no hardware dimension.true when at least one dimension failed, false otherwise. It is true on both 207 and 422, so use the HTTP status to tell a mixed result from a total failure. Absent when the request included no hardware dimension.Status codes
200: every requested dimension applied207: some dimensions applied and others failed (checkresults)422: every requested dimension failed
Example
Response
Errors
VCPU_ADDON, RAM_ADDON, or DISK_QUOTA_EXCEEDED refusal that more room on the plan would clear also carries short (vcpu, ram_gb, disk_gb), monthly_usd, and can_add_room. The workspace owner, signed in or with an account-wide key that has Billing write, also gets next: the calls that price the room, add it, and resize again. Anyone else gets a hint instead.
A computer that runs by the hour
A running hourly Linux computer, on a paid plan or an account Orgo has set to pay from credits, changes itsvcpus and mem_gb to any size sold by the hour, and its rate changes from that moment. A prepaid run is held again at the new rate. Windows, GPU, trial and Bops hourly computers keep their size (409 COMPUTE_HARDWARE_PINNED).
- Its disk, bandwidth and auto-stop stay. A different
disk_size_gbreturns400withcode: "HOURLY_DISK_FIXED", andbandwidth_limit_mbpsorauto_stop_minutesreturns400withcode: "NOT_RESIZABLE". - A size not sold by the hour returns
400withcode: "HOURLY_SIZE_UNAVAILABLE"and thesizesit can take. - A higher rate spends the owner’s credit, so only the workspace owner may ask for one, signed in or with an account-wide key that has Billing write. Anyone else gets
403withcode: "HOURLY_NEEDS_BILLING". A lower rate needs only write access. - A higher rate needs credit for an hour at it plus an hour of the owner’s other hourly computers. With a prepay, it needs what the rest of the run costs at the new rate past what is held, plus that hour. Short, it returns
402withcode: "INSUFFICIENT_COMPUTE_CREDIT",running_usd_per_hour,stopped_usd_per_hour,credit_usdandcredit_floor_usd.
running_usd_per_hour and stopped_usd_per_hour (the new rates), and prepaid_until and prepaid_cents.
Read the ceilings before resizing
GET /computers/{id}/resize returns this computer’s headroom, so you can size a request before making it. It takes the same path parameter and no body.
disk_size_gb this computer can be resized to. It is the plan’s base plus whatever add-on storage the owner’s other computers have not already claimed, up to hard_max_disk_gb.300, unless Orgo raised it for the account, up to 1000.mem_gb this computer can be resized to, already bounded by the live-resize limit and by what the owner’s other computers leave of the account’s total RAM.vcpus this computer can be resized to: what the account’s vCPU pool leaves it beside the owner’s other computers, up to the per-computer limit, and never below what it has now.8, or lower when your plan is a custom one that sets its own. No add-on lifts it.6 (XL) and hard_max_cpu, or hard_max_cpu itself when past_xl_allowed is true. Past it, the PATCH returns CONTACT_US_FOR_SIZE.32 (XL) and hard_max_ram_gb, or hard_max_ram_gb itself when past_xl_allowed is true.true when Orgo has set the workspace owner’s account up for computers past XL (more than 6 vCPU or 32 GB RAM).vcpus a resize reaches before the computer restarts. A change past it fails in results. Absent when the host cannot say, for example when the computer is not running.true when a mem_gb change applies without restarting the computer. Absent when the host cannot say, for example when the computer is not running.200 with a different shape: resizable: false, reason, code (COMPUTE_HARDWARE_PINNED with pinned_by for the billing case), and current_disk_gb, max_disk_gb, max_ram_gb, and max_cpu all set to its current size.
A computer that runs by the hour and can change size answers without base_disk_gb, blocks, add_on_gb, max_bandwidth_mbps, addon_ram_gb, and addon_vcpu, with max_disk_gb at its current disk, and adds hourly: running_usd_per_hour, stopped_usd_per_hour, may_spend (whether you may pick a higher rate), credit_usd (only when may_spend), prepaid_until, prepaid_cents, and sizes, each with cpu, ram_gb, its two rates and, when may_spend, credit_floor_usd.
Authorizations
Body
New vCPU count. Omitted, the CPU is left alone. Growth past 6 (XL) returns 403 (CONTACT_US_FOR_SIZE) unless Orgo has set your account up for computers past XL; on such an account, above 8 returns 403 (PER_COMPUTER_CPU_CAP). A live change past the vCPU threads the computer booted with (vcpu_threads) needs a restart first. Capped by the workspace owner's plan; call GET /computers/{id}/resize for the ceiling.
0.5, 1, 2, 4, 6, 8, 16 New RAM in GB. Omitted, the RAM is left alone. Growth to 64 returns 403 (CONTACT_US_FOR_SIZE) unless Orgo has set your account up for computers past XL. On such an account a resize still tops out at the host's boot-memory ceiling, 32 GB by default: 64 returns 400 unless the fleet is configured above that ceiling, so a 64 GB computer is otherwise reachable only at create time. Above your per-computer ceiling, or more than your other computers leave in the account's RAM pool, returns 403. Call GET /computers/{id}/resize for the ceiling.
4, 8, 16, 32 Idle minutes before the computer suspends itself. 0 means always-on. Omitted, the setting is left alone. Applied separately from the hardware dimensions and not reflected in results. Orgo does not check the value first: a value the host rejects, such as a negative number or more than 43200 (30 days), returns 500 after any hardware change has already applied.
Response
Every requested dimension applied
The effective configuration after the resize attempt. A dimension that failed to apply comes back with its previous value.