Skip to main content
Namespace provides flexible compute resources through a comprehensive selection of machine shapes designed to meet diverse workload requirements. Machine shapes define the CPU, memory, and storage resources allocated to your compute instances, allowing you to optimize performance and cost for your specific use cases.

​
Understanding Machine Shapes

Machine shapes in Namespace follow a simple AxB notation format, where A represents the number of virtual CPUs (vCPUs) and B represents the amount of memory in gigabytes (GB). For example, a 4x16 machine shape provides 4 vCPUs and 16 GB of RAM. This standardized format makes it easy to identify and select the appropriate resources for your workload, whether you’re running lightweight development tasks or memory-intensive applications.

​
Available Configurations

Each platform supports its own shape configurations, and the following tables list the most common shapes for each. All prices are per minute.
The per-minute price for Linux AMD64 instances and Linux ARM64 instances is identical.

​
Storage Allocation

Namespace automatically provisions ephemeral storage based on your selected machine shape. The storage allocation scales dynamically to ensure adequate disk space for your workload. The disk space for an instance is calculated using the following formula:
disk_size=32GB+max⁡(vCPU_count,RAM_GB/2)×8GB\text{disk\_size} = 32GB + \max(\text{vCPU\_count}, \text{RAM\_GB} / 2) \times 8GB

​
Non-Standard shapes

Namespace allows you to freely choose your shape configuration to best match your workflow requirements. For example, you can grow your memory allocation to 64GB while keeping the vCPU count at 4, forming a 4x64 shape. Standard shapes for Linux and Windows are multiples of 1 vCPU and 2GB RAM. For example: 1x2 (minimum), 2x4 (tiny), 4x8 (small), 8x16 (medium), 16x32 (large), 32x64 (maximum). Non-standard shapes consume the per-minute cost of the smallest standard shape that contains them. When billing an instance, Namespace calculates how many 1 vCPU x 2GB RAM units were consumed for that instance: unit_count=max⁡(vCPU_count,RAM_GB/2)\text{unit\_count} = \max(\text{vCPU\_count}, \text{RAM\_GB} / 2) Contact support@namespace.so if you have special shape requirements.

​
High-Memory and High-CPU Instances

For workloads requiring exceptional memory capacity like data processing and analytics pipelines, Namespace offers extended memory configurations:
  • 80 GB, 96 GB, 112 GB, 128 GB - Extended memory options
  • 256 GB, 384 GB, 512 GB - High-memory instances for specialized workloads
Note: High-memory and high-CPU instances require special access and may not be available on all subscription plans. Contact support@namespace.so to request access for your workspace. High-CPU (64 vCPU) instances have an additional 1.25x unit multiplier.

​
Billing and Cost Optimization

Machine shapes are billed on a per-minute basis with a one-minute minimum charge. For more details on the usage and billing calculation, check out Billing and Limits →. When trying to optimize performance and cost, picking the right shape is an important step:
  • Larger shapes may shorten your workflow duration.
  • Smaller shapes may be cheaper if your current machine type is oversized.
  • Using standard shapes (ratio of 1vCPU : 2GB RAM) leads to better cost efficiency.
For assistance with machine shape selection, high-memory or high-CPU instance access, or performance optimization, reach out to our support team.

​
Unit minute accounting

We account for a minimum of 1 minute for each instance, but round the next 15 seconds down. For example, 30 seconds of usage is 1 billable minute, 70 seconds is 1 billable minute, and 150 seconds are billed as 3 minutes. Jobs that run on Windows or macOS consume minutes at a higher rate than jobs on Linux. Unit minutes usage per shape and platform can be found above. An instance is only accounted for the time it runs a job. Instances that never pick up a job, such as runners whose job was cancelled or picked up by another matching runner, consume no unit minutes. See Billing and Limits → for details.
Last modified on September 23, 2026