New features, fixes, and security notices for IBEE Cloud, newest first. Filter by tag to see only what affects you.
November 18, 2026
Public API 0.13.0: no single call wipes a bucket or a registry
The public API manages resources. Files and container images stay on each product’s own endpoint, with the clients that already exist for them: S3 tools at <workspace>.blob.ibeestorage.com for Object Storage, and docker at registry.ibee.ai for Container Registry.
November 15, 2026
Public API 0.11.0: Object Storage and Container Registry are back; Secret Manager and regional load balancers
The public API manages resources. Files, images, secret values and load balancer traffic stay on each product’s own endpoint, with the clients that already exist for them: S3 tools at <workspace>.blob.ibeestorage.com, docker at registry.ibee.ai, and bao or vault at your Secret Manager endpoint. Every call goes through the API gateway to the same portal logic the console uses.
November 12, 2026
Public API 0.10.0: wallet balance and top-ups, and a working VM resize body
Read the wallet. GET /billing/wallet returns the balance of the API token’s organization: paid, promotional and held credit, and the total, as integers in the currency’s minor unit (paise for INR, cents for USD). The wallet belongs to the organization, so every workspace returns the same one. It needs the billing.read scope.
November 4, 2026
Public API 0.9.1: clearer retry keys and errors, and corrections to the reference
No path, method or operation changed. The reference stays at 178 active operations.
- VM delete:
public_ip_actionapplies only to an automatically assigned IP. If the VM’s IP is already a Reserved IP,releaseandreserveare both refused with400. Delete with no body, then release the IP from Reserved IPs to stop its billing. - Backup runs:
triggerisscheduledormanual. Runs started through the API reportmanual, notapi. The run lists return only finished, successful runs; read a run by ID to see one that is queued, running or failed. - Retry keys on networking creates: send the same key and body on every retry. A completed create returns its original answer for 24 hours, even if the plan limit has since been reached. A refused or unsent create leaves the key free to use again. An unknown outcome answers
409 idempotency_in_progresswithRetry-Afteruntil the next retry resolves it. See Retry a networking create. - Errors: the catalog reads now use the same format as other errors:
error,messageandrequest_id, withdetailkept.409answers carry the product’s reason inmessagewhere it’s safe to show.413and502are now documented on every operation, and423on restore cancel. - Paused Object Storage operations:
DELETEon bucket lifecycle rules, CORS rules, notifications and custom domains needsobject-storage.delete, notobject-storage.write.
November 3, 2026
Public API 0.8.0: manual backups and asynchronous backup deletion
Start a backup immediately with POST /compute/cloud-vms/{vm_id}/backups/runs
or POST /compute/gpu-vms/{vm_id}/backups/runs. An enabled backup policy is
required. Send {"requested_by":"api"} to use that policy’s stored billing
catalog, or supply an explicit billing_catalog override. The response includes
the queued run_id; poll the run until it succeeds or fails. Both operations
require vm.write and a workspace_id query parameter.
November 3, 2026
Public API 0.9.0: Object Storage and Container Registry paused, one error format, retry keys on networking creates
Object Storage and Container Registry management are temporarily paused. The 25 Object Storage and 26 Container Registry operations answer 404 with an empty body until they resume. That doesn’t mean a resource was deleted. The portal, S3 file traffic, registry pushes and pulls, and your existing resources are not affected. The active reference has 178 operations. The SDKs and CLI keep their methods and commands for the paused operations.
October 30, 2026
Public API 0.7.1: example fix for the SDK generators
No path, operation, parameter or schema changes. The examples on POST …/backups/disable (cloud and
GPU VMs) now carry the vm_id path parameter and the workspace_id query parameter. Without them the
SDK generators refused the contract (“Example is missing required path parameter”), while the
reference site rendered it. The Python and TypeScript SDKs, the CLI and the Terraform provider are
generated from this version.
October 29, 2026
Public API 0.6.3: two schema corrections found by the client test run
POST /object-storage/credentialslists thepermission_typevalues:admin_rw(default),admin_ro,object_rw,object_ro.GET /block-storage/plans:included_usage.iopsandincluded_usage.throughputare display text such asUp to 10K, not numbers. Clients generated from 0.6.2 could not read the response.
October 29, 2026
Public API 0.7.0: the reference is final; paths are frozen
Every path and operation of 0.6.3 stays as it is. From this version the public API only grows: no path is renamed or removed in a 0.x release.
- Asynchronous operations documented in one place. Every write that returns before it finishes (VM create, delete, power, access, resize, attach and detach; snapshot and backup restores; block volume create, resize and delete; registry create, delete and upgrade) now names its status read and terminal states in its description, and the new Asynchronous operations page explains how to follow them and what to do on a timeout.
- Lists documented as served. The new Lists and paging page gives every list operation’s response shape and paging parameters. Shapes are not changed in this release.
POST …/backups/disable(cloud and GPU VMs) now declares an optional empty JSON body. Send{}: the virtualization engine rejects a request with no body. A fix on the engine side is requested.- Refusal semantics written into the descriptions: deleting an unknown registry repository or artifact
answers
200; a permanently deleted secret or store answers403; a bucket without custom domains answers404on read and400on remove.
October 28, 2026
Public API 0.6.1: every route exact-path and method-matched
Object lock and custom domains work. GET/PUT /object-storage/buckets/{bucket_name}/object-lock and the three custom-domains operations answered 404 from the storage service after 0.6.0 because the gateway forwarded them on a prefix route; they are now routed per operation. Object lock reads answer 404 on a bucket created without lock, and adding a custom domain answers 400 until the hostname CNAMEs to cname_target; both are now documented on the operations.
October 28, 2026
Public API 0.6.2: hourly or monthly VMs through the API
POST /compute/cloud-vms and POST /compute/gpu-vms now name the billing term inside billing_catalog. Hourly pay-as-you-go stays the default. For a plan’s monthly price, send "billing_interval": "MONTHLY" and "committed": true: the first month is reserved from the wallet before the VM is created, and the VM cannot be deleted or resized until the month ends (409 with code VM_COMMITTED, plus paid_until and renews_on). The plan’s billing_catalog from GET /compute/plans does not carry the term itself, so earlier clients that passed it through unchanged always created hourly VMs.
October 27, 2026
Public API reference 0.6.0: the portal’s operations, and only those
The API reference is now 223 operations, lined up with what the portal offers and with what servers.com, Vultr and E2E Networks expose for the same products.
Removed (25). Operations the portal never used and no provider offers: on cloud and GPU VMs, resize-plan, resize-root-disk, mount-guidance/acknowledge, backups/policy/next-run-at and the manual backups/runs POST; the three VM console session operations; POST /cdn/generate-url; PATCH /networking/vpcs/{vpc_id}/subnets/{subnet_id}; the Secret Store PATCH operations on stores, secret values, identities and permissions; POST /container-registry/registries/{registry_id}/empty; and POST /billing/resource-eligibility (no pre-check: every billable create answers 402 with the reason). The block-storage attachments and detach operations, which needed a storage-node name, are gone too; attach volumes from the VM with POST /compute/cloud-vms/{vm_id}/actions/attach-volume.
October 20, 2026
Public API reference 0.5.0: Container Registry
The API reference adds Container Registry: 27 operations under /v1/container-registry for registries, storage plans, registry access tokens, repositories, images, vulnerability findings, SBOMs, and metrics. They need the new container-registry.read and container-registry.write scopes. See Use the API.
October 19, 2026
Public API reference 0.4.1
VM create now lists site_id as required (the API already refused a create without it), VM plan and root-disk resizes accept an optional billing_catalog, and block-storage volumes show the metadata.billing_catalog that volume attach needs.
Public API reference 0.4.0
May 1, 2026
CVE-2026-31431 (CopyFail) mitigation applied to IBEE server images
IBEE has applied security mitigations for CVE-2026-31431 (CopyFail vulnerability) across all supported Linux server images.
The following operating systems now include this protection by default:
