A toy that responds to the body, not just the remote.
App-connected toys follow a pattern, a partner’s remote or a script. orgasm.dev lets your companion app follow the person too: the phone’s front camera reads how close they are, and the toy builds, holds at the edge, backs off or carries them through, on rules they chose.
- 01
The phone’s front camera
Published from the person’s own phone, sealed to the enclave
- 02
orgasm.dev
Imminence every second; each orgasm’s onset, peak and end
- 03
Your app
Turns the events into cues, and the cues into levels
- 04
The toy
Follows over Bluetooth, within the person’s limits
Signals
What a toy responds to
p30 and p60, about once a second: the probability that orgasm begins within 30 and within 60 seconds.
The intensity curve, and backing off before the edge.
An orgasm has begun (women) or peaked (men), called a few seconds after it did.
Hold the pattern steady through it.
When it was over.
Wind down, or build again for the next.
Your report of the toy as it changes: on or off, its level and the most it goes to, each motor’s level, its mode.
Imminence accounts for how long the person has been stimulated, and the HUD shows the toy beside their signals.
Reference policies that turn the events into cues.
Your modes, ready to tune.
Every field is described in signals; the edge, ruin and finish presets are reference policies to copy and tune.
Cues to actuators
One set of cues, every kind of toy
The presets answer with seven cues. Map each one to your hardware once, and every mode runs on every device you make.

Vibration
Amplitude climbs on build, freezes on hold and sustain, and drops to a low idle on back off.

Stroking
Speed and stroke length follow the cues; back off slows to a rest rather than stopping abruptly.

Air pulse
The nozzle that seals over the clitoris follows the cues: pulse strength climbs on build, holds through the orgasm, and eases on back off.

Rotation and thrusting
Motor speed follows the cues; hold keeps the rhythm steady and back off pauses it.

Inflation
Inflates only in small steps on build, never on a signal alone, and releases pressure at once on stop.

Electrostimulation
The unit ramps its output gently under a ceiling set in the hardware, and cuts it at once on back off and stop.

