Overview

A Gateway serves 2 purposes :

Performs the actual analytic processing either on Edge (on-premise) devices or servers, or on GPU servers in the cloud.
Allows secure access to on-site cameras for configuration and cloud streaming, without opening up ports outside the firewall.

Gateways run Lumeo software on them, and communicate securely to Lumeo's cloud services for command-and-control via the Console or API. Lumeo supports local devices such as Jetson family (NX, AGX, etc.) , and on-prem or cloud based x86 servers with Nvidia GPUs as Gateways.

Lumeo also provides managed Cloud gateways you can use to process video in the Lumeo cloud, without having to setup your own. To provision a Lumeo Cloud gateway on your account, please contact support.

📘
Quickstart
Head on over to Gateway Setup Guide to set up a Lumeo Gateway on your Jetson device, x86 server with Nvidia GPU or a GPU instance in AWS, GCP, Azure, etc.

Hardware Requirements

Overview

The table below outlines various supported hardware and deployment options for Lumeo gateways.

Deployment Mode	Hardware	Hardware Specifications	Benefits	Limitations
On-prem	See Gateway Hardware for a list of supported Gateway hardware devices.	Jetson Xavier, Jetson Orin, x86 Server with Nvidia DGPUs	+ Wide range of hardware options at various price points.	- Requires access to manage and maintain
Lumeo Cloud	Lumeo managed GPU-based Cloud instances	x86 Server with one or more Nvidia DGPUs	+ Best suited for processing camera streams or files accessible via the web (i.e., not behind a on-prem firewall) + Ideal if you have enough bandwidth on site and do not want to deploy on-prem hardware + No need to manage hardware or cloud computing instances	- More expensive vs running on On-prem devices (over a longer period of time) - Cannot access Cameras or content behind on-prem firewalls
Your Cloud	GPU-based Cloud instances	x86 Server with one or more Nvidia DGPUs	+ Ideal if you have enough bandwidth on site, do not want to deploy on-prem hardware, and have technical expertise to manage your own cloud instances	- More expensive vs running on On-prem devices (over a longer period of time) - Cannot access Cameras or content behind on-prem firewalls

The table below outlines video sources & VMS integrations supported by the various deployment modes of a Lumeo Gateway.

Deployment Mode	Supported Video Sources	VMS Integrations	Limitations
On-prem	Cloud-accessible Cameras, Cloud-accessible Recordings, On-prem Cameras & NVRs, On-prem Recordings	Cloud VMS, On-prem VMS
Lumeo Cloud	Cloud-accessible Cameras, Cloud-accessible Recordings	Cloud VMS	Cannot access Cameras or content behind on-prem firewalls without a dedicated VPN setup
Your Cloud	Cloud-accessible Cameras, Cloud-accessible Recordings	Cloud VMS	Cannot access Cameras or content behind on-prem firewalls without a dedicated VPN setup

For information on manufacturers and devices that meet the Gateway Requirements, visit our Recommended Gateway Hardware guide.

Setting Up a Gateway

Setup a new Gateway using the Lumeo Gateway Installer script on your own devices or cloud GPU instances, or use Lumeo-published Gateway machine images for public clouds.

See instructions here : Gateway Setup Guide

Once setup, return to the Console to see it show up in the Gateways list.

You need to ensure the Gateway is able to talk to Lumeo’s cloud services. More info in Security & Network section.

Update Gateways

Once installed, Lumeo will always keep itself up to date on the Gateways, by downloading and installing any updates we publish.

To refresh an installation, you can always re-run the installer from the previous step, and answer No when it asks you if you would like to set is up as a new gateway.

Discover Cameras

Navigate to Gateways → Gateway Name page and you will notice the Gateway automatically attempts to discover IP Cameras on the network, or USB Cameras attached to the Gateway device. If not, at any time you click on Discover and start a discovery process.

For more details on linking the discovered cameras see Camera

API Reference

See gateways