diff --git a/content/_index.md b/content/_index.md index db0c767..cdc2692 100644 --- a/content/_index.md +++ b/content/_index.md @@ -17,47 +17,45 @@ The **Kerberos.io** project, pronounced as `/kuh buh ruhs dot ai o/`, is a video [![An Introduction to Kerberos.io](youtube-introduction-kerberosio.png)](http://www.youtube.com/watch?v=LjCaMMKJCGc "An Introduction to Kerberos.io") -Kerberos.io scales from small home deployments to large scale enterprise deployments. To set the expectations of what is possible and how, it's recommended to have a look [at the deployments page](/prologue/deployments/) to find the most suitable architecture for your use case. +Next to being stable and feature-rich, Kerberos.io's main differentiator is scale. It helps you moving from a small home deployment to a large scale enterprise deployment. To illustrate the art of the possible, we recommend to have a look [at the deployments page](/prologue/deployments/) to find out the most suitable architecture for your use case. ## The name: Kerberos.io Many people are confused, and don't understand why this project is called Kerberos.io. If you've been in the IT world for a while you will notice that Kerberos is already used for the authentication protocol [Kerberos](). -After all those years, we still believe that the name Kerberos.io makes sense for this project as well. With a strong emphasize on the suffix **.IO**, which stands for any **(I) input** of camera, and any **(O) output** such as a webhook, bash script, mqtt, etc. Kerberos itself is keeping an eye, using the configured input, and triggers the required outputs. +After all those years, we still believe that the name Kerberos.io makes sense for this project. With a strong emphasize on the suffix **.IO**, which stands for any **(I) input** of camera, and any **(O) output** such as a webhook, bash script, mqtt, etc. Kerberos itself is keeping an eye, using the configured input, and triggers the required outputs. ## What is Kerberos.io -Kerberos.io is a video analytics and monitoring platform, that is focussing on both end-consumer and enterprises. It comes with modular solutions to support small deployments, a couple of camera streams and larger deployments, with multiple sites and thousands of camera streams. +[Kerberos.io](/prologue/how/) is a video analytics and monitoring platform for everyone, from a traditional user to a multinational corporation, we have different solutions and components to help you grow. + +Within the portfolio of [Kerberos.io](/prologue/how/) you leverage more or less components depending on the stage you are in, there is no need to overcomplicate things. The backbone of the Kerberos.io ecosystem is the [Kerberos Agent](/agent/first-things-first/). This [Kerberos Agent](/agent/first-things-first/), installed [through various possibilities](https://github.com/kerberos-io/agent#how-to-run-and-deploy-a-kerberos-agent), is deployed to a compute - VM, baremetal, Kubernetes cluster or other - of choice and connected to a camera stream you control. {{< figure src="introduction-kerberos-io.svg" alt="A Kerberos Agent is monitoring a single camera stream." caption="A Kerberos Agent is monitoring a single camera stream." class="stretch">}} -With Kerberos.io you start small, with just one or more [Kerberos Agents](/agent/first-things-first/), and grow over time while introducing more and more components like [Kerberos Factory](/factory/first-things-first/), [Kerberos Vault](/vault/first-things-first/) and [Kerberos Hub](/hub/first-things-first/); which we refer to as the [Kerberos Enterprise Suite](/enterprise/first-things-first/). Each solution is shipped through the concept of containers and can be leveraged by using Docker, Docker compose, Kubernetes, OpenShift, Terraform, Ansible, and many more. +With [Kerberos.io](/prologue/how/) you start small, with just one or more [Kerberos Agents](/agent/first-things-first/), and grow over time while introducing more and more components like [Kerberos Factory](/factory/first-things-first/), [Kerberos Vault](/vault/first-things-first/) and [Kerberos Hub](/hub/first-things-first/); which we refer to as the [Kerberos Enterprise Suite](/enterprise/first-things-first/). Each solution is shipped through the concept of containers and can be leveraged by using Docker, Docker compose, Kubernetes, OpenShift, Terraform, Ansible, and many more. {{< figure src="./introduction-enterprise.svg" alt="A scalable video platform for an ever-growing video landscape." caption="A scalable video platform for an ever-growing video landscape." class="stretch">}} +As previously mentioned, the [Kerberos Enterprise Suite](/enterprise/first-things-first) brings additional components into the picture which help you build a more scalable and resilient video landscape through concepts such as Kubernetes, bring you own storage, bring your own cloud, single-pane of glass, live streaming, machine learning, etc. + ## Why Kerberos.io -Kerberos.io initiated as a side project, due to inspiration and motivation in the space of video analytics, computer vision and machine learning. Its first focus was video surveillance only, as nowadays burglary or attacks are very common in this world. +Kerberos.io initiated as a side project, due to inspiration and motivation in the space of video analytics, computer vision and machine learning. Its first focus was video surveillance only, as nowadays burglary and attacks are very common in this world. -Due to this, our first mission is to provide every human being on this planet with a solution, a video platform, to protect its families, friends, homes or anything else which you think is important. - -Our second mission is to make this video platform affordable and Open Source (MIT), and develop it in such a way, that it's using the latest technologies, to create a seamless, never-seen and delicious user experience. - -While we move forward our third mission is to scale, and make Kerberos.io reach far beyond a traditional video platform. With the rise of the [Kerberos Enterprise Suite](/enterprise/first-things-first), we allow our users to scale from a home deployment to a full-blown production ready deployment; covering thousands of cameras. +Over time we have grown an amazing commmunity, collaborated with lots of international companies and received a lot of kudos for the work we've done. To consolidate our efforts, [we have written down our mission statement](/prologue/mission/), which explains why this projects exists. ## Integration and extension -The majority of VMS systems out there are owned by multi-national manufacturers who are building closed systems which, as an hobbiest or professional, are unaccessible in any programmatical way; such as a REST API. This forced people to create workarounds (headless browser) to fetch the desired data from the NVRs or cameras. +The majority of video management platforms out there are owned by multinational manufacturers that are building closed systems which are unaccessible in any programmatical way; such as an API. This forces anyone to create unsupported workarounds, which become outdated very quickly. The whole idea behind Kerberos.io is to challenge previous statement. > We want open and integratable systems for anyone and anywhere. You generate the data, you own the data. -The response of Kerberos.io is, that any solution you'll find in our portfolio allows you to integrate and extend by default; no work-a-rounds, the data that is in our solutions belongs to you. +The response of Kerberos.io is, that any solution you'll find in our portfolio allows you to integrate and extend by default, no workaround, the data belongs to you. We expose Swagger APIs by default, to extract all the data you desire. -You decide where (cloud, self-hosted) and how (Docker, Kubernetes, OpenShift, Terraform, etc) to deploy our solutions, what storage you want (local SSE, S3, etc), how to integrate it with other third-party solutions (Kafka, SQS, etc). - -If you want to build your own application, you can use the Swagger APIs we ship by default, and will allow you to build your own applications or integrations, without any limitations. +You decide where (cloud, self-hosted) and how (Docker, Kubernetes, OpenShift, Terraform, etc) to deploy our solutions, what storage you prefer (local SSE, S3, etc) and how to integrate it with other third-party solutions (Kafka, SQS, etc). ## Machine learning diff --git a/content/introduction-enterprise.svg b/content/introduction-enterprise.svg index 082064f..4602880 100644 --- a/content/introduction-enterprise.svg +++ b/content/introduction-enterprise.svg @@ -1,191 +1,96 @@ - + - - - - - - - - - - - - - - - - - - - - + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + - - - - - - - - - - + + + + - + - - - - - + + + + - + - - - - - + + + + - + - - - - - + + + + - + - - - - + + + + + + + + + + + + + + + + + + + + + - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - + @@ -199,7 +104,7 @@ - + @@ -213,7 +118,7 @@ - + @@ -227,7 +132,7 @@ - + @@ -241,7 +146,7 @@ - + @@ -255,7 +160,7 @@ - + @@ -269,7 +174,7 @@ - + @@ -283,7 +188,7 @@ - + @@ -297,170 +202,8 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + diff --git a/content/prologue/how/agents-to-vault.svg b/content/prologue/how/agents-to-vault.svg new file mode 100644 index 0000000..d814e37 --- /dev/null +++ b/content/prologue/how/agents-to-vault.svg @@ -0,0 +1,308 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/content/prologue/how/index.md b/content/prologue/how/index.md index 9bbefe8..5f3b069 100644 --- a/content/prologue/how/index.md +++ b/content/prologue/how/index.md @@ -1,9 +1,9 @@ --- title: "How it works" -description: "How Kerberos.io works, and the different building blocks." -lead: "How Kerberos.io works, and the different building blocks." +description: "From one to a myriad of cameras" +lead: "From one to a myriad of cameras" date: 2020-10-06T08:48:57+00:00 -lastmod: 2020-10-06T08:48:57+00:00 +lastmod: 2022-12-14T22:37:57+00:00 draft: false images: ["camera.png"] menu: @@ -13,24 +13,56 @@ weight: 102 toc: true --- -A [Kerberos Agent](/agent/first-things-first/), is a piece of software that is responsible for monitoring a single camera stream. It contains two pieces: a front-end and a back-end. The back-end processes the video stream, applies computer vision techniques, makes recordings and takes actions (for example sending notifications). The front-end allows you to review recordings, and configure specific settings for the back-end. +As described at the [introduction page](/) and [mission statement](/prologue/mission/), Kerberos.io has a strong vision and roadmap to help anyone on this planet to setup a video management platform to fit its needs. In this section we'll describe the different building blocks and illustrate how they complement and enrich each other, to build up an [ideal deployment model](/prologue/deployments/). + +## The Kerberos Agent + +At the foundation of any Kerberos.io deployment you'll find one or more [Kerberos Agents](/agent/first-things-first/). These Kerberos Agents are installed [through various possibilities](https://github.com/kerberos-io/agent#how-to-run-and-deploy-a-kerberos-agent) and are deployed to a compute - VM, baremetal, Kubernetes cluster or other - of choice and connected to camera streams you control. {{< figure src="agent-explanation.svg" alt="A Kerberos agent consists of both a backend en frontend." caption="A Kerberos agent consists of both a backend en frontend." class="stretch">}} -## Kerberos Vault +The Kerberos Agent is responsible for a single camera. It is a piece of software which has two responsibilities: it acts as an user interface (frontend) and an API (backend). The API processes the video stream, applies computer vision techniques, makes recordings and takes desired actions; e.g. a webhook. On the otherhand, the user interface allows a user to review recordings and configure specific settings for the API. -End-consumer or enterprises which only have a few camera streams to manage, probably will be fine with just one or more [Kerberos Agents](/agent/first-things-first/). If remote access is required they could also benefit from the [Kerberos Hub Saas offering](/hub/first-things-first). +The Kerberos Agent itself is bundled in a single container, which includes all the dependencies and libraries required to have it running. For each camera, a Kerberos Agent container will be created. -As soon you will process more [Kerberos Agents](/agent/first-things-first/), it will become interesting to manage your own central storage through [Kerberos Vault](/vault/first-things-first/). If you want to bring your own integrations or machine learning models than [Kerberos Vault](/vault/first-things-first/) is also the way forward. +{{< figure src="introduction-kerberos-io.svg" alt="A Kerberos Agent is monitoring a single camera stream." caption="A Kerberos Agent is monitoring a single camera stream." class="stretch">}} -{{< figure src="vault-edge-cloud-storage.svg" alt="Bring your own storage using Vault" caption="Bring your own storage using Kerberos Vault" class="stretch">}} +The appealing thing with this approach is that you'll experience complete isolation. If one Kerberos Agent goes down, it will not affect any other Kerberos Agent (or camera). It also makes it elegant to scale. -## Kerberos Hub +## Scaling out Kerberos Agents + +Starting with a few Kerberos Agents, is straight forward. Scaling your Kerberos Agents is not a complex task as well, you can benefit [from the different deployments models](https://github.com/kerberos-io/agent#how-to-run-and-deploy-a-kerberos-agent) we have documented. + +{{< figure src="scaling-out.svg" alt="Scaling out your Kerberos Agents is not a complex task." caption="Scaling out your Kerberos Agents is not a complex task." class="stretch">}} + +Depending on your scenario [you choose one deployment over the other](https://github.com/kerberos-io/agent#how-to-run-and-deploy-a-kerberos-agent), however there is no golden rule, you should move forward with what you prefer and have experience with. A few examples: + +- If you are not into `kubernetes`, and you have only a dozen of cameras, it might be more suitable to utilise `docker compose`. + +- On the other hand if you have hundreds of cameras, and plan to install more over the next months and years, you will benefit from the elasticity `kubernetes` provides to you out of the box. + +- If you rather have non-technical users managing a video landscape, than [Kerberos Factory](/factory/first-things-first/) might be a good choice. + +Whatever you choose, you can always migrate from one option to the other, it's just the engine on which the Kerberos Agent containers are running is updated. + +## Storing data where you want + +Kerberos Agents are responsible for storing recordings and triggering events. By default all recordings are stored within the Kerberos Agent container, this means that if the containers stops, all your data will be lost. Luckily [there are a couple of techniques to persist](https://github.com/kerberos-io/agent#configure-and-persist-with-volume-mounts) the data outside the container, without losing any information. + +In most cases, especially with a growing video landscape, it's more convenient to have a central storage system in place that scales, like Ceph, Minio, or cloud storage like S3 and other blob storage. This is exactly, where Kerberos Vault comes into the picture. + +{{< figure src="agents-to-vault.svg" alt="Bring your own storage using Kerberos Vault" caption="Bring your own storage using Kerberos Vault" class="stretch">}} + +[Kerberos Vault](/vault/first-things-first/) acts like a interface between your Kerberos Agents and your storage system. It is responsible for receiving recordings from your Kerberos Agents, and storing them in the right storage system you've configured. By decoupling your Kerberos Agents with [Kerberos Vault](/vault/first-things-first/), you can switch your underlaying storage system on the fly. + +Next to persisting your data in your storage system, [Kerberos Vault](/vault/first-things-first/) also acts as an event producers. Each time a recording is successfully stored in your storage system, it will send a message to the configure [Integration](/vault/integrations/), such as Kafka, SQS, etc. + +## Centralise your video landscape One or more [Kerberos Agents](/agent/first-things-first/) are perfect for a small scale deployment. The disadvantage, when running a couple of Kerberos Agents, is that an agent is designed to handle a single camera stream. This means if you would like to have an overview of all your [Kerberos Agents](/agent/first-things-first/), you will need to open multiple interfaces or build something yourself. Another disadvantage is the network, typically a Kerberos Agent is on a local network, and not accessible from the internet. This requires port-forwarding, or a VPN tunnel to properly secure and access them. {{< figure src="hub-with-vault.svg" alt="Kerberos Vault connected to Kerberos Hub." caption="Kerberos Vault connected to Kerberos Hub." class="stretch">}} -To overcome these disadvantages a tool, [Kerberos Hub](/hub/first-things-first/), was developed that allows to connect a couple, or a thousand of video stream to a single pane of glass. The idea is that you can use either the [Kerberos Hub Saas offering](/hub/first-things-first/) or the [Kerberos Hub self-hosted](/hub/first-things-first/) version, depending on your needs. +To overcome these disadvantages a tool, [Kerberos Hub](/hub/first-things-first/), was developed that allows to connect a couple, or a thousand of video stream to a single pane of glass. The idea is that you can use either the [Kerberos Hub Saas offering](/hub/first-things-first/) or the [Kerberos Hub self-hosted](/hub/first-things-first/) version, depending on your needs. [Kerberos Hub](/hub/first-things-first/) comes with features to manage cameras in groups or sites, view livestreams, delegate access of a subset of cameras to specific accounts, filtering through machine learning, etc. diff --git a/content/prologue/how/introduction-kerberos-io.svg b/content/prologue/how/introduction-kerberos-io.svg new file mode 100644 index 0000000..db471b1 --- /dev/null +++ b/content/prologue/how/introduction-kerberos-io.svg @@ -0,0 +1,2008 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/content/prologue/how/scaling-out.svg b/content/prologue/how/scaling-out.svg new file mode 100644 index 0000000..56030c3 --- /dev/null +++ b/content/prologue/how/scaling-out.svg @@ -0,0 +1,445 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/content/prologue/mission/index.md b/content/prologue/mission/index.md index 7563822..e342470 100644 --- a/content/prologue/mission/index.md +++ b/content/prologue/mission/index.md @@ -13,10 +13,10 @@ weight: 104 toc: true --- -Kerberos.io initiated as a side project, due to inspiration and motivation in the space of video analytics, computer vision and machine learning. Its first focus was video surveillance only, as nowadays burglary or attacks are very common in this world. +We want to provide every human being on this planet with a free-of-charge solution, a video platform, to protect its families, friends, homes, or anything it cares for, in the form of Open Source; MIT license. -Due to this, our first mission is to provide every human being on this planet with a solution, a video platform, to protect its families, friends, homes, etc in the form of open source (MIT license). +We develop our solutions in such a way, that it’s using the latest technologies and best-practices, to create a seamless, never-seen and delicious user experience in the space of video management, video analytics and video surveillance. -Our second mission is to make this video platform affordable and Open Source (MIT), and develop it in such a way, that it’s using the latest technologies, to create a seamless, never-seen and delicious user experience. +Our mission is to reach far beyond the traditional video platforms we experiencing nowadays. We have a strong focus to simplify the process of scaling, going from a simple home deployment to a large scale production deployment with thousands of cameras. -While we moved forward our third mission is to scale, and make Kerberos reach far beyond a traditional video platform. With the rise of Kerberos Enterprise Suite, we now focus on large scale deployments (covering thousands of cameras), and video intelligence through machine learning. +While moving on, and leveraging our skills to scale, we are experimenting and implementing video analysis that are linked to optimise specific use case: people tracking, license plate recognition, people counting, etc. These concepts will/are be integrated in the various components of the Kerberos.io portfolio.