Start with the Problem
StreamCore SDK and StreamGate both support private video projects, but they solve different problems. StreamCore SDK is embedded into your own application. StreamGate is deployed as an on-prem camera gateway.
When to Choose StreamCore SDK
Choose StreamCore SDK when your team is building or extending an application: desktop software, server-side software, mobile apps, industry terminals, capture tools, or dedicated devices. It provides APIs for playback, capture, publishing, recording, SRT, GB28181, ONVIF, H.264/H.265, hardware decoding, and diagnostics.
When to Choose StreamGate
Choose StreamGate when a site needs to connect and manage cameras, NVRs, GB28181 platforms, existing streams, browser playback, recording replay, and APIs. It is gateway software rather than a library.
Comparison
| Dimension | StreamCore SDK | StreamGate |
|---|---|---|
| Delivery | SDK packages, headers, wrappers, demos | Gateway software and Web Console |
| Primary users | Software teams | Deployment and integration teams |
| Value | Embed media capabilities | Unify on-site video access |
| Licensing | Edition and release platforms | Edition and input channels |
| Search intent | media SDK, RTSP SDK, GB28181 SDK | camera gateway, on-prem video gateway |
Can They Work Together?
Yes. A project may deploy StreamGate on the server side for camera ingest and use StreamCore SDK in client or business software for custom playback, capture, publishing, or interaction.
Decision Method
Use StreamCore SDK when the capability must be embedded into your own application. Use StreamGate when the project needs an installed gateway that manages devices, channels, browser playback, recording replay, playback URLs, and APIs.
Combined Use
Some projects use both: StreamGate handles on-site cameras and recording, while a custom application uses StreamCore SDK for playback, capture, publishing, or a tailored UI.
Licensing Difference
SDK licensing usually follows platform, edition, and host application identity. Gateway licensing usually follows edition and input-channel capacity. Compare delivery form and operations, not only feature names.
Delivery Advice
Let developers evaluate the SDK API, platform packages, demo behavior, and license identity. Let field engineers evaluate installation, channels, recording, browser playback, and operations. Combine both results before purchasing.