Real-time API

Real-time audio, video, and data for your product.

Add live calls, multiparty rooms, and data channels with two small SDKs. Direct peer connections are unmetered — you only pay when sessions need relay or multiparty media.

Start with the SDKs Read the API reference

Two SDKs, one API

A server module to mint session tokens, a client module to join. Audio, video, and data ride the same shape.

P2P-first pricing

Direct peer connections are unmetered. You only pay when a session falls back to relay or multiparty rooms.

European by jurisdiction

Operated by a Swedish company on EU infrastructure. The procurement story is in the sovereignty section below.

How Radist fits in

Your app owns auth and product logic. Radist owns connectivity.

Keep your product focused on users, permissions, and the experience around each live session. Radist runs the infrastructure underneath — from a quick direct conversation to a multiparty room with shared media.

Your users, your rules

Your backend still owns accounts, roles, and permissions. Radist takes over only at the moment a session needs to be created.

Scoped per project

Each project gets isolated keys, usage counters, and billing. Spin up a staging project alongside production without crossing wires.

Survives the real network

Reconnects, NAT traversal, codec quirks, and flaky mobile links are handled by the SDKs rather than by your application code.

Honest meters

Nothing is recorded, transcribed, or counted twice. P2P sessions cost nothing; relay and rooms bill on what they actually used.

Developer experience

Straightforward to integrate.

Two small SDKs do the work. The server module creates sessions from the backend that already understands your users, while the client module joins with audio, video, data, or any combination of channels.

Sensible defaults out of the box, with hooks to take over connection state when you need to.

Server

import { RadistServerClient } from '@radist-tech/server';

const radist = new RadistServerClient({
  projectId: process.env.RADIST_PROJECT_ID,
  secretToken: process.env.RADIST_KEY
});

const { callId, callTokens } = await radist.createP2PConnection();
const [hostCallToken, guestCallToken] = callTokens;

return {
  callId,
  hostCallToken,
  guestCallToken
};

Create sessions from your server module with the users and permissions your app already understands.
Join from the client module with audio, video, data, or any combination of channels.
Use simple defaults first, then take over lower-level behavior only when your product needs it.

Sovereignty & GDPR

The boring part, done properly.

Procurement, legal, and your DPO will eventually ask where the data goes, who can reach it, and what's on paper. Here are the answers up front.

European jurisdiction

Operated by Rock and Stone AB, a Swedish company, on infrastructure inside the Union. Not reachable by US compelled-disclosure orders.

Data path stays here

Signaling, relay, and multiparty media all terminate inside the EEA. Participants outside the Union connect to the nearest European edge.

No media at rest

Calls are not recorded or transcribed. Session metadata is kept for 30 days for billing and abuse review, then deleted.

Paper trail for procurement

Signed DPA available on request. Published sub-processor list. You are the controller, Radist is your processor — said plainly in writing.