...
Cloud Services
Deployment on the customer’s AWS account takes around about 1 hour. Once the Cloud VMS is deployed, it’s going to work with any number of cameras and scale up and down fully automatically. It will be fully functional through REST API with a swagger published on your end-point:
...
and with Web and Mobile SDKs published on VXG GitHub
White-label
...
Dedicated hosting
The platform can be deployed on a customer’s infrastructure. VXG supports:
Kubernetes
AWS. See more on AWS services used by Cloud VMS
Hybrid deployment
The hybrid deployment assumes deployment of Cloud NVRs of Gateway Servers. The difference between a Cloud NVR and a Gateway Server is that the former performs video recording, while the latter is just relaying video to the cloud. We call this module VXG Server.
VXG provides the VXG Server as a downloadable package for x86 and ARM platforms. The server is offered as a docker container for Linux or an installation package for Windows.
Below are examples of the server h/w requirements:
20 channels @2Mbps – 4GB RAM, Atom CPU
20 channels @2Mbps – 4GB RAM, Raspberry PI 4
50 channels @2Mpbs – 8GB RAM, i3 CPU
...
Web front-end with VSaaS template
The white-label Web front-end with VSaaS template and full source code can be deployed together with Cloud Services or anytime later on a separate EC2 instance or on any customer’s Web server with PHP support. The VSaaS template uses Firebase as an Authentication service. The customer will need to generate Firebase config data. The Web front end has all features of a standard Cloud VMS and is ready for sign-up/in of end users.
...
The Web front can be easily modified to use the customer’s logo, colors, or any specific logic.