Scenes that follow the viewer.
Interactive and generative adult content can respond to the person watching. When the viewer turns it on, their own front camera tells your player how close they are, so the scene can build, hold at the edge and resolve with them.
- 01
The viewer’s camera
Their own device, once they turn the feature on
- 02
orgasm.dev
Imminence every second; each orgasm’s onset, peak and end
- 03
Your player
Reads the events over server-sent events
- 04
The scene follows
Tempo, the next segment, the resolution
Signals
What a scene follows
p30 and p60, about once a second: the probability that orgasm begins within 30 and within 60 seconds.
The tempo, which segment plays next, and when the resolution starts.
An orgasm has begun (women) or peaked (men), called a few seconds after it did.
Carry the scene through it, without cutting away.
When it was over.
The outro, and a quiet close.
Reference policies: build, hold, back off, sustain, ease off.
Edging modes and a synchronized finish.
Every field is described in signals; the edge, ruin and finish presets are reference policies to copy and tune.
What you can build
Scenes paced by the person watching
Adaptive pacing
The scene’s tempo follows the viewer: it builds while they are far off and holds while they are near the edge, so it neither rushes nor drags. An edging mode holds them there for as long as they chose.
imminence.updatededge preset
Branching on imminence
Choose the next segment of a branching scene by how close the viewer is: an extended segment while they are far off, a slower one at the edge, the resolution when they are ready.
imminence.updated
A synchronized finish
Start the resolution as p30 climbs, carry it through the viewer’s orgasm and play the outro once the end is called, so the scene lands with them rather than before or after.
imminence.updatedorgasm.end
Generative scenes
Feed imminence into a generative pipeline, video, voice or audio, as a control signal for tempo and intensity, so a rendered scene adapts second by second.
imminence.updated
Devices in step
Drive the viewer’s toy in time with the scene and with the viewer, on the same cues. The sex toy case study shows how.
reportStimulation
Creator tools
For OnlyFans creators and creators on platforms like it: a creator submits their own solo recording, and its timeline marks the onset, peak and end, so chapters and device scripts land on the moment. Live, creators put the HUD on their own stream from orgasm.dev’s Studio.
POST /v1/recordings
On the page
The viewer sees where they are
Pin the device SDK’s HUD beside the player: <orgasm-hud layout="rail"> on the siderail, or layout="bar" across the bottom of the page. It shows the viewer how close they are as a chance within 30 seconds, what just happened, the last three minutes, the counts and the clock, and what needs attention, such as their face out of view.
It always carries the indicator that analysis is on and the control that stops it, which the rules ask for, and it takes your colours, fonts and words. See Show the HUD.
On the sandbox
A synchronized finish
The sandbox’s woman-onset-end scenario with the finish preset. The scene builds once the baseline is in, sustains from the onset to the end, and eases into the outro once the end is called. Start the resolution on imminence: the onset itself is called a few seconds after it happens.
Consent
Consent, on both sides of the screen
Adult platforms already verify performers’ ages and agreements. An interactive scene adds a second person to protect: the viewer on camera. Each is the subject of something intimate, and each decides.
The viewer
- Interactive features analyse the viewer’s own front camera, on their own device, only after they turn the feature on.
- They are an adult you verified, not by a self-declared birthday, and they agreed knowing what is measured and who receives it.
- An indicator is on screen whenever analysis runs, and one control ends it: the HUD carries both.
- Viewer sessions need no history: create them with
retentionDays: 0, and the events are delivered as they happen and never kept. - Never use the events to identify, profile, retarget or recommend to a viewer, and never store the subject read as their sex or gender.
Performers
- Submit a recording only when every person in it agreed in writing to this analysis of that recording, and you hold their age records.
- Never analyse scraped, downloaded, pirated or third-party content, or any performer’s work without their agreement.
- A creator’s own solo recording is theirs to analyse, and where its markers are published is theirs to decide.
- A live session analyses the person on that camera, who turned it on. Never run one on a stream of someone else.
Integration
From the viewer’s browser to your player
The viewer’s browser publishes the front camera straight to the enclave, after verifying it, so neither your platform nor orgasm.dev ever sees the video: only numbers come back. A web player reads them over server-sent events with the session’s client token, and the HUD shows them to the viewer.
import { subscribe, streamOf } from '@orgasm-dev/device';
import '@orgasm-dev/device/hud';
import { threshold } from './hysteresis'; // from orgasm.dev/docs/concepts/timing
const edge = threshold(0.5, 0.35, 3); // near the edge once p60 holds 0.5 for 3 s
const hud = document.querySelector('orgasm-hud'); // <orgasm-hud layout="rail"> beside the player
subscribe({
...streamOf(session), // the session's stream, with the client token in a header
onEvent: (event) => {
hud.feed(event);
if (event.type === 'imminence.updated') {
const { p30, p60 } = event.data;
if (p60 === null) return; // calibrating, or no face: keep the current segment
player.setTempo(edge(p60, event.streamTimeS) === 'above' ? 'hold' : 'build');
if (p30 !== null && p30 >= 0.7) player.queueNext('resolution');
}
if (event.type === 'orgasm.end') player.queueNext('outro');
},
});
hud.addEventListener('orgasm-hud-stop', () => endSession()); // the viewer's one controlSafety
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 on an adult platform
Special-category data. The events are data about a person’s sex life and, from the face, biometric data: explicit consent under the GDPR, a written release under Illinois’s BIPA, and more. Acceptable use lists them.
No paywalls at the edge. Never time a purchase prompt, a tip request or a paywall to a viewer’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
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 studySex 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 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