VPSGit M4 Core
M4 · 16GB · 256GB, ideal for single Xcode builds, automated testing, and everyday remote development.
$19.5/day
3 plans · 4 terms
Compare plans and fixed prices, then rent a cloud Mac
Every plan includes a dedicated Apple Silicon physical node with no shared compute resources and no virtualization. This catalog includes only VPSGit M4 Core, VPSGit M4 Plus, and VPSGit M4 Pro, starting at $19.5/day.
Delivery-ready
Live console confirmation
Available plans
VPSGit M4 Plus
M4 · 24GB · 512GB, ideal for continuous builds, cache reuse, and medium-scale MLX experiments.
$41.7/day
VPSGit M4 Pro
M4 Pro · 64GB · 2TB, ideal for memory-intensive inference, parallel pipelines, and large media workloads.
$60.9/day
Dedicated physical node
6 locations
Billed in USD
Delivered in about 4 minutes
Fixed-term pricing
Three plans without guessing your bill from a vague starting price
Each card shows daily, weekly, monthly, and quarterly pricing. Selecting a model carries that plan into checkout; available locations and inventory are confirmed live by the console.
VPSGit M4 Core
Ideal for temporary debugging, single Xcode builds, automated testing, and routine remote development.
$19.5 /day
ChipM4
Unified memory16GB
Local SSD256GB
Weekly$52.6
Monthly$97.4
Quarterly$264.9
VPSGit M4 Plus
Ideal for cache-heavy continuous builds, team development, and medium-scale MLX inference workloads.
$41.7 /day
ChipM4
Unified memory24GB
Local SSD512GB
Weekly$112.5
Monthly$208.4
Quarterly$566.8
VPSGit M4 Pro
Ideal for 64GB unified-memory workloads, parallel pipelines, large MLX models, and media processing.
$60.9 /day
ChipM4 Pro
Unified memory64GB
Local SSD2TB
Weekly$164.4
Monthly$304.4
Quarterly$828
Hardware comparison
Choose by working set, concurrency, and storage needs
Memory determines how many build processes or model weights you can keep active at once; SSD capacity determines local space for dependency caches, model files, and media assets. All six locations are available across the three plans.
| Comparison | VPSGit M4 Core | VPSGit M4 Plus | VPSGit M4 Pro |
|---|---|---|---|
| Chip | M4 | M4 | M4 Pro |
| Unified memory | 16GB | 24GB | 64GB |
| Local SSD | 256GB | 512GB | 2TB |
| Best for | Single Xcode builds, single-project testing, remote development | Continuous builds, larger dependency caches, medium-scale MLX inference | Memory-intensive MLX, parallel builds, media processing, and large working sets |
| Recommended concurrency | Run one heavy build at a time; queue lightweight checks sequentially | Separate build and test queues; limit simultaneous memory-intensive jobs | Isolate concurrency by project or pipeline and monitor unified-memory pressure |
| Available locations | Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, US West | Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, US West | Singapore, Japan (Tokyo), South Korea (Seoul), Hong Kong, US East, US West |
Choose a location based on your developers, code repository, dependency sources, and end users. Catalog combinations can be ordered; live availability is confirmed by the console.
Add-ons
Expand storage or link devices with Thunderbolt 5
Add-ons use the same term as the host. Storage upgrades suit dependency caches, model files, and media assets; Thunderbolt 5 linking is priced per device for workflows that specifically need high-speed connectivity between devices.
+1TB SSD
Expand local space for Xcode caches, model files, proxy media, and build artifacts.
- Daily
- $2.3
- Weekly
- $6.3
- Monthly
- $11.7
- Quarterly
- $31.8
+2TB SSD
Keep multiple model versions, large media projects, or longer-term build caches on hand.
- Daily
- $4.6
- Weekly
- $12.6
- Monthly
- $23.4
- Quarterly
- $63.6
Thunderbolt 5 link (per device)
Choose this only when your workload genuinely needs high-speed device-to-device connectivity; ordinary builds and remote development usually do not require it.
- Daily
- $1.5
- Weekly
- $4.1
- Monthly
- $7.5
- Quarterly
- $20.4
Renting, buying, or sharing resources
Compare procurement time, maintenance effort, and resource boundaries in one table
For tasks lasting days or weeks, delivery speed and exit cost often matter more than hardware ownership. For long-term use, weigh the rental term, purchase cost, and team maintenance time together.
| Comparison dimension | VPSGit rental | Owned hardware | Shared VM |
|---|---|---|---|
| Cost structure | Rent at fixed daily, weekly, monthly, or quarterly prices and choose a term for the task window | Pay upfront for equipment, networking, power, space, and ongoing maintenance | Usually billed by shared-resource tier; verify contention and limits |
| Delivery | After payment confirmation, system, network, and access credentials are configured in about 4 minutes | Requires procurement, delivery, cabling, system installation, and remote-access setup | Usually provisions quickly, but available hardware capability depends on the virtualization platform |
| Dedicated access | Dedicated Apple Silicon physical node, not a VM | Team-owned equipment is used and managed by the team | Compute hosts are shared with other tenants; the platform defines resource boundaries |
| Maintenance effort | VPSGit handles core node operation; your team handles its environment, account boundaries, and backups | The team handles hardware, networking, systems, remote access, and incident response | The platform maintains the infrastructure, but system permissions and hardware capability may be limited |
| Upgrade flexibility | Choose a new model, location, and add-ons for each new term | Upgrades usually require additional or replacement hardware | You can switch platform tiers, but this is not equivalent to a dedicated physical node |
Term selector
Choose a term for the task window instead of guessing long-term usage
Choose a term to see the corresponding recommendation. The four terms do not change the hardware; they change the order coverage period and fixed price.
Daily: temporary debugging and short tasks
Ideal for reproducing a build issue, validating an Xcode toolchain, testing the remote desktop experience, or running short inference jobs. Export artifacts and revoke temporary access before the term ends.
Weekly: sprints and experiment windows
Ideal for a release sprint, Runner scaling, focused testing, or a time-boxed MLX experiment. Freeze the environment on day one and export data on the final day.
Monthly: continuous builds and team development
Ideal for a stable self-hosted Runner, ongoing dependency-cache maintenance, or a team remote development machine. Establish account rotation, cache cleanup, and scheduled backup rules.
Quarterly: stable team resources
Ideal for teams with known users, fixed pipelines, and stable location preferences. Confirm capacity, storage upgrades, handover responsibilities, and migration plans before the term ends.
Billing and payments
All prices are billed in USD
We support USDT-TRC20 and Visa / Mastercard / Amex via Stripe. The checkout backend confirms the gateways available at payment time; orders and renewals both start in the console.
- The host and add-ons use the same term; different billing cycles cannot be mixed.
- Before submitting, the order lists the model, location, term, add-ons, and total due.
- Changing the model or location requires a new order and fresh confirmation of catalog and live availability.
- Before renewal, check which data, account permissions, and build caches still need to be retained.
Order checklist
USD
- Model
- Choose from the three-plan catalog
- Term
- Day / week / month / quarter
- Location
- One of six catalog locations
- Expansion
- SSD or Thunderbolt 5
- Payment
- USDT-TRC20 or bank card
- Delivery
- About 4 minutes after payment confirmation
Plan selection FAQ
Separate concurrency, model, storage, and location decisions
Identify the heaviest resource requirement first, then choose a model. Do not use a longer term to compensate for insufficient memory or storage, and do not choose a location based only on geographic distance.
Which plan should I choose for Xcode build concurrency?
For a single project and one heavy build, start with VPSGit M4 Core. When builds, tests, and dependency-cache tasks run together, choose the 24GB VPSGit M4 Plus. For multiple pipelines or working sets clearly above 24GB, choose the 64GB VPSGit M4 Pro and split queues by project to avoid simultaneous contention between memory-intensive jobs.
How do MLX model sizes map to 16GB, 24GB, and 64GB?
Estimate total memory for model weights, runtime caches, and input batches rather than looking only at model-file size. Use 16GB for small validation tasks; consider 24GB for more context or larger batches; choose 64GB for memory-intensive models, multiple resident processes, or parallel experiments. Monitor memory pressure and swapping after launch, then adjust batch size and concurrency.
When should I add a 1TB or 2TB SSD?
Estimate system files, toolchains, dependency caches, model files, media, and outputs separately, leaving room for cleanup. Choose +1TB SSD when build caches or a model collection exceed the base disk budget; choose +2TB SSD for multiple large model versions, long-running media assets, or caches for multiple projects. Keep important data in a separate backup.
Does a typical CI/CD workflow need Thunderbolt 5 linking?
Usually not. Standard Git pulls, builds, tests, remote desktop sessions, and result transfers do not require device linking. Add Thunderbolt 5 per device only when the workflow explicitly needs high-speed connectivity between multiple devices and the application can use it.
How should I choose among the six locations?
Singapore, Japan (Tokyo), South Korea (Seoul), and Hong Kong cover different Asia-Pacific collaboration zones; US East and US West suit teams, repositories, or service dependencies in those regions. Test network jitter, remote desktop responsiveness, and dependency download paths before ordering. Distance is only one factor—also consider your code repository, artifact storage, and team time zones.
Ready to order
Choose your model, term, and location, then configure your order
All three plans provide dedicated Apple Silicon physical nodes. Rent daily, weekly, monthly, or quarterly; after payment confirmation, delivery takes about 4 minutes.