BUILDS.IO Sign up

LocalDevVPN: SideStore JIT With No PC on iPhone

Updated Jul 14, 2026
Sid closing a self-loop tunnel so JIT runs with no PC

LocalDevVPN is the small piece that makes JIT for SideStore work without a computer once your device is set up. If you sideload emulators or tweaked apps with SideStore and keep hitting the “you need a PC to enable JIT” wall, LocalDevVPN is the tool that gets quoted as the fix. It is a free, on-device VPN that lets your iPhone talk to itself as if a trusted computer were plugged in — which is the exact trick that JIT enabling on iOS needs. Here is what it actually does, how the pairing file and tunnel fit together, and where iOS 26 and 27 break the whole thing.

What LocalDevVPN actually is

LocalDevVPN is a loopback VPN. Instead of routing your traffic to a remote server, it spins up a virtual network interface that points back at your own device. The App Store listing is published by Coxson Engineering LLC, it is free, and it requires iOS 14.0 or later. The original open-source project is jkcoxson’s LocalDevVPN, itself forked from SideStore’s own StosVPN, and several community forks of the repo exist.

The privacy story is simple because there is no remote leg. As SideStore’s own docs put it, the VPN “is only connecting to your own device. No remote servers are used, meaning no external connections, meaning no extra battery drain.” Nothing about it resembles a commercial “hide my IP” VPN — the name is almost misleading. It is plumbing for on-device debugging, filed under Developer Tools.

Why SideStore needs a VPN at all

JIT — Just-In-Time compilation — is what lets emulators and a handful of advanced apps run at full speed instead of crawling through interpreted code. Apple only hands that permission to an app while a debugger is attached, and normally that debugger lives on a Mac or PC connected over USB. That is the “you need a computer” problem in one sentence.

The workaround is to make the iPhone play both roles. SideStore and StikDebug “use a specially designed VPN in order to trick iOS into” thinking a trusted computer is present. A pairing file — generated once, with a computer, during SideStore’s install — stands in for the trust relationship a real Mac would have. LocalDevVPN provides the local network path the on-device debugger uses to reach the system services that grant JIT. Pairing file plus loopback tunnel equals a phone that can debug itself.

Worth being precise about the “no PC” claim: you still need a computer exactly once, to create that pairing file and install SideStore. After that, LocalDevVPN and StikDebug run entirely on the phone.

Sid tangled in the old JIT chore: laptop, cable and a re-run clock

How to enable JIT with LocalDevVPN

The current on-device flow, per the SideStore JIT docs, looks like this:

  1. Install StikDebug (formerly StikJIT), the on-device debugger for iOS 17.4 and up, and make sure your pairing file is in place.
  2. Open LocalDevVPN and connect it, on Wi-Fi or with Airplane Mode enabled.
  3. Open StikDebug once so it can mount the developer disk image, then force-close and reopen it.
  4. Long-press the sideloaded app you want to accelerate and tap “enable JIT.”

If JIT fails to stick, the two usual suspects are the VPN connection (it has to be on and reachable) and the pairing file. None of that touches a computer once the pairing file exists.

LocalDevVPN vs StikJIT, JitStreamer and WireGuard

These names get mixed up constantly, so here is the split:

  • StikDebug / StikJIT is the debugger — the app that actually attaches to your sideloaded app and flips JIT on. It is powered by the idevice library and needs both a pairing file and a loopback VPN to work.
  • LocalDevVPN (or StosVPN) is that loopback VPN — the network layer StikDebug talks over. It is not a JIT enabler by itself.
  • JitStreamer was the older, server-based approach from the same author. It ran remote servers, required a WireGuard profile, and generated pairing files through a Jitterbug Pair tool. It has been retired — the project page now tells users to switch to StikJIT.

That history explains the “stabler than WireGuard” line in LocalDevVPN’s description. The old JitStreamer path leaned on a WireGuard tunnel to a remote box; LocalDevVPN keeps everything on-device and, per the project, works offline. There is no published benchmark behind the stability claim, so treat it as the maintainers’ framing rather than a measured result.

The catch: iOS 26 and 27

This is where the picture gets honest. On iOS 17.4 through 18 (excluding the 18.4b1 beta), StikDebug plus LocalDevVPN is the stable route; iOS 17.0–17.3 uses SideJITServer instead, and iOS 16 and below can lean on SideStore’s built-in minimuxer method. Then iOS 26 changed the rules.

On iOS 26 and 27, JIT no longer works broadly. The get-task-allow entitlement that used to be enough is out; instead, each app has to manually add support for a new JIT method, so only a short and slowly growing list of apps can use it at all. iOS 26.4 went further and closed the offline trick — as one report on the change put it, “There is no known way to get JIT running offline on 26.4 anymore,” with the old Airplane Mode bypass gone. StikDebug 3.1.0 later restored function for many users on 26.4, but the underlying limit — apps must opt in — still stands. If you are on the newest iOS, assume JIT is a narrow, per-app feature, not a switch you flip once.

Sid calm at the sealed loop, app running at full speed with no PC

When you would rather skip the whole layer

Step back and the reason LocalDevVPN exists is that iOS refuses to trust your phone without a computer in the loop, and free signing expires every seven days. That is a lot of scaffolding — a pairing file, a loopback VPN, a debugger app, a maintenance ritual — just to keep sideloaded apps alive.

That is the pain builds.io removes from a different angle: apps are signed server-side and stay signed for your subscription, so there is no pairing file, no VPN to keep apps running, no seven-day refresh, and no computer after the fact. A revoked certificate is replaced for you rather than sending you back to a rebuild. JIT stays a separate, narrow concern — it mainly matters for a few demanding emulators, and most catalog apps, tweaks and streaming tools never needed it.

So the split is clean. If you run SideStore and just want emulators to breathe, LocalDevVPN is the right tool and it is free. If what you actually want is apps that install in Safari and keep working through the next iOS 27 update, that is a different problem — and it does not need a VPN.