On-prem Is About Control, Not Only Playback
Public cloud media APIs are useful for fast prototypes and internet-facing applications. In government, security, industrial, campus, healthcare, and isolated-network projects, the hard questions are different: where does video travel, can the system run without cloud access, how is licensing handled, and how can the site be diagnosed later?
On-prem deployment keeps media paths, logs, recording, licensing, and operations within the customer-controlled environment.
Cloud vs On-prem Video
| Dimension | Public cloud media service | On-prem SDK or gateway |
|---|---|---|
| Data path | Video often passes through cloud infrastructure | Video can stay inside LAN or private networks |
| Licensing | Account, cloud authorization, or usage billing | Offline license and local runtime |
| Cost model | Traffic, minutes, concurrency, storage | Edition, platform, input channel, or contract scope |
| Operations | Cloud console and vendor support | Local logs, ports, services, hardware, and storage |
| Best fit | Internet applications | Cameras, NVRs, GB28181, and private systems |
When On-prem Fits Better
Choose an on-prem approach when the project cannot rely on public internet access, video must stay within the site, cameras and NVRs are already deployed, GB28181 interconnection is required, users need browser playback inside the LAN, or business systems need local APIs for channels, playback URLs, and recording search.
On-prem Still Requires Planning
The project should confirm server sizing, ports, external address, HTTPS, bitrate, storage, recording retention, GPU or hardware decoding, browser support, and licensing scope. The benefit is that these decisions become explicit and manageable.
HBRun Product Fit
StreamCore SDK is for embedding media capabilities into your own software. StreamGate is for deploying a gateway that manages cameras, browser playback, recording replay, APIs, and local operations.
What to Prepare Before Evaluation
Prepare the network topology, camera count, bitrate range, external access requirements, GB28181 interconnection needs, recording retention, browser viewer scale, third-party API requirements, and licensing model. These inputs make it easier to decide whether the project needs an embedded SDK, a deployable gateway, or both.
Common Misunderstanding
On-prem deployment does not mean the system can only run inside a LAN. It means the runtime, video path, logs, licensing, and operations are controlled by the customer. The system may run in a LAN, private network, edge server, private cloud, or controlled internet-facing environment.
Acceptance Criteria
Check whether video follows the expected path, whether licensing and logs remain usable without cloud dependency, and whether local operators can inspect channels, recordings, ports, certificates, and service status from the console.
Boundaries to Confirm
On-prem does not simply mean LAN-only. It means the runtime, video path, logs, recording, licensing, and operations remain under the customer's control. Confirm which paths may access the internet, which paths must stay local, whether remote access is needed, and what systems need APIs.
Cost and Operations
Cloud cost often comes from traffic, transcoding, storage, concurrency, and managed services. On-prem cost comes from servers, disks, networking, licensing, deployment, and maintenance. The right choice depends on data boundaries, long-term runtime, and operational responsibility.
Acceptance Criteria
Check three things: the video path follows the expected boundary, licensing and logs remain usable without cloud dependency, and local operators can inspect channels, recordings, ports, certificates, and resource status.
Delivery Advice
Treat deployment notes, port lists, license information, log paths, recording directories, and upgrade steps as part of the deliverable. Keep a baseline resource snapshot from acceptance testing for future capacity comparison.