Remote Simulators
Sign in to start a remote simulator. See Remote simulator pricing for rates.
A remote simulator runs your React Native app on our servers and lets you watch and drive the authoritative instance from anywhere. You hand Peach your app folder, or a Metro JavaScript bundle, and it opens a browser-hosted iOS simulator. There is no Xcode and no local simulator process.
Launch one
Sign in once with peach login, or set PEACH_API_KEY to an API key with the
sims scope. Then, from your Expo or React Native app’s folder:
Peach builds the app with the app’s own bundler and runs it. Your Metro configuration needs no changes.
You can also hand it a bundle you built yourself. Wrap your app’s Metro
configuration with
withPeach(config) from
peachsim/metro (npm install --save-dev peachsim), which records the
installed React Native version and module identities the hosted runtime needs,
then build and pass the bundle:
The command prints and opens the simulator viewer.
The CLI uses Peach Cloud by default. Set PEACH_BOX_ENDPOINT or pass
--endpoint to use another service; the flag takes priority.
How it actually works
peach ios --remote builds your app folder when you give it one, produces a
self-contained artifact, splits it into bounded parts, and creates a hosted
session. The control plane stores your bundle files,
revisions, identity, and lifecycle state, while a hosted headless browser joins
the parts, boots the app in Peach’s CPU renderer, and remains the single
authoritative simulator.
The hosted session exposes that simulator through Remote Viewing. Viewer browsers receive scene commits and compose them locally, while input travels back to the same hosted instance.
What you give it
- +Your app folder, or a JavaScript bundle. A folder is built for you. A bundle is one local
.jsfile or one HTTPS URL. HTTP URLs are refused. Hermes bytecode is refused, so supply the JavaScript bundle produced before Hermes compilation. - +Your assets. Peach finds Metro’s compiled asset directory on its own and embeds the declared scales into the artifact. See bundles and assets below.
- +Your app’s native modules, when it has any. From your app folder, or the folder a local bundle sits in, Peach compiles its Expo modules, Nitro modules and C++ TurboModules on your Mac, as it does when you open the app locally, and ships them inside the artifact. Pass
--native-project <app-dir>when the bundle lives elsewhere. Remote Android simulators do not load compiled Kotlin modules yet. - +Nothing else. No Xcode project, no provisioning profile.
Bundles and assets
Peach locates the compiled asset directory Metro wrote, rather than asking you to name it. It reads the asset graph out of your bundle first, then checks the handful of places Metro actually writes to and picks the directory that resolves the most declared asset scales. The directory it chose is printed when the simulator starts.
If an image is declared by the bundle but missing from every candidate directory, Peach embeds a magenta checker in its place at every declared scale, and prints one warning naming each substituted asset and every directory it searched. The descriptor keeps Metro’s own width and height, which is what React Native lays an image out from, so the stand-in changes the pixels without moving your layout. A missing image will not stop a session from starting, and you will always be told it happened.
Fonts, video, and audio still refuse, because there is no stand-in a viewer would read as missing.
Peach never recompresses your images. Embedded bytes are the bytes you built.
Remote viewing
Remote Viewing opens the running simulator in a browser and paints the authoritative hosted instance with the viewer’s local Peach compositor. A person and an agent therefore see the same app state. Pointer, scrolling, keyboard, text editing, and the agent cursor travel over the same leased connection.
The viewer is private to members of the account running the simulator and uses a short-lived display grant without exposing the command credential. One viewer at a time holds the input lease, and another viewer takes it by tapping or typing in the simulator.
Session lifecycle and cost
Remote simulator time costs $0.005 per minute while running. Server-side builds cost $0.005 per minute of bundling. Build minutes prepare your app; simulator minutes run it.
The remote simulator belongs to the project folder you opened it from, so later
peach commands from that folder, including a coding agent’s, drive it.
peach remote close ends the active session and stops the simulator charge.
Closing its viewer tab does not stop the hosted session. See
Remote simulator pricing for rates and account limits.
What it can and cannot do
The remote simulator supports:
- +Remote Viewing with live pointer, scrolling, keyboard, and text input
- +people and agents driving the same authoritative simulator
- +hot reload from edits to its hosted files
- +a private local-copy mode with the Peach inspector
- +stable member URLs across session restarts
The hosted renderer uses the CPU tier.
Next
- +Remote simulator pricing explains session costs and account limits.
- +CLI reference lists the remote launch and close commands.