Thrusting machines
Stroke speed and depth climb on build and hold steady through the orgasm; back off slows the stroke and stop parks the rod.
What you can build
Modes for a toy that can see the person
Finish
Builds while the person is far off, holds the pattern steady through the orgasm instead of changing it, then winds down once it is over. Set a count for more than one.
finish preset
Edge
Holds as p60 climbs, backs off before the edge and resumes after a rest, for as many approaches as the person asked for.
edge preset
Adaptive
Intensity tracks p60 continuously within the person’s limits, so the toy follows them rather than a timer or a looped pattern.
imminence.updated
Ruin and denial
Stops for good at the point of no return, timed on imminence because a call would come too late. Intense, so strictly opt-in.
ruin preset
Partner play
A partner holds the remote and sees a gauge of how close the person is, if the person chooses to share it, so the partner can take them to the edge and hold them there.
imminence.updated
Long distance
One partner’s onset or peak sets off the other’s toy, across any distance, with each partner’s agreement to what the other receives.
orgasm.onsetorgasm.peak
On the sandbox
Finish, twice
The sandbox’s finish scenario with the finish preset set to two orgasms. The toy builds once the baseline is in, holds its pattern from each onset to its end, builds again in between, and winds down after the second.
On screen
The toy beside the person
Report the toy as it changes and the HUD shows it with the person’s signals: its name, its mode, a bar per motor, and its level across the whole session under imminence, each change of mode marked. A partner’s screen, read with a view token, sees the same. The HUD only shows the toy; your app’s own controls set it. Below, the edge scenario with a scripted two-motor toy.
Ecosystem
Built for the app you already ship
Your companion app already holds the phone, the account and the Bluetooth link to the toy. orgasm.dev adds the one thing it cannot see: how close the person is. That suits makers of app-connected toys and machines such as these, and any app built on the open-source Buttplug protocol.
- Lovense
- Kiiroo
- We-Vibe
- Satisfyer
- Lelo
- Magic Motion
- Svakom
- The Handy
- Vorze
- Hismith
- OSSM
Buttplug and Intiface
The open-source protocol and server that already drive hundreds of app-connected devices through one interface. If your app speaks it, map the seven cues to its generic commands once, and every device it supports can follow a preset.
buttplug.io ↗Company and product names are the trademarks of their owners. orgasm.dev is not affiliated with or endorsed by any of them; each maker decides whether its app integrates.
Integration
The app closes the loop
The phone publishes its front camera straight to the enclave. The events reach your app, on the phone or through your cloud; the app runs a preset, turns each cue into a level and sends it to the toy. Each time the level or the mode changes it reports the toy, so imminence knows how long the person has been stimulated and every screen of the session shows the toy.
import { finish, type Cue } from './presets'; // from orgasm.dev/docs/concepts/presets
const preset = finish();
const cap = settings.maxIntensity; // the person's own limit, 0 to 1; the firmware keeps its own
// Each cue sets where the toy is heading, and how many seconds it takes to get there.
function plan(cue: Cue, level: number): [target: number, rampS: number] {
switch (cue) {
case 'build':
case 'resume':
return [cap, 90]; // climb slowly toward the cap
case 'hold':
case 'sustain':
return [level, 0]; // keep the pattern steady, through the orgasm too
case 'back_off':
return [Math.min(level, 0.1), 1];
case 'ease_off':
return [0, 8];
case 'stop':
return [0, 0];
}
}
live.subscribe({
onEvent(event) {
const cue = preset.next(event);
if (!cue) return;
const [target, rampS] = plan(cue.cue, toy.level);
toy.rampTo(target, rampS); // your Bluetooth command
},
onState: (state) => state === 'reconnecting' && toy.rampTo(0, 8), // the stream is gone: wind down, never keep building
});
// Each time the toy's level or mode changes, say so: imminence then accounts for time under
// stimulation, and the HUD and a partner's screen show the toy. Merged and paced for you.
toy.onChange = () =>
live.reportStimulation({
state: toy.level > 0 ? 'on' : 'off',
level: Math.round(toy.level * 100),
levelMax: Math.round(cap * 100),
channels: toy.motors.map((motor) => ({ id: motor.id, level: Math.round(motor.level * 100) })),
mode: toy.pattern, // 'waves', 'pulse'
drive: 'auto',
device: { label: toy.model, connected: toy.connected },
});
stopButton.onclick = () => toy.stop(); // local: needs no signal, network or serverSafety
What every integration builds in
Adults who said yes
Everyone on camera is an adult you verified, who agreed to this analysis before it started. A self-declared birthday is not verification.
Never covertly
The person sees when analysis is running and can end it at any moment. Consent to one experience is not consent to another.
A stop that always works
One control ends stimulation or the experience at once, without depending on the signals, the network or your server.
Signals advise; limits decide
Never raise intensity or take an irreversible step on a signal alone. Cap intensity in the device, and treat a null reading as unknown and hold.
False calls happen
Detectors miss real orgasms and call ones that did not happen. Any consequence of a call is agreed in advance and can be contested.
Keep as little as you can
The events are data about a person’s sex life. Keep them only as long as the experience needs, down to none, never sell them, and delete them on request.
And in a toy
Limits in the hardware. Cap intensity, pressure and current in the firmware, not in the app or the policy; the person sets their own maximum below it.
A stop on the toy itself. A button on the device, and one in the app, stop it at once, with no camera, network or signal involved.
Fail safe. If the stream, the network or the Bluetooth link drops, the toy winds down; it never keeps building on a stale reading.
Electrostimulation. Follow the unit maker’s instructions. Never pass current across the chest or near the heart, and never use it with a pacemaker or another implanted device.
Inflation. Release pressure at once on stop, and never inflate on a signal alone.
Thrusting machines. Set stroke-length and depth limits in the hardware, keep the travel path clear, and make stop park the rod rather than reverse it.
Read the acceptable use policy, the presets’ safety notes and how the enclave keeps the video private.
Other industries
The same signals, elsewhere
Game developers
Gameplay that keeps pace with the player.
Difficulty, power-ups and unlocks that follow how close the player is and how many orgasms they have had.
Read the case studyAdult entertainment
Scenes that follow the viewer.
Interactive and generative scenes that build, hold and resolve with the viewer, from the viewer’s own camera.
Read the case studyAI chatbots
Companions that know where the user is.
Voice and video companions that pace the conversation to the user and know when it is time for aftercare.
Read the case study