Live sessions open

Orgasm, as an event stream.

Know when your users orgasm, with live updates as they get close.

From a consenting adult’s front camera, analysed in a verified enclave and never stored.

Sandbox keys work instantly. Live keys after a short setup.

Live session8:47
Brows
Eyes
Cheeks
Nose
Lips
Corners
Jaw

At rest

What your app receives

  1. 0:32.0subject.identifiedwoman · pWoman 0.94
Read inside the enclave: her face, her voice and her heart. Sent to your app: imminence every second, then the onset and the end, each a few seconds after it happens. Solid lines mark the moment; dashed lines, when it was called.

What people build

Experiences that keep pace with the person

Signals

Five events, from one camera

imminence.updated

Imminence

The probability that orgasm begins within 30 and within 60 seconds, about once a second.

Needs: Face

orgasm.onset

Onset

When a woman’s orgasm began, called a few seconds after it did.

Needs: Face and microphone

orgasm.peak

Peak

The peak of a man’s orgasm, called a few seconds after it.

Needs: Face and microphone

orgasm.end

End

When it was over: from the onset detector for women, from the face for men.

Needs: Face, and the microphone for women

subject.identified

Subject

Whether the face reads as a woman’s or a man’s, which decides the detectors. You never have to say.

Needs: Face

confidence

On every signal

High, medium or low, from how much of the face and voice the call was made on.

For developers

Your first event in three calls

  1. POST /v1/live-sessions

    Your server opens a session with its secret key. In the sandbox, a scripted session starts playing at once.

  2. publishLiveSession()

    The person’s device verifies the enclave and sends its front camera and microphone straight to it, with the SDK.

  3. GET /v1/live-sessions/{id}/stream

    Imminence about once a second, and each onset, peak and end a few seconds after it happens, as server-sent events, over a WebSocket or to your webhooks.

Recorded videos go in through POST /v1/recordings and come back as the same events on a timeline. Recordings →

event: orgasm.onset
data: {
  "id": "evt_2099smltv0t2c2wzzyzq",
  "object": "event",
  "type": "orgasm.onset",
  "mode": "test",
  "sessionId": "ls_8f3kq2m7x9w4c1n6t5ra",
  "sequence": 969,
  "streamTimeS": 542.6,
  "confidence": "high",
  "data": {
    "orgasmIndex": 1,
    "eventAtS": 538,
    "calledAtS": 542.6,
    "lagS": 4.6,
    "detector": "onset_end",
    "score": 0.71,
    "threshold": 0.5
  },
  "wallTime": "2026-10-16T14:00:55.260Z"
}

Open by design

Don’t take our word for it

The code that touches your users’ video is open source, and the enclave proves which release it runs before a device sends it anything.

Principles

Built to be trusted with this

Adults who said yes

Every request that starts an analysis attests that the person on camera is a verified adult who agreed to it and can stop it.

Numbers out, never video

Media is decrypted only inside a confidential-computing enclave the device verifies first. It is never stored; only the events leave.

Signals, not verdicts

Every event says how complete its input was. Edge, ruin and finish are policies you run on the signals, with a stop that always works.

Read how the enclave works and what you agree to.

Start building in the sandbox.

Sign up, tell us what you are building and accept the Acceptable use rules, and your sandbox key is waiting. Scripted sessions play the same events a real one does, so the integration is done before the first person goes live.