EU alternative
The EU-native alternative to US real-time vendors.
An EU region from a US company is still operated by a US company. Radist is different: a Swedish company running real-time infrastructure inside the EEA under EU law, so the jurisdiction answer changes before procurement starts.
| Question | Radist | Typical US vendor (EU region) |
|---|---|---|
| Operating entity jurisdiction | Radist Systems AB, a Swedish Aktiebolag operating under EU law. | Typically a US-headquartered entity, even when services are sold with an EU region. |
| CLOUD Act exposure | Not a US entity and not subject to US compelled-disclosure regimes for service data. | US corporate jurisdiction may still apply to the vendor, regardless of selected region. |
| Data path termination | Signaling, TURN relay, and multiparty room media terminate on EU infrastructure. | EU-region paths may terminate in Europe, but the operating company can remain under US jurisdiction. |
| Media recorded/transcribed | Not recorded, transcribed, or stored by Radist. | Depends on vendor configuration and product features. |
| Sub-processors | Short published list. US sub-processors are limited to dashboard sign-in and billing, covered by SCCs. | Often includes US parent-company services and broader global platform sub-processors. |
| DPA / procurement | Signed DPA available on request, with jurisdiction, data paths, retention, and sub-processors in one place. | Usually region settings plus a global DPA from the US-headquartered vendor. |
Note: multiparty room media is end-to-end encrypted by default, so Radist's SFU forwards encrypted frames it cannot read (falling back to DTLS only where the client lacks Insertable Streams). Google/GitHub sign-in and Stripe billing are SCC-covered US sub-processors. See the sovereignty page for the full data path and sub-processor schedule.