Deploying
Choose where your Pops run
A Pop definition is the same wherever it runs. What changes is who operates the machine it runs on.
Runs on
infrastructure EyePop hosts
a machine you control
Media goes
to EyePop
nowhere — it stays on the host
You provision
nothing
one Linux host with Docker
Scaling
on demand
the hardware you have
Best for
getting started, bursty and batch work, production without hardware to run
data that cannot leave your network, cameras on a private LAN, latency at the edge
Most projects start in the cloud. Move on-premise when the media cannot leave your network, or when the hardware is already where the cameras are.
Cloud
Two session types. A transient session, created by the SDK on demand, is the right default while you build. A Deployment is persistent, with your Pop's models pre-loaded, for production latency.
Cloud — how the two compare
Development — connect the SDK and run a first inference
Deployment — create a persistent session and attach to it
Private Cameras — cloud inference for cameras behind a firewall
On-Premise
An instance is the EyePop runtime installed on one machine, serving one Pop. The CLI creates and manages it, and the SDKs reach it in local mode.
On-Premise — create an instance, change its Pop, and run inference against it
VMS
Already running a video management system? A VMS integration runs EyePop next to it and publishes detections back into the VMS, so operators see them in the client they already use.
VMS — how the integrations work, and which VMS are supported
Milestone XProtect — install the EyePop app into the Milestone AI Bridge
Next steps
Last updated