A better understanding of the Kerberos Ecosystem.
While working in the Kerberos Ecosystem, specific words and sentences become to start feel natural. Unfortunately that’s not the case for everyone, that’s why we added and updated this glossary page, to anyone can come back to this if he would require more detailed explanation.
Chaining or forwarding refers to connecting two Kerberos Vaults. A source Kerberos Vault is connected to a remote Kerberos Vault, and setup in a specific mode: continuous or on-demand forwarding.
A Kerberos Agent is a collection of binaries, shipped in the form of container. It executes specific tasks related to the camera processing, monitoring, configuration and reviewing.
Kerberos Agents are scaled through various deployments:
terraform, etc. The main goal of Kerberos Factory is to serve as a non-technical user interface that allows business users to deploy and manage Kerberos Agents without entering into the complexity of Kubernetes resources.
Kerberos Vault is an interface between Kerberos Agents and a storage system like Minio, S3, Google Storage, Storj and others. It helps decoupling Kerberos Agents from a storage system, and allows you to change a storage system on the fly without reconfiguring your Kerberos Agents. Next to that it allows to build integrations and extensions through messaging (Kafka, SQS, etc) and a Swagger API.
The Kerberos Hub is a single pane of glass that connects your users to groups and/or sites of cameras. It allows you to build a video landscape governance and delegate specific regions or locations to a set of users. It comes with features such as on demand low resolution and high resolution streaming, camera monitoring, alerts and many more.