PLATFORMS Signal 94
Basic build machines with 2 vCPUs and 8 GB memory now available on Pro and Enterprise plans
Pro and Enterprise teams can now select Basic build machines with 2 vCPUs and 8 GB RAM as a fixed-size, cost-effective alternative to the default Elastic build machines.
This gives teams a predictable, lower-cost option for lightweight workloads such as small agents or simple apps that do not need autoscaling. By keeping Hobby accounts on the same 2 vCPU machines under the new name, Vercel unifies the low-tier offering across all plans.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Basic build machines provide 2 vCPUs and 8 GB of memory for Pro and Enterprise projects.
They are priced at $0.0035 per vCPU per minute ($0.007 per build minute), offering a cheaper static-size option.
Projects still default to Elastic build machines, which autoscale and remain recommended for most workloads.
THE READ
What the cluster adds up to.
Pro and Enterprise teams can now select Basic build machines when configuring a project. These machines provide a fixed allocation of 2 vCPUs and 8 GB of memory. Activation is done through team settings, project settings, or the Vercel CLI (version 59.6.0 or later) using the command `vc project update --build-machine basic`. New projects continue to default to Elastic build machines unless explicitly changed.
Adopting Basic build machines requires updating the project configuration; no additional setup steps are needed beyond that selection. The pricing remains at $0.0035 per vCPU per minute, which equals $0.007 per build minute, matching the rate previously applied to Hobby accounts. Because the machine size is static, teams must ensure their build workloads fit within the 2 vCPU and 8 GB limits to avoid performance issues. For workloads that stay within those bounds, the option can reduce costs compared to over-provisioned Elastic instances.
Basic build machines are not appropriate for builds that require more than two virtual CPUs or exceed eight gigabytes of RAM, as they cannot scale beyond those limits. They also lack the automatic scaling feature of Elastic build machines, so sudden spikes in build demand could lead to longer queue times or failures. In such cases, the default Elastic machines remain the recommended choice because they adjust resources dynamically. Teams should evaluate their typical build resource usage before switching to the Basic option.
Hobby accounts continue to run on the same 2 vCPU hardware, now branded as Basic build machines, aligning the low-tier experience across all plan levels. Documentation and the build machines page provide further details on usage and pricing. Contributors to the update include Jon Vincent, Cody Wong, Pranav Kanchi, Caleb Boyd, and Eric Dodds.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER
↗