From 737a1e04d05603f5e255bdcd4d2809ab78f3ee36 Mon Sep 17 00:00:00 2001 From: Nikita Sharma Date: Tue, 23 Dec 2025 15:32:52 -0600 Subject: [PATCH 1/3] document custom instance types for all container users --- .../2025-12-23-custom-instance-types.mdx | 22 +++++++++++++++++++ .../containers/platform-details/limits.mdx | 21 +++++++++++++++++- .../docs/workers/wrangler/configuration.mdx | 8 ++----- 3 files changed, 44 insertions(+), 7 deletions(-) create mode 100644 src/content/changelog/containers/2025-12-23-custom-instance-types.mdx diff --git a/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx b/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx new file mode 100644 index 000000000000000..5b84e392e133f73 --- /dev/null +++ b/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx @@ -0,0 +1,22 @@ +--- +title: Custom instance types now available for all users +description: Configure custom vCPU, memory, and disk allocations for your container instances +products: + - containers +date: 2025-12-23 +--- + +Custom instance types are now enabled for all users. Previously limited to Enterprise customers, you can now configure specific vCPU, memory, and disk allocations for your container instances instead of using predefined instance types. + +To use a custom instance type, specify the `instance_type` property as an object with `vcpu`, `memory_mib`, and `disk_mb` fields in your Wrangler configuration: + +```toml +[[containers]] +image = "./Dockerfile" +instance_type = { vcpu = 2, memory_mib = 6144, disk_mb = 12000 } +``` + +Individual limits for custom instance types are based on the `standard-4` instance type (4 vCPU, 12 GiB memory, 20 GB disk). You must allocate at least 1 vCPU for custom instance types. For workloads requiring less than 1 vCPU, use the predefined instance types like `lite` or `basic`. + +See the [limits documentation](/containers/platform-details/limits/#custom-instance-types) for the full list of constraints on custom instance types. +See the [getting started guide](/containers/get-started/) to deploy your first Container, diff --git a/src/content/docs/containers/platform-details/limits.mdx b/src/content/docs/containers/platform-details/limits.mdx index e31611766ef888f..18c899686e03928 100644 --- a/src/content/docs/containers/platform-details/limits.mdx +++ b/src/content/docs/containers/platform-details/limits.mdx @@ -14,12 +14,31 @@ Six instance types are currently available: -These are specified using the [`instance_type` property](/workers/wrangler/configuration/#containers) in your Worker's Wrangler configuration file. Looking for larger instances? [Give us feedback here](/containers/beta-info/#feedback-wanted) and tell us what size instances you need, and what you want to use them for. +These are specified using the [`instance_type` property](/workers/wrangler/configuration/#containers) in your Worker's Wrangler configuration file. :::note The `dev` and `standard` instance types are preserved for backward compatibility and are aliases for `lite` and `standard-1`, respectively. ::: +### Custom Instance Types + +In addition to the predefined instance types, you can configure custom instance types by specifying `vcpu`, `memory_mib`, and `disk_mb` values. See the [Wrangler configuration documentation](/workers/wrangler/configuration/#custom-instance-types) for configuration details. + +Custom instance types have the following constraints: + +| Resource | Limit | +| -------------------- | ----------------------------------- | +| Minimum vCPU | 1 | +| Maximum vCPU | 4 | +| Maximum Memory | 12 GiB | +| Maximum Disk | 20 GB | +| Memory to vCPU ratio | Minimum 3 GiB memory per vCPU | +| Disk to Memory ratio | Maximum 2 GB disk per 1 GiB memory | + +For workloads requiring less than 1 vCPU, use the predefined instance types such as `lite` or `basic`. + +Looking for larger instances? [Give us feedback here](/containers/beta-info/#feedback-wanted) and tell us what size instances you need, and what you want to use them for. + ## Limits While in open beta, the following limits are currently in effect: diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx index 40945489a4c6179..dfdb5e67f8d098a 100644 --- a/src/content/docs/workers/wrangler/configuration.mdx +++ b/src/content/docs/workers/wrangler/configuration.mdx @@ -1071,12 +1071,8 @@ new_sqlite_classes = ["MyContainer"] ### Custom Instance Types -:::note -For Enterprise customers only. -::: - -In place of the [named instance types](/containers/platform-details#instance-types), you can set a custom instance type by -individually configuring vCPU, memory, and disk. +In place of the [named instance types](/containers/platform-details/limits/#instance-types), you can set a custom instance type by individually configuring vCPU, memory, and disk. +See the [limits documentation](/containers/platform-details/limits/#custom-instance-types) for constraints on custom instance types. The following options are available: From 7f0b1761c158b9a9d2d37946a1381561a52f353a Mon Sep 17 00:00:00 2001 From: Nikita Sharma <54369599+nikitassharma@users.noreply.github.com> Date: Tue, 23 Dec 2025 15:49:27 -0600 Subject: [PATCH 2/3] Apply suggestions from code review Co-authored-by: Mike Nomitch --- .../changelog/containers/2025-12-23-custom-instance-types.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx b/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx index 5b84e392e133f73..28ab309e9af5ddb 100644 --- a/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx +++ b/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx @@ -1,12 +1,12 @@ --- -title: Custom instance types now available for all users +title: Custom container instance types now available for all users description: Configure custom vCPU, memory, and disk allocations for your container instances products: - containers date: 2025-12-23 --- -Custom instance types are now enabled for all users. Previously limited to Enterprise customers, you can now configure specific vCPU, memory, and disk allocations for your container instances instead of using predefined instance types. +Custom instance types are now enabled for all [Cloudflare Containers](/containers) users. You can now specify specific vCPU, memory, and disk amounts, rather than being limited to pre-defined [instance types](/containers/platform-details/limits/#instance-types). Previously, only select Enterprise customers were able to customize their instance type. To use a custom instance type, specify the `instance_type` property as an object with `vcpu`, `memory_mib`, and `disk_mb` fields in your Wrangler configuration: From 7e7f7e95fcaf69b8e15e2a7db8179fb7a574206d Mon Sep 17 00:00:00 2001 From: Nikita Sharma Date: Mon, 5 Jan 2026 12:15:14 -0600 Subject: [PATCH 3/3] update date for changelog --- ...-instance-types.mdx => 2026-01-05-custom-instance-types.mdx} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename src/content/changelog/containers/{2025-12-23-custom-instance-types.mdx => 2026-01-05-custom-instance-types.mdx} (98%) diff --git a/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx b/src/content/changelog/containers/2026-01-05-custom-instance-types.mdx similarity index 98% rename from src/content/changelog/containers/2025-12-23-custom-instance-types.mdx rename to src/content/changelog/containers/2026-01-05-custom-instance-types.mdx index 28ab309e9af5ddb..392fc525701bd08 100644 --- a/src/content/changelog/containers/2025-12-23-custom-instance-types.mdx +++ b/src/content/changelog/containers/2026-01-05-custom-instance-types.mdx @@ -3,7 +3,7 @@ title: Custom container instance types now available for all users description: Configure custom vCPU, memory, and disk allocations for your container instances products: - containers -date: 2025-12-23 +date: 2026-01-05 --- Custom instance types are now enabled for all [Cloudflare Containers](/containers) users. You can now specify specific vCPU, memory, and disk amounts, rather than being limited to pre-defined [instance types](/containers/platform-details/limits/#instance-types). Previously, only select Enterprise customers were able to customize their instance type.