ioMoVo includes a built in CDN, so video in your library is ready to stream without you standing up separate delivery infrastructure.
How playback works
Video is transcoded to HLS for adaptive streaming. That means a viewer gets a quality appropriate to their connection and the player steps up or down as conditions change, rather than stalling on a single large file.
This is what makes review and approval workable for people who are not on the same network as the content. A reviewer on a hotel connection can still watch and comment.
Using your own CDN
The built in CDN is extensible. If you already run a delivery layer, or you have a contractual or performance reason to use a specific provider, you can attach an external CDN rather than replacing the built in one. Cloudinary is one example of a provider teams attach this way.
The usual reasons to bother: you have negotiated delivery rates you want to keep using, you need points of presence in a specific region, or your security team has already approved a particular provider and would rather not review another.
In air gapped and on premise deployments
Streaming works inside your environment. Delivery stays on your network, which is normally the entire point. Sizing the transcoding capacity for your expected volume is worth doing during deployment planning rather than after your first large ingest.
Planning notes
Transcoding is compute work. A large first ingest will take real time, so plan for it
Proxies serve both playback and editorial. Agreeing your proxy settings once, up front, saves regenerating them later
If you are attaching an external CDN, involve whoever owns that contract early