Starting at $20.2/day . Rent an entire dedicated physical machine, not a virtual machine. Choose a billing term to match your project timeline. All prices are in USD.
Both plans include SSH and VNC access. Start by choosing the memory and storage you need, then select a location and billing term. Add-ons are priced separately.
Start with daily billing for short-term testing, or compare weekly, monthly, and quarterly terms for ongoing development. Prices below are for the full term, not a daily equivalent. Switching terms updates both plan cards, and the complete price list stays visible for easy comparison.
Showing daily pricing. See each plan card for prices on other terms.
Single-app builds and short regression tests
$20.2/day
A good fit for building, testing, and archiving a single project. Budget for dependency caches, build artifacts, and project files—not just the repository—to avoid running short on disk space.
Available locations: Singapore / Tokyo / Seoul / Hong Kong
Desktop debugging and multitasking
$39.2/day
Well suited to multi-target projects, parallel simulators, and VNC desktop debugging. More memory and storage than the entry plan support more complex development environments, but test your project to determine the right concurrency level.
Available locations: Singapore / Tokyo / Seoul / Hong Kong
Availability labels indicate that these configurations are generally orderable in the catalog. Check the console for real-time availability when placing your order. The buttons above only change the displayed prices; confirm your billing term in the order configuration.
| Plan details | MetalBench 16 | MetalBench 24 |
|---|---|---|
| Chip | M4 | M4 |
| Memory | 16GB RAM | 24GB RAM |
| Storage | 256GB SSD | 512GB SSD |
| Daily | $20.2/day | $39.2/day |
| Weekly | $54.6/week | $105.8/week |
| Monthly | $101.2/month | $195.9/month |
| Quarterly | $275.3/quarter | $532.8/quarter |
| Resource allocation | Entire dedicated physical machine | Entire dedicated physical machine |
| Remote access | SSH command line and VNC desktop | SSH command line and VNC desktop |
Plan prices exclude the add-ons below. Check actual usage across source code, toolchains, simulators, caches, and build artifacts before deciding whether to upgrade. More SSD storage adds capacity, not unified memory, and is not a substitute for a higher-memory plan.
| Add-on | Daily | Weekly | Monthly | Quarterly |
|---|---|---|---|---|
| +1TB SSD | $2.4/day | $6.5/week | $12.1/month | $32.9/quarter |
| +2TB SSD | $4.8/day | $13/week | $24.2/month | $65.8/quarter |
| Thunderbolt 5 connection (per machine) | $1.1/day | $3/week | $5.5/month | $15/quarter |
If build caches need frequent clearing or model files won't fit, check disk usage first. If simulators and compiler processes are competing for memory, check memory pressure. More storage won't solve a memory bottleneck, and it doesn't guarantee faster builds.
Thunderbolt 5 connectivity supports multi-machine workflows; it does not automatically distribute your application across machines. Before ordering multiple machines, share how many you need, how data will move, and how tasks will be split so you can confirm your app and storage workflow can make use of the connection.
To estimate your order, use the plan and add-on prices for the same billing term. Confirm the selected quantity, configuration, term, and total due at checkout.
Recommendations are not performance guarantees. Run a complete test with your actual repository, dependencies, and dataset. Track build times, memory pressure, and peak storage use before increasing concurrency or extending your rental. Getting your workload running comes before committing to a longer term.
| Workload | Recommended plan | Recommended term | Why this plan and what to test |
|---|---|---|---|
| Light builds | MetalBench 16 M4 · 16GB · 256GB | Test daily first; compare weekly for ongoing tasks | A fit for single-app CI and simulator regression tests. Run one clean build and one cached build, then check build times and disk growth for both. |
| Everyday development | MetalBench 24 M4 · 24GB · 512GB | Monthly; consider quarterly for steady, long-running workloads | A fit for multi-target projects, parallel simulators, and VNC desktop debugging. Increase concurrency gradually and check responsiveness and test stability—don't estimate speed based on memory alone. |
| LLM inference experiments | MetalBench 24 +2TB SSD M4 · 24GB · 512GB | Test models daily; consider quarterly for ongoing experiments | Suitable for MLX experiments with quantized 7B–13B models. Check the quantization format, context length, and runtime overhead first. The extra storage holds models and datasets; loading them still depends on memory requirements. |
Note memory pressure, disk usage, and the number of tasks running at once. Separate one-time dependency installs from everyday incremental builds so a single peak doesn't skew your estimate for the whole rental.
SSH may be enough if pipeline logs are all you need. Keep VNC if you need to inspect the UI, simulators, or failures firsthand. Desktop responsiveness also depends on your network route to the machine.
A short acceptance test, a release push, and ongoing development call for different rental terms. Include time for backups, exporting artifacts, and moving your environment—not just build time.
Compare delivery time, resource ownership, and the cost of changing your setup. A dedicated physical machine suits workloads that need a controlled toolchain, remote desktop, and a complete development environment. Local hardware still makes sense for offline work or workflows that rely on nearby peripherals.
| What to compare | Rent a dedicated physical Mac | Buy hardware | Shared VM |
|---|---|---|---|
| Cost structure | Rent by the day; pay for your selected term and add-ons | Pay upfront for hardware, then cover depreciation, power, and idle time | May have a lower starting price; check for resource contention and plan limits |
| Time to get started | Typically about 15 minutes; check progress in the console | Purchasing and delivery can take days, plus environment setup | Usually available immediately, depending on the service |
| Resource exclusivity | An entire physical machine; CPU, memory, and storage aren't shared with other tenants | Your own physical device, with access managed by you | Shares a host with other users; isolation depends on the service |
| Upgrade flexibility | Request a plan change or more storage; confirm migration steps and costs first | Changing the configuration may require replacing or adding hardware | Options are limited by the host and service plan |
| Connectivity | Connect over SSH or VNC; a working internet connection is required | Use locally; configure remote access yourself if needed | Connect over the internet; check desktop and device support separately |
| Best suited to | Release work, remote development, isolated build environments, and model experiments | A permanent desk setup, offline work, and workflows with local peripherals | Workloads that suit virtualization and can tolerate sharing a host |
Don't decide based only on a single build time. Factor in environment setup, debugging failures, exporting artifacts, and idle time. This table compares usage models; it doesn't make up prices or benchmark scores for other services.
Choose from four Asia-Pacific locations: Singapore, Tokyo, Seoul, and Hong Kong. Both plans are available in every location. Compare actual network connectivity, not just distance—desktop performance can vary across providers within the same city.
| Plan | Singapore | Tokyo | Seoul | Hong Kong |
|---|---|---|---|---|
| MetalBench 16 | Available | Available | Available | Available |
| MetalBench 24 | Available | Available | Available | Available |
This is the current product catalog, not a timestamped inventory feed. Check the console for real-time availability. Nodes run year-round, 365 days a year. For SSH builds, prioritize connection stability; for VNC, test interactive latency too.
Plan cards show catalog prices; the order confirmation page lists the charges for your selected configuration. Before paying, check the plan, location, term, add-ons, and quantity. For issues with an existing machine, submit a support ticket through the console so it can be linked to your order and instance.
We accept USDT-TRC20 and Visa, Mastercard, or Amex credit cards via Stripe. All prices are in USD. Available payment gateways are determined by the backend at checkout. If paying with USDT, verify the network, order amount, and payment details. Transfers on other networks won't count as the same payment.
Choose based on how long you'll need the machine, not just how long commands take to run. Daily billing works for short tests; for ongoing development, compare the full weekly, monthly, and quarterly prices. The price list shows each term's actual price—not a daily equivalent—and doesn't default to a long-term commitment. Before renewing, check your remaining tasks and the expiry date.
No. +1TB SSD, +2TB SSD, and Thunderbolt 5 connectivity are separate add-ons. Thunderbolt 5 is priced per machine. Compare catalog prices for the same billing term and check the quantity you need. Don't add a daily add-on price to a monthly plan price and treat that as the order total; check the full breakdown at checkout.
A transfer record and an order confirmation are different statuses. Blockchain confirmations, payment gateway recognition, and order updates happen in sequence; processing time depends on the transaction, so there is no guaranteed arrival time in minutes. Check your order status in the console after paying. If you need help, include your order number, transaction hash, network, and amount in a support ticket. Don't send another payment to try to speed things up.
Check your instance expiry date and billing details in the console, and renew before the expiry date. Schedule long tests, artifact exports, and backups within your rental term rather than relying on reminders. After submitting payment, check the billing page and the instance's new expiry date. If the status hasn't updated, verify it through a support ticket; initiating a payment doesn't mean the renewal is complete.
You can request a plan change or storage expansion. Include your current instance, target configuration, remaining rental term, and any data you need to keep. Support will confirm the price difference, steps, and migration plan. A plan change doesn't migrate your app automatically, and a machine restart doesn't mean the upgrade is complete. Back up data on the working drive before making changes, and proceed once the plan is confirmed.
Data retention and deletion timelines are governed by the service terms for your order; this page doesn't set a standard retention period. If you need to confirm the timeline before ordering, contact us by email. For an existing instance, ask about the specific arrangement in a support ticket. Treat the expiry date as your deadline for backups and exports—don't rely on post-expiry retention or wait until your instance expires to start migrating.
Check your order and billing records in the console, then submit a support ticket with the billing name, billing entity, order number, and required document fields. Support will confirm which billing documents are available. USD payment records and tax documentation requirements vary by location. Clarify your team's finance requirements before renting; a payment record isn't necessarily a tax invoice in a specific format.
For pre-sales questions, email us at support@metalvnc.com; for existing orders, log in to the console and submit a support ticket. Include your order number and steps to reproduce the issue. Never send passwords, private keys, or full payment card details.
Choose the M4 plan that fits your workload, then confirm the term, location, and add-ons at checkout. Not sure? Tell us about your project size, concurrency needs, and expected rental period.