You can boot a 'virtual iPhone' on a Mac now — but it's strictly for tinkerers, not iPhone-on-a-budget
A new open-source tool lets Apple Silicon Macs run a virtualised iOS, but it demands disabled security protections and doesn't play nicely with the EU or Japan.
What’s actually being claimed
A developer known as Lakr233 has published vphone-cli, a command-line tool that boots what its README calls a “virtual iPhone” on Apple Silicon Macs, using Apple’s own Virtualization.framework. It’s already racked up 8.8k GitHub stars and 1.3k forks, and a Hacker News thread discussing it has pulled in over 200 points and 65-plus comments — so people are clearly interested. The question, as ever, is what “virtual iPhone” actually means in practice.
What’s really going on under the bonnet
This isn’t Apple quietly shipping an official iPhone simulator for everyday users. The tool repurposes infrastructure originally built for Apple’s Private Cloud Compute (PCC) research virtual machines — the setup Apple provides so security researchers can inspect its server-side AI infrastructure — and points it at iOS instead. To get it running you need a fairly serious set of ingredients: an Apple Silicon Mac on macOS 15 (Sequoia) or later, a full Xcode installation with the iOS SDK to cross-compile a guest daemon, and — crucially — SIP and AMFI relaxed on the host. That last part means deliberately weakening two of macOS’s core security protections so the system will accept private “PV=3” entitlements on an unsigned binary. On top of that, the project pulls in a long list of command-line dependencies via Homebrew, from aria2 and zstd to reverse-engineering tools like ipsw and keystone.
In short: this is a build-it-yourself project for people comfortable compiling software, editing system security settings, and debugging along the way. It is not an app you download and double-click.
Who’s actually affected — and who isn’t
Ordinary iPhone or Mac users have nothing to install here and nothing to worry about. This tool doesn’t touch anyone’s real device, doesn’t run on Intel Macs, and doesn’t offer a shortcut to owning an iPhone’s software for free — it requires an Apple Silicon Mac running current macOS, plus a working Xcode setup, which puts it firmly in developer and researcher territory.
Even for that audience, there are limits. One detail flagged repeatedly in the Hacker News discussion: during setup, users are advised not to select Japan or the EU as their region, because the virtual device can’t satisfy “extra regulatory checks” tied to those markets. Commenters link this to the on-device eligibility checks Apple uses to gate alternative app marketplaces under the EU’s Digital Markets Act and Japan’s newer app-store rules — checks that a virtual machine apparently can’t pass. That’s a useful reminder that Apple’s regulatory compliance features are baked in at a level deep enough to trip up even a from-scratch virtualised device, not just real hardware.
What to do about it
Unless you’re already the sort of person who compiles kernels for fun and doesn’t mind loosening macOS’s security model, there’s no action needed here. This is a niche research and tinkering project riding on infrastructure Apple built for a different purpose, not a mainstream way to run iOS software on a Mac. For developers curious about iOS internals or PCC-style virtualisation, it’s a genuinely interesting proof of concept — just don’t expect it to behave like a real iPhone, particularly if you try setting it up as one based in the EU or Japan.