Build real-time products on European infrastructure.
Add real-time calling to your product in minutes. Direct peer connections are free. Scale to relay and multiparty rooms when needed.
Ship in minutes
Drop-in call UI or two small SDKs. Go from zero to live video without building WebRTC yourself.
P2P is free
Direct peer connections cost nothing. You only pay when sessions need relay or multiparty rooms.
Infrastructure is on us
The SDKs handle reconnection, NAT traversal, and mobile handoff.
Live demo
Play a round, talk while you do
Tic-tac-toe over a Radist session: open it, share the link with someone, and you get voice plus a data channel carrying the moves. No sign-up, and the whole thing is about a hundred lines of client code.
Share a link or scan the QR code to bring in the second player.
Live audio both ways, with mute and speaking indicators.
Moves travel peer-to-peer on the session's data channel.
From no-code to full control
Integration options
Start with a fully managed Space, replace either the frontend or backend independently, or build both with the SDKs. Public, password, and host-approved Spaces handle admission without your own backend.
| Frontend → | Easy Interface | Custom frontend |
|---|---|---|
| Managed Spaces | Managed Spaces Create a Space and share its hosted link. | Custom Space UI Build on Spaces with |
| Custom sessions | Easy Interface Mint tokens and use Radist's hosted call UI. | Fully custom Own both layers with the server and client SDKs. |
How it works
How it works
01
Create a project
Sign up, grab your keys, and mint session tokens from your backend with the server SDK.
02
Connect your users
Use the hosted Easy Interface for instant video, or join with the client SDK for full control.
03
Add capacity
Start with direct P2P calls. Add relay and multiparty rooms through the same API.
What Radist handles
Your product and Radist connectivity
Your application handles users and permissions. Radist runs connectivity from direct calls to multiparty rooms.
Your users, your rules
Your backend owns accounts and permissions. Radist starts live sessions.
Scoped per project
Isolated keys, usage counters, and billing per project. Run staging alongside production without crossing wires.
Network handling
The SDKs handle reconnection, NAT traversal, and mobile handoff.
Usage metering
Media is never recorded or transcribed. P2P is free; relay and rooms are metered by use.
Developer experience
SDKs
Use the hosted Easy Interface or SDK defaults. The same tokens and sessions support full control over connections and streams.
Browse the docsPricing
Pricing
Direct peer-to-peer connections are free on the Free plan. You pay when sessions use relay traversal or multiparty rooms.
See full pricingFree
€0
Unmetered P2P. 100 multiparty minutes/month to evaluate rooms.
Plus
€20
10 GB relay and 5,000 room minutes included. €0.004/min after that.
Enterprise
Custom
Volume pricing, SLAs, and procurement support.
No media recorded or transcribed
Session metadata retained 30 days, then deleted
Signed DPA available on request
Procurement evidence →Frequently asked questions
Data, jurisdiction, and retention
Where does our data physically live?
All production infrastructure runs in EU data centres (Hetzner, Germany and Finland). Participants outside the EEA connect to the nearest European edge.
Are you subject to the US CLOUD Act?
Radist Systems AB is a Swedish company with no US entity or US establishment, so it isn't a provider that can be compelled under the CLOUD Act. Two US sub-processors are in scope for the data they hold: our dashboard sign-in provider holds your account identifier, and Stripe holds billing records. Neither holds media, signaling payloads, or session content. Those never leave EU infrastructure, and media isn't stored at all.
Is any media recorded or transcribed?
Media streams are never recorded, transcribed, or stored.
Are calls encrypted end-to-end?
Direct peer-to-peer calls are always end-to-end encrypted with DTLS-SRTP. When a call needs TURN, the relay forwards encrypted packets it cannot read. Multiparty rooms use per-frame AES-GCM encryption through WebRTC Insertable Streams in Chrome and Edge, so the SFU does not receive the keys. Firefox and Safari fall back to DTLS, where the SFU can read media in transit.
How long do you keep session data?
Real-time session metadata is retained for 30 days for billing and abuse review, then deleted. Signaling payloads and media are not stored beyond the live session.
Can we get a DPA for our procurement review?
Yes. A signed Data Processing Agreement is available on request.
Start building on European real-time infrastructure.
Ship live features on Swedish-owned, EEA-hosted infrastructure. Direct peer connections are free. You pay when sessions need relay or multiparty rooms.