An audience can share one live programme without receiving it through one identical route. Speakers may need interactive delivery. A large audience may need a path designed for scale. A constrained viewer may need a lower bandwidth continuity mode. The delivery path can vary while identity, timing and authoritative state remain coherent.
TL;DR
- Deliver selects an approved route according to participant role, latency, scale, network, device and experience requirement.
- Route Preflight identifies likely browser, permission, firewall, VPN, proxy and relay constraints before admission.
- Experience Router can choose among certified interactive, low latency, regional, CDN and packaged delivery paths.
- Path changes preserve participant identity, authority, captions, presentation state, interactions and live timing.
- Eligible sessions can move between approved regions or providers without claiming impossible zero interruption.
- One audience needs one coherent programme, not one physically identical delivery path.
Delivery is a role decision
A presenter, moderator and viewer may belong to the same session but have different delivery obligations. Presenters need timely contribution and return media. Moderators need current state and control. Viewers need an experience appropriate to the promised scale and participation model.
Using one route for every role can make the system simpler on paper and less dependable in practice. An interactive path may not be the most economical way to serve a large passive audience. A packaged path may not provide the responsiveness required for a speaker. Deliver treats the role and expected experience as part of the route decision.
The route remains subordinate to the session. It does not create a second identity or a different version of the programme.
Preflight before admission
Some delivery problems can be identified before the participant enters. Route Preflight checks the conditions that commonly affect joining and media transport, including browser readiness, camera and microphone permissions, VPNs, corporate firewalls, proxies, relay requirements and bounded upload or download capability.
The purpose is not to guarantee that the future route will never change. It is to make the initial recommendation safer and to give the participant useful recovery guidance before failure becomes part of the live experience.
A preflight result should include uncertainty. A short test cannot prove every future condition. It can identify evidence, recommend an approved path and explain which fallback may be needed.
Route the experience, not only the packets
Experience Router selects among the certified delivery paths available to the participant and customer configuration. Those paths may include interactive WebRTC, low latency delivery, regional routing, CDN delivery, packaged streaming or an approved provider alternative.
The choice considers more than reachability. Participant role, expected latency, network conditions, device capability, privacy, scale, accessibility and cost authority all matter. A route that is technically available may still be inappropriate for the expected experience.
This is why routing belongs inside a governed media product rather than as a collection of unrelated provider links.
Prioritizes timely contribution and response for participants who need to speak or operate the session.
Serves larger viewing groups through an approved route suited to scale and the promised participation model.
Preserves useful speech and authoritative state when the primary path is no longer practical.
Moves eligible participation to an approved region or provider when policy and operating conditions permit.
One live clock across paths
Different paths can introduce different delays. Without one live clock, captions can drift from speech, slide changes can arrive before or after the explanation and timed interactions can become unfair.
The Unified Live Clock relates audio, human video, screen sharing, slides, captions, polls, reactions, overlays, calls to action, recording and replay markers to one authoritative timeline. A participant who changes routes converges on current state rather than replaying obsolete events.
The objective is not to make physics disappear. It is to keep material differences visible, controlled and related to one programme.
Fairness when timing differs
A small live offset may be acceptable for passive viewing and significant for a timed poll or moderated response. Fairness Clock measures material differences between participants against the customer’s configured tolerance.
Where the experience requires it, the system may add a small controlled delay to faster viewers rather than allowing one group to receive a timed opportunity earlier. This behavior must be explicit and measurable. It should never be hidden as a vague claim that everyone is perfectly synchronized.
Fairness is therefore a product policy supported by delivery evidence, not an assumption that every route has equal latency.
Migration with honest boundaries
An approved provider or region can become unsuitable during a session. Seamless Provider and Region Migration allows eligible sessions or participants to establish a replacement path before retiring the earlier one where the environment supports it.
Identity, roles, presentation state, interactions, captions, live position, encryption authority, recording lineage, usage ownership and audit evidence must remain connected to the same session. The migration should not create duplicate privileged participation or split the authoritative state.
The product does not claim impossible zero interruption. It exposes bounded interruption honestly and records whether the replacement restored the required experience.
Cross device handoff is also delivery
Sometimes the better path is another device. Cross Device Session Handoff lets an authorized participant move the live experience without losing identity, admission, role, captions, presentation state, interactions, delivery preferences or synchronization.
Where possible, the new device receives authority before the old device is retired. Controls prevent token reuse, duplicate privileged participation and unintended concurrent publishing. The goal is a continuation of the same participation, not a new participant joining with copied access.
This makes device choice part of experience continuity while keeping security and session authority intact.
Questions to ask about delivery
- Which participant roles require interactive delivery and which can use an audience path?
- What does preflight test before a participant is admitted?
- Can delivery change without losing identity, captions, slides or interaction state?
- How are latency differences measured for polls and other time sensitive activity?
- Which providers, regions and routes are approved for the customer’s environment?
- What privacy and cost authority applies before a fallback route is used?
- Can a participant move to another device without creating duplicate privilege?
- How does the system describe interruption and recovery without claiming perfection?
Summary
One audience does not require one delivery path. Deliver selects certified paths according to role, scale, network, device, privacy and timing requirements while the programme retains one identity and one authoritative clock.
Preflight, experience routing, fairness controls, provider or region migration and cross device handoff make delivery more flexible without allowing the route to own the product experience.
Frequently asked questions
What does Deliver do?
Why would one webinar use more than one delivery path?
What is Route Preflight?
Can cRUD Morph move a live session to another provider or region?
Does route selection override privacy or cost controls?
About this article. It explains the public role of Deliver and related routing capabilities within cRUD Morph. It does not promise that every provider, region, transport, migration or handoff is available in every engagement. Scope and operating commitments are confirmed during the technical engagement.