A video or RTC vendor bills on one of three pricing models — a per-minute rate on room time, a per-participant rate on each join, or a pay-as-you-go meter that charges for what the session did — and the model a vendor picks moves total cost of ownership more than any rate printed on a price page. The pricing overview consolidates the industry pricing hub, and the CPaaS pricing models TCO post runs the same arithmetic on messaging. This post works the RTC version: three models, three usage shapes, worked arithmetic, with current unit rates always deferred to the published pricing page. Figures below are illustrative; a model and its trade-offs are what this post teaches, not a quote.
The three models in one table
| Model | What the bill counts | Where it wins | Where it bites |
|---|---|---|---|
| Per-minute (room time) | Minutes a room is open | Chatty, many-participant rooms, predictable duration | Idle open rooms bill like live ones; participant count invisible to the price page |
| Per-participant | Each joiner of a session | Small, fixed-size rooms; telehealth and support | Webinar and audience shapes multiply the bill with headcount |
| Pay-as-you-go meter | What the session did — publish, record, co-browse, AI participant | Programs that mix room shapes; no rate surprises from room size | Requires an account with per-call usage statements to audit |
Model 1 — per-minute of room time
The classic RTC rate card bills the room, not the occupants: open a video room for N minutes, and the bill is N × the per-minute rate regardless of whether two people or forty sat inside. The model wins when the session shape is a chatty room of many participants streaming for a predictable window — a team stand-up, an instructor-led class — because the per-minute number is stable while headcount inside moves. It bites when the room-idle leak appears: a vendor that keeps a room open for a sponsor or a waiting period is billing wall-clock minutes to nobody.
Illustrative arithmetic for a 200-room-month program of 30-minute average sessions: 6,000 room-minutes. At an illustrative room rate of $0.0040 per minute, the room-time line is $24.00 per month regardless of how many joins happened inside those rooms.
Model 2 — per-participant metering
The participant-metered alternative prices the join instead of the room: every head inside a session multiplies the bill, at a per-participant rate that is low enough per join to look cheap at 1:1. The model wins in telehealth and support, where rooms are nominally two people and the session itself is the product. It bites hard on broadcast — an audience of two hundred joiners turns the illustrative $0.0060 per-participant rate into a $1.20-per-session event, where the room-time alternative priced the same session on its duration alone (30 minutes at $0.0040 ≈ $0.12).
Work the two models against each other at the session-shape your program actually runs:
| Session shape | Duration | Joiners | Per-room-minute at $0.0040 | Per-participant at $0.0060 | Cheaper model |
|---|---|---|---|---|---|
| 1:1 support consult | 15 min | 2 | $0.06 | $0.01 | Participant |
| Small onboarding group | 30 min | 6 | $0.12 | $0.04 | Participant |
| Weekly all-hands broadcast | 45 min | 200 | $0.18 | $1.20 | Room-minute |
| Class with audience | 60 min | 40 | $0.24 | $0.24 | Tie |
Illustrative rates only — the crossover point between room-minute and participant-metered billing depends on the actual rate card; current rates live on the pricing page, and the trade-off shape is what this post transfers.
Model 3 — pay-as-you-go metering of what the session did
The third shape prices the metered events a session actually produced — publish and subscribe minutes, recording minutes, co-browse usage, an AI avatar participant's join — as a line-item bill rather than a room or headcount formula. The model wins whenever the program mixes room shapes (support 1:1 on Monday, a 200-seat webinar on Friday) because there is no crossover arithmetic to outrun; the session bills for what it did. It bites at audit time: a pay-as-you-go bill is auditable only when the account emits per-call usage statements that name what was metered.
Devotel Orbit's model is pay-as-you-go — the video room, its recording, its co-browse, and an AI avatar participant all meter on the same account as the voice, SMS, WhatsApp, RCS, and email channels around them. One pay-as-you-go bill, with per-event statements on the dashboard, rather than a video vendor stacked as a separate line next to the messaging and email vendors.
The rule of thumb
Pick the model by session shape, not the unit rate. Probe the program: if the answer is "mostly 1:1 or small fixed rooms," a participant-metered rate card wins; if it is "audiences of unknown size," room-minute pricing wins; if it is "both, on the same account," a pay-as-you-go meter on an all-in-one account wins by absorbing the shape variance without crossover arithmetic. Every real program of any age drifts toward the third shape.
Frequently asked questions
Where are Orbit's actual unit rates for video and RTC?
On the published pricing page. Orbit publishes its rates the way the rest of the account is published — the rate card the buyer checklist uses, not behind a sales call. The illustrative figures above ($0.0040 per room-minute, $0.0060 per participant) exist to make the crossover arithmetic concrete; they are not Orbit's rates.
Does the room-time or participant-metered bill include recording and co-browse?
Usually no — recording and co-browse meter separately on most vendor price pages, which is why the pay-as-you-go model is the honest comparison shape: it names every metered event the session produced rather than attaching a room or headcount formula that hides the extras.
Is a free tier or sandbox the same as a pricing model?
No. A free tier is a rate-card event (the first N units free), not a billing model. The model is which things the meter counts (room time, joins, session events); the free tier adjusts the first N of whatever the model counts. Both questions are settled on the vendor's publishing pricing page before any TCO exercise.
Published 21 September 2026.