Remote stim used to mean a Bluetooth toy tied to an app. ReDrive drives the raw signal from any browser — patterns, position, intensity, ramps — into a rider’s own ReStim rig, anywhere. ReStim plays it out however they’re wired.
No app lock-in, no Bluetooth range limit — the raw signal, driven to any ReStim rig anywhere, over the wire.
Open a room and share the code with your riders. You hold the controls.
Have a room code? Patch your ReStim into a live session.
Set up a waiting room and send the link to your driver. When they claim it, you connect automatically.
Your driver visits the link and takes over — no account needed.
For a first-time driver. You set everything up, then send a link that opens a single touch pad — no dials, no menus. They just drag on the body to drive you.
You connect your ReStim as usual — your driver only sees the anatomy pad.
ReDrive lets a driver remotely control one or more riders’ ReStim e-stim devices in real time over the internet. The driver uses a browser-based control panel — adjusting patterns, intensity, ramps, beta sweeps and more. Riders don’t install anything new — their own ReStim is the client. They open a join link in any browser and it bridges the signal straight into their local ReStim. There’s also an optional touch canvas the driver can use with an anatomy overlay, but the main controls are the standard sliders and pattern buttons.
A PC running ReStim (its WebSocket server starts automatically, default port 12346), and any modern browser. That’s it — no app to download. Your driver sends you a join link; open it in your browser and it bridges automatically to your local ReStim. ReStim then sends the signal to whatever you run — audio / StereoStim, FOC-Stim, or NeoStim. See the field manual →
Yes — there’s an optional headless bridge: download redrive_bridge.py (or view the source). It connects to a room from the command line and forwards the signal to your local ReStim, no browser needed: pip install websockets, then python redrive_bridge.py YOURCODE. Handy on Linux/Mac or if your browser blocks ws://localhost. You lose the rider UI (feel orb, watch-along) — it’s a pure signal bridge.
Nothing, really — ReStim starts its WebSocket server automatically on startup (port 12346), and the ReDrive bridge page connects to ws://localhost:12346/tcode for you. If you’ve changed the port, set it in the bridge panel. See the
ReStim GitHub
for setup help.
The touch canvas and anatomy overlay steer sensation between three points, so placing your FOC / ReStim electrodes to match the picture makes what the driver touches line up with what you feel. On a standard FOC box, wire the three channels like this:
Matched up this way the overlay reads true — the spot the driver drives is the spot you feel.
Open the join link your driver shared (or go to this page and enter the room code). Your browser connects to the session and bridges directly to your local ReStim — nothing to install.
Any phone, tablet, or computer with a modern browser. No app or install needed — just create a room and share the code.
Pattern type (Hold, Sine, Ramp ↑, Ramp ↓, Pulse, Burst, Random, Edge), intensity, speed, depth, beta sweep (which electrodes are active and how they cycle), alpha oscillation, intensity ramp, and 4-channel funscript mode for direct electrode control. Presets let you save and recall full configurations instantly. There’s also an optional touch canvas with anatomy overlays for a more hands-on control style. See the field manual →
Yes — share your room code with as many riders as you like. They all receive the same signal simultaneously.
By default your session appears in the Live Sessions list on this page. You can switch to private using the 🔒 toggle in your room’s share panel, which removes it from the list. Your driver key (part of your room URL) is always required to access the driver controls — the room code alone only gives rider access.
Rooms expire automatically after a period of inactivity. Waiting rooms (rider-initiated) expire after 30 minutes if unclaimed.
ReDrive sends T-code commands (pattern shape and relative intensity) — it does not access your hardware directly. The rider’s ReStim device receives these as normal T-code input. The rider always controls their own maximum output level at the device itself. Never run at intensities that are uncomfortable — the driver controls pattern, but you control your ceiling.
Use the overlay maker tool → — upload a photo, align it to the outline, download a ready-to-use PNG.