1
Create a session
From the dashboard, or from your server with an API key that never reaches the browser.
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. Audio, extra participants, and data channels are on the roadmap, not in this release.
Available now
Phone camera to browser
2
Invite the camera
Share an expiring link or QR code. Opening it does not create a PeerKit account.
3
Watch it live
One viewer joins in another browser. 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
Bidirectional audio, screen sharing, and more than one camera or viewer.
Control and capture
Data and control channels, plus recording.
Scale-out
Native SDKs and additional regional media nodes. Redis stays out until cross-node coordination needs it.