Cloud Mac vs Mac VPS: what's the difference?

A cloud Mac and a Mac VPS both give you remote macOS, but one is a whole physical machine and the other is a virtual machine sharing hardware. That difference shapes performance, GPU access, Xcode behaviour, isolation and cost.

Definitions

The terms are used loosely, so it helps to pin them down.

• Cloud Mac (dedicated). A physical Mac mini or Mac Studio in a hosting facility, assigned to one customer. macOS runs directly on the hardware. You get every core, the full GPU and the whole SSD.
• Mac VPS (virtual). A macOS virtual machine running on a Mac host. The host's CPU, memory and storage are divided between one or more guests. You get a slice, with virtual devices in place of some real ones.

Some offers labelled "macOS VPS" run macOS on non-Apple hardware. Apple's licence does not permit that, and such setups tend to break with updates and lack proper GPU support. This guide only considers macOS virtualised on genuine Apple hardware.

How macOS virtualisation works on Apple hardware

On Apple silicon, macOS virtual machines use Apple's Virtualization framework, which builds on the hypervisor built into macOS. Tools such as UTM, Tart, Parallels Desktop and commercial orchestration platforms are built on top of it. Guests boot quickly, can be cloned from a template, and can be thrown away after a job. That is why virtual macOS is popular for ephemeral CI.

Licensing shapes how far this goes. As we understand Apple's macOS licence, it allows up to two additional copies of macOS to run in virtual machines on each Mac, alongside the host. It also allows a Mac to be leased to a single customer, with a minimum lease period of 24 hours. In practice this means a provider cannot legitimately pack many macOS tenants onto one host the way a Linux VPS host can, and that per-customer rentals carry a 24-hour minimum. Licence terms change between macOS versions, so read the current text if this matters for your project; this is not legal advice.

Performance

Virtualisation on Apple silicon is efficient. CPU-bound work in a well-configured VM runs close to native speed. The differences show up elsewhere:

• Shared resources. If two guests share a host, they share cores, memory bandwidth and SSD throughput. A busy neighbour slows you down.
• Fixed allocations. A VM gets a set number of cores and memory. Memory is often the tighter limit, because the host also needs its share.
• Storage. Virtual disks add a layer between your files and the SSD. For heavy I/O, such as large Xcode builds with DerivedData, the gap can be noticeable.

A dedicated Mac has none of these variables. Build times are repeatable, which makes performance regressions in your own code easier to spot.

GPU and Metal access

This is the largest practical difference. macOS guests do not get direct access to the host GPU. Instead, Apple's Virtualization framework provides a paravirtualised graphics device that exposes Metal to the guest. It is good enough for the desktop and many apps, but it does not deliver the full GPU performance or feature set of the hardware.

That matters for:

• LLM inference with Ollama, llama.cpp or MLX, which rely on Metal for speed.
• GPU rendering, video effects and game engine work.
• Metal-based tests that need to behave as they would on a real device.

If any of these are central to your work, a dedicated Mac is the safer choice. See running Ollama on a Mac mini server for an example of a GPU-dependent workload.

Xcode and Simulator behaviour

Xcode runs in a macOS VM, and compiling, signing and uploading builds generally work. A few things are worth knowing:

• Simulators. iOS Simulator works in VMs, but it competes for the guest's limited memory and GPU. Running several in parallel is where VMs struggle first.
• Apple Account sign-in. Signing in with an Apple Account inside a VM has historically been limited, and support has improved in recent macOS versions. Features that depend on it, such as some iCloud and App Store flows, may still behave differently.
• Physical devices. Connecting a real iPhone to a hosted machine is rarely practical in either model, so plan on simulators or a device cloud for on-device testing.
• Disk space. Xcode, simulator runtimes and DerivedData take a lot of space. VM images are often sized tightly; check how much you actually get.

On a dedicated Mac, Xcode behaves exactly as it does on a Mac on your desk, because it is one. Our Xcode build server page covers typical setups.

Isolation and security

A VM is a strong isolation boundary, and hypervisor escapes are rare. Still, VMs share physical hardware, and side-channel attacks between guests are a known class of risk on any shared platform. A dedicated Mac removes that category: no other customer's code runs on the machine.

VMs do have one security advantage. An ephemeral VM, destroyed after every job, leaves nothing behind for the next job to find. On a dedicated Mac you get the same effect with care: clean workspaces between jobs, separate user accounts, and secrets kept in a keychain or your CI system rather than on disk.

Cost

Because the licence limits how many macOS guests a host can run, virtual macOS is not as cheap as Linux VPS hosting. A VM on shared hardware is usually somewhat cheaper than a whole machine, and hourly billing after the minimum period can suit short bursts. For machines used every day, a dedicated Mac on a monthly or annual term is often competitive. At Hatmac a dedicated Mac mini starts from $119/mo on a 12-month term. Our Mac mini hosting cost guide compares the options in more detail.

Side-by-side comparison

Aspect	Dedicated cloud Mac	Mac VPS (macOS VM)
Hardware	Whole physical Mac	Slice of a Mac host
CPU performance	Native, consistent	Near native, can vary with neighbours
GPU / Metal	Full access	Paravirtualised, limited
Memory	All of it	Fixed allocation
Xcode and Simulator	Exactly as on a local Mac	Works, with resource limits
Reset to clean state	Manual or scripted	Fast snapshot or clone
Isolation	Physical	Hypervisor
Typical billing	Monthly or term	Hourly or monthly, 24-hour minimum per lease

When each is right

Choose a Mac VPS when

• You need short-lived, disposable build environments and can orchestrate them.
• Your jobs are CPU-bound and do not depend on Metal.
• You need a Mac for occasional testing and want the lowest entry cost.

Choose a dedicated cloud Mac when

• You run CI every day and want consistent, warm-cache build times.
• You use the GPU: LLM inference, rendering, video or Metal tests.
• You want a full remote desktop that behaves like a local Mac.
• You want physical isolation from other customers.

You can also combine them: run your own VMs on a dedicated Mac for disposable jobs, within the licence limits, while keeping full control of the host. Read more on our dedicated Mac server page.

FAQ

What is the difference between a cloud Mac and a Mac VPS?

A cloud Mac, in the dedicated sense, is a whole physical Mac assigned to you. A Mac VPS is a macOS virtual machine sharing a Mac host. The dedicated Mac gives full GPU access and consistent performance.

Are Hatmac machines virtual?

No. Each machine is a dedicated physical Mac mini or Mac Studio assigned to one customer.

Can I run macOS VMs on a rented dedicated Mac?

Yes, you control the machine, so you can use tools built on Apple's Virtualization framework. Stay within the licence limits on additional macOS copies.