peerkit.dev

Live sessions. Built into your app.

Video, audio, and data. One API and SDK.

The current release sends one phone camera to one browser. The person filming does not need an account. A session can also include one-way microphone audio from that phone. Two-way audio, extra participants, and data channels are not in this release.

Open the dashboard Read the API

Available now

Phone camera to browser

Create a session

From the dashboard, or from your server with an API key that never reaches the browser.

Invite the camera

Share an expiring link or QR code. Opening it does not create a PeerKit account.

Watch it live

One viewer joins in another browser. That viewer can record the received camera locally, including the phone microphone when the session has one-way audio. A front or rear camera switch stays in the same recording. Media is forwarded by the PeerKit media server, with TURN as fallback.

Keep the API key on the server

Browsers receive a short-lived participant token. This call stays on your server.

const response = await fetch(process.env.PEERKIT_API_URL + "/v1/sessions", {
  method: "POST",
  headers: {
    authorization: "Bearer " + process.env.PEERKIT_API_KEY,
    "content-type": "application/json",
  },
  body: JSON.stringify({ durationSeconds: 1800 }),
});

Roadmap

Not available yet

Conversation

Two-way audio, screen sharing, and more than one camera or viewer. One-way audio from the phone is already available.

Control and capture

Data and control channels. Server recording is not in this release.

Scale-out

Native SDKs and additional regional media nodes. Redis stays out until cross-node coordination needs it.