Fixed configurations and fixed terms
Every plan gives you an entire dedicated physical node—not a virtual machine and never shared with other tenants. Choose a daily, weekly, monthly, or quarterly term, then confirm regional availability and add-ons at checkout.
Pricing matrix
Each figure is the fixed price for its term. No sale prices are displayed, and no term is converted into another. At checkout, the selected model, regional availability, term, and add-ons determine the order.
M4 · 16GB RAM · 256GB SSD
Ideal for single-project development, short builds, automated testing, and lightweight always-on workloads.
M4 · 24GB RAM · 512GB SSD
Built for larger Xcode projects, dependency caches, CI jobs, and parallel development tools.
M4 Pro · 64GB RAM · 2TB SSD
Designed for memory-intensive builds, multiple parallel processes, large local datasets, and AI inference experiments.
| Model | Chip | Memory | SSD | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|---|---|---|
| Forge M4 | M4 | 16GB | 256GB | $20.2 | $54.5 | $100.9 | $274.4 |
| Studio M4 | M4 | 24GB | 512GB | $39.5 | $106.8 | $197.7 | $537.7 |
| Atlas M4 Pro | M4 Pro | 64GB | 2TB | $59.1 | $159.7 | $295.7 | $804.3 |
Regional availability
Forge M4, Studio M4, and Atlas M4 Pro are available in the regions below, subject to live inventory. Plan pricing does not vary by region; the final node options are based on inventory returned when you open the order page.
Add-ons
Add-ons use the same term as the selected host. Do not estimate weekly prices from monthly prices or mix items from different terms; review each item before ordering.
For workloads whose dependency caches, build artifacts, project copies, or medium-sized model files exceed the base capacity.
For larger local datasets, long-term artifact archives, multiple large projects, or workflows that minimize frequent data transfers.
For deployments that explicitly require physical nodes to be paired. Charged per node, it should be selected according to the actual topology and node count.
Invoice breakdown
This example uses the monthly Forge M4 term and monthly +1TB SSD term to illustrate invoice fields. Items remain separate rather than showing an estimated combined total, making each configuration, region, and applicable term easier to verify.
Rent or buy
Choosing a resource type is about more than the headline price. Upfront cost, delivery speed, resource exclusivity, hardware responsibility, and the ability to release resources after a project all affect the real cost of execution.
| Comparison factor | MacWorker rental | Owned hardware | Shared VM |
|---|---|---|---|
| Upfront cost | Pay for the selected term No need to purchase an entire device upfront, making costs easier to align with a specific project timeline. |
Purchase the equipment upfront Hardware, supporting network, and hosting requirements must be funded before work begins, regardless of task duration. |
Usually pay by resource tier Lower initial outlay, but verify whether underlying resources are shared with other tenants. |
| Delivery speed | Order completed in about 4 minutes Select the model, region, and term, then complete USD payment; connection details are provided according to node status. |
Depends on procurement and deployment Requires purchasing, delivery, network access, system configuration, and remote access setup. |
Usually quick to create Creation is fast, but instance performance and underlying resource allocation require separate confirmation. |
| Resource exclusivity | Entire physical node dedicated to you The processor, memory, and local storage are not shared with other tenants; this is a non-virtualized solution. |
Team controls the entire device A high degree of resource control, but the team must manage the physical equipment and access boundaries. |
Underlying resources may be shared Suitable for workloads that can accept a virtualization layer and changing resource scheduling. |
| Hardware operations | MacWorker handles node-side operations The team can focus on the system environment, project dependencies, access permissions, and workload itself. |
Handled by the purchaser Equipment wiring, networking, remote recovery, troubleshooting, and replacement must all be managed internally. |
Platform handles underlying infrastructure Users generally cannot directly control the specific physical equipment or connection topology. |
| Scaling flexibility | Select a new tier and term for each project Add nodes for pipeline peaks and release them when the project ends—no need to hold equipment long term. |
Scaling requires another purchase Disposing of old equipment, managing assets, and deploying new hardware all become part of the team’s workflow. |
Resource-tier changes are usually flexible However, they remain constrained by the virtualization platform’s available specifications and shared-resource policies. |
Fixed terms align easily with release sprints, short-term capacity increases, temporary compatibility testing, build peaks, or rapidly adding dedicated execution nodes.
If your team already has equipment hosting, network access, incident response, and asset-management capabilities—and plans to use the hardware continuously—ownership may be worth evaluating.
If the workload can accept a virtualization layer, shared underlying resources, and a potentially changing runtime environment, a shared instance may meet basic execution needs.
Payments and currency
Page prices and order invoices are recorded in US dollars (USD). The payment gateway available at checkout is determined by the backend response at that step.
Card payments are processed by Stripe, while orders remain billed in US dollars (USD). Verify invoice items, terms, and region before checkout.
Pay using the information provided at checkout, and verify the network and amount due. Order amounts are consistently billed in US dollars (USD).
Ready to order
Use memory and base SSD capacity to select a model, then check live inventory in Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, or US East. Choose a daily, weekly, monthly, or quarterly term, then add options based on data volume and pairing needs. After USD payment, connection details are provided according to the actual node status.