Get a dedicated Apple Silicon physical node, not a virtual machine. Choose from three plans across five locations, starting at $21.8 per day. Run builds, pipelines, and inference workloads on a configuration that fits.
All prices are in USD. You pay the full price for the selected term, not a prorated daily rate.
Showing daily pricing. Your selected term will also be applied when you place an order.
Try a build first, then decide how long to rent.
$21.8/ day
Ideal for Xcode builds on a single project, command-line development, and short-term release work. Test dependency installation and archiving first, then check your memory and storage headroom.
More room for persistent runners and build caches.
$39.6/ day
Well suited to continuous integration, multiple working directories, and longer development sessions. Extra memory and storage give your toolchains, dependency caches, and build artifacts more room. We don’t set a fixed concurrency limit.
Extra headroom for demanding toolchains and memory-intensive workloads.
$61.6/ day
Built for large projects, multiple toolchains, and MLX experiments. Whether a model fits in memory depends on quantization, context length, and runtime overhead. Test your actual workload first.
Start with a day for a short-lived archive, or compare the full weekly, monthly, and quarterly prices for a persistent pipeline. The table below shows the complete catalog pricing, regardless of the selection above, so you can check your budget.
| Model | Chip / Memory / Storage | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|---|
| Shell M4 | M4 / 16GB / 256GB | $21.8 | $58.8 | $108.9 | $296.2 |
| Shell M4 Plus | M4 / 24GB / 512GB | $39.6 | $107 | $198.1 | $538.8 |
| Shell M4 Pro | M4 Pro / 64GB / 2TB | $61.6 | $166.4 | $308.1 | $838 |
Choose your rental term after estimating how long you’ll need the machine. Switching terms updates the displayed price and your order selection only; it won’t create an order, renew a rental, or charge you.
Every plan includes the storage shown in its specifications. Add SSD capacity if you need more room for dependency caches, build artifacts, or experiment data. For multi-machine workloads using Thunderbolt 5, check the price for each participating machine.
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.4 | $6.6 | $12.2 | $33.2 |
| +2TB SSD | $4.8 | $13.2 | $24.4 | $66.4 |
| Thunderbolt 5 linking (per machine) | $1.3 | $3.5 | $6.4 | $17.4 |
All three plans are available in Singapore, Tokyo, Seoul, Hong Kong, and the US East Coast. “Available” means that the combination can be ordered from the catalog; it isn’t a live inventory count. Check the console for current availability.
| Model | Singapore | Japan (Tokyo) | South Korea (Seoul) | Hong Kong | US East Coast |
|---|---|---|---|---|---|
| Shell M4 | Available | Available | Available | Available | Available |
| Shell M4 Plus | Available | Available | Available | Available | Available |
| Shell M4 Pro | Available | Available | Available | Available | Available |
For interactive desktops, start with round-trip latency between your location and the node. CI workloads also depend on where your repositories, dependency sources, and artifact destinations are. Distance can help narrow down your options, but it can’t replace testing your actual connection.
Round-trip figures from eight cities to the five nodes are not published, so this page does not show an empty grid. Distance only narrows the first choice. A remote desktop and an unattended build do not depend on the same path. After the machine is ready, test SSH and the desktop from your own network.
Here’s an example using Shell M4 Plus in Hong Kong for one week, with a +1TB SSD add-on. The node and add-on are listed separately, and all prices are in USD. This example explains the charges; it isn’t a generated order.
Check the plan and location first, then the start and end times, add-ons, and total due. Changes made partway through a term aren’t covered by this full-term example; check the itemised details in the console.
Check these five points before paying to reduce the chance of having to move data or reconfigure your toolchain after setup. If you’re unsure about anything, write down your questions rather than guessing and choosing a larger plan.
Choose your main use case: builds, CI, testing, or inference. Note your project size, toolchain versions, and expected concurrency. Repository size alone isn’t enough to estimate memory requirements.
Start with where the person using the machine is based, then consider where code, dependencies, and artifacts need to travel. Remote desktop sessions and unattended builds have different latency requirements.
Choose a day, week, month, or quarter, then check the expiry time and time zone shown in your order. Schedule releases and data exports ahead of time rather than waiting until the last minute to back up.
Allow space for Xcode, simulators, DerivedData, archives, and model files as well as source code. Review your cleanup strategy before deciding whether you need a +1TB SSD or +2TB SSD.
Have USDT-TRC20 or a Visa / Mastercard / Amex card ready. For digital asset payments, check the network, address, and amount. For card payments, check the amount in USD.
The prices on this page are catalog prices. Before confirming an order, check the details returned by the console for timing, proration, retention status, and payment gateway.
Your term starts when the node is provisioned, not when you open the pricing page or click the order button. Your order shows the start and end times; check the time zone shown there. For monthly and quarterly terms, use the end time in your order rather than converting the displayed price into a fixed number of hours.
After paying, check your order status and provisioning result. If the payment record and node status don’t match, keep your order number and transaction details and contact support through a console ticket. Don’t pay repeatedly to try to trigger provisioning.
Before renewing, check your current subscription, the new term, and the updated expiry time. If you need to change plans, add storage, or adjust the term, follow the options and pricing shown in the console. This page doesn’t assume a credit for unused time or promise an in-place upgrade without interruption.
The confirmation page should show your current configuration, the new configuration, the amount due, and when the change takes effect. If you can’t verify the details, contact support through a ticket. Don’t calculate an upgrade fee by simply subtracting the list prices for two different terms. Export important files and build configurations before any migration.
Don’t use an expired node as backup storage. This page doesn’t promise a standard number of free retention days. Before expiry, check the retention, recovery, and erasure notices shown for your order, and export any data you need in advance. If the console doesn’t clearly state what will happen, contact support through a ticket.
Back up configurations, certificates, build artifacts, and experiment data outside your repository, and make sure you can restore them. Once a node has been reclaimed and erased, recovering its files isn’t a supported option. A dedicated physical machine doesn’t replace your own backup process.
All three plans and every add-on use the same USD catalog, making it easier to compare orders across locations and billing terms. This page doesn’t convert currencies; check the USD amount shown by the payment gateway before paying.
We support USDT-TRC20 and Visa / Mastercard / Amex via Stripe only. The backend confirms which payment gateways are available. For digital asset payments, check the TRC20 network and your order details. Card payments are handled by Stripe. For billing questions, provide your order number; never send your full card number, password, or private key by email or in a support ticket.
Plan sorted. Ready to get started.
Validate a workload by the day or deploy a persistent pipeline by the quarter—let your real workload guide the decision. Confirm your location, term, and add-ons when you order.