Gameplay that keeps pace with the player.
orgasm.dev turns a consenting adult player’s front camera into two things a game can be designed around: how close they are to orgasm, every second, and how many orgasms the session has counted so far. Build pacing, power-ups, unlocks and an in-game economy on them.
- 01
The player’s camera
Published from their own device, sealed to the enclave
- 02
orgasm.dev
Imminence every second; each orgasm’s onset, peak and end
- 03
Your game
Reads the event stream, and can show the player the HUD
- 04
The play adapts
Pace, power-ups, unlocks and score
Signals
What a game reads
p30 and p60, about once a second: the probability that orgasm begins within 30 and within 60 seconds.
Live mechanics: pace, difficulty, the edge zone and power-ups.
An orgasm, confirmed a few seconds after it began: the onset for women, the peak for men.
Score, rewards and the end of a level.
The session’s running count, 1, 2, 3, carried on every call.
Unlocks, tiers and achievements.
When it was over.
A cool-down, the results screen, the next round.
Reference presets that hold, back off and stop on imminence.
Edging and denial modes.
Every field is described in signals; the edge, ruin and finish presets are reference policies to copy and tune.
What you can build
Mechanics built on the player’s arc
Pacing and difficulty
Map p60 to tempo, spawn rate or difficulty. Build while the player is far off and level out as they near the edge, or, in a challenge mode, raise the stakes the closer they get.
imminence.updated
Power-ups in the edge zone
Charge a shield, a score multiplier or slow motion while p60 stays above your entry level. Hysteresis keeps the charge from flickering; crossing over ends it.
imminence.updatedorgasm.peak
Unlocks on the count
Gate levels, areas, outfits or story chapters on orgasmIndex: the first orgasm opens the second chapter, the third a hidden area. Settle unlocks on calls, never on imminence.
orgasm.onsetorgasm.peak
An economy of confirmed orgasms
Pay out experience or currency for each confirmed orgasm and a smaller trickle for time held in the edge zone, to spend on upgrades and cosmetics.
orgasm.onsetimminence.updated
Edging and denial modes
Run the edge preset as a mode that scores each approach and back-off, or the ruin preset as a denial challenge. The player picks the mode, and any forfeit, before play.
edge presetruin preset
Head to head
Two players, each on their own camera: first to a set count, or last to cross over. Each sees only what the other agreed to share.
orgasmIndex
On screen
The player sees what the game sees
Put the same read in the corner of the screen: <orgasm-hud layout="card"> from the device SDK shows the phase and the chance of orgasm within 30 seconds, with the indicator and the Stop control the rules ask for. A larger panel adds the last three minutes, the counts and the clock.
An engine that draws its own interface reads the same model the element draws, as plain data every frame. See Show the HUD.
On the sandbox
The edge zone, played as a game
The sandbox’s edge scenario, drawn from the events it sends: three approaches and no orgasm. Each hold, where p60 reaches 0.5, is where a power-up starts charging; each back-off, where p30 reaches 0.6, is where the game eases the pressure before the player crosses over. Run it yourself with any sk_test_ key and sandbox.scenario: "edge".
Integration
One stream, from engine to enclave
Your server creates the live session with the secret key and hands the game a client token. The player’s device publishes its front camera straight to the enclave, so the video never touches your servers. The game reads the event stream with the device SDK’s subscribe, or an engine’s own HTTP client, and if it also drives a toy it reports each change of stimulation with reportStimulation.
import { subscribe, streamOf } from '@orgasm-dev/device';
import { threshold } from './hysteresis'; // from orgasm.dev/docs/concepts/timing
const zone = threshold(0.5, 0.4, 3); // in once p60 holds 0.5 for 3 s, out below 0.4
// Each event once and in order, resumed after a dropped connection.
subscribe({
...streamOf(session), // the session's stream, with the client token your server handed over
onEvent: (event) => {
switch (event.type) {
case 'imminence.updated': {
const { p60 } = event.data;
if (p60 === null) break; // calibrating, or no face: keep the current pace
level.setPace(p60); // your curve
powerUp.charging = zone(p60, event.streamTimeS) === 'above';
break;
}
case 'orgasm.onset': // a woman's orgasm began
case 'orgasm.peak': // a man's orgasm peaked
wallet.add(500, `orgasm ${event.data.orgasmIndex}`);
unlocks.reach(event.data.orgasmIndex); // the running count
break;
case 'orgasm.end':
level.coolDown();
break;
}
},
});Safety
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 game
Adults-only titles. Ship these mechanics only in an adults-only game, behind age verification of your own, never in an all-ages title.
Stakes agreed before play. A forfeit, a reset or a lost unlock tied to a call is something the player chose in advance, and can contest.
Nothing shared by default. Show a player’s imminence or count to another player, a spectator or a stream only if that player chose to, with a view token for that screen.
No real money at the edge. Never offer a purchase, a continue or a currency pack timed to a player’s imminence.
Read the acceptable use policy, the presets’ safety notes and how the enclave keeps the video private.
Other industries
The same signals, elsewhere
Sex toy manufacturers
A toy that responds to the body, not just the remote.
The toy builds while the person is far off, backs off at the edge and carries them through, on rules they chose.
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