This section describes design decisions implemented or being implemented in the product. See the Honesty boundary for what is live today versus roadmap.

#	Differentiator	What it changes
1	Media infrastructure sovereignty (self-host)	No "per-minute meter"; marginal cost approaches infrastructure cost
2	Data stays in the Room	Every Room is a compounding knowledge asset owned by the organization
3	No-code composability	Non-programmers build their own digital experiences
4	Local-first, genuine localization	Every market served in its own language — not a translation layer over a product born for another market

4.1. Media infrastructure sovereignty (self-host)

9Zoom operates its own media stack (built on the open-source LiveKit technology) on servers controlled by the team or the customer, instead of renting per-minute cloud media services.

Diagram

Economic meaning: no "per-minute meter" — the marginal cost of a meeting, class, or live session approaches infrastructure cost, not per-minute fees.
Sovereignty meaning: video/audio streams and data are not forced through a third-party cloud.

4.2. Data stays in the Room

Chat, attendance, polls, notes, documents, recordings… are durable data belonging to the Room and the organization — not ephemeral state that evaporates after a call. This turns every Room into a knowledge asset that compounds over time.

4.3. Composability (no-code)

Users attach and detach modules around a Room without programming. This is a democratization philosophy: people who cannot code can still build their own digital experiences — much as no-code platforms democratized website building.

4.4. Genuine localization, local-first

The interface and experience are designed local-first — prioritizing each market's own language on a multilingual architecture from day one — not a translation layer over a product born for another market. Vietnamese is one fully served language among several, not the sole exception.

4.5. Underlying engineering principles

So the content team describes the product accurately:

Server-side authority is separated from client-side display — safety never relies on "hiding buttons".
Business logic is separated from UI for reuse across platforms (mobile, web).
Secrets/keys are never embedded on the client side.
Honesty about scope: anything without a real backend is described as "in development" — no fake numbers.