mirror of
https://github.com/kerberos-io/documentation.git
synced 2026-08-23 15:18:31 +00:00
add introduction and how it works
This commit is contained in:
cedricve
@@ -13,26 +13,34 @@ weight: 100
|
||||
toc: true
|
||||
---
|
||||
|
||||
The **Kerberos.io** project, pronounced as `/kuh buh ruhs dot ai o/`, is a video surveillance solution, which was initiated back in 2014. Over the years it has evolved into a trusted, stable and feature-rich video surveillance system. To set the expectations, watch the video below to understand what it can and can't do. If you want to install Kerberos.io, it's recommended to have a look [at the architectures page](/prologue/deployments/) to find the best solution for your usecase.
|
||||
The **Kerberos.io** project, pronounced as `/kuh buh ruhs dot ai o/`, is a video analytics and video management platform, which was initiated back in 2014. Over the years it has evolved into a stable and feature-rich video platform, which is used for management and analytics such as machine learning.
|
||||
|
||||
{{< vimeo id="382090189" class="responsive-video ratio-16by10" title="Kerberos introduction" >}}
|
||||
To set the expectations of what is possible and how, it's recommended to have a look [at the architectures page](/prologue/deployments/) to find the best, or most reasonable architecture for your use case.
|
||||
|
||||
## The name: Kerberos.io
|
||||
## 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](https://en.wikipedia.org/wiki/Kerberos_(protocol)).
|
||||
|
||||
We believe that the name Kerberos.io makes sense for this project as well, with a strong emphasize on the suffix **.io**, which stands for input and output devices (e.g. any type of camera). Kerberos.io can be seen as a kind of security protocol driven by hardware devices such as surveillance cameras. To make writing easier we will from now on, refer to Kerberos instead of Kerberos.io.
|
||||
We believe that the name Kerberos.io makes sense for this project as well, with a strong emphasize on the suffix **.io**, which stands for input and output devices (e.g. any type of camera). Kerberos.io can be seen as a kind of security protocol for images and recordings.
|
||||
|
||||
## Why Kerberos
|
||||
## Why Kerberos.io
|
||||
|
||||
As burglary is very common, we believe that video surveillance is a trivial tool in our daily lifes which helps us to feel a bit more secure. Responding to this need, a lot of companies have started developing their own video surveillance software in the past few years.
|
||||
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.
|
||||
|
||||
Nowadays we have a myriad of expensive cameras, recorders, and software solutions which are mainly outdated and difficult to install and use. Kerberos goal is to solve these problems and to provide every human being or enterprise in this world to have their own ecological, affordable, easy-to-use and innovative surveillance solution.
|
||||
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).
|
||||
|
||||
## What is Kerberos
|
||||
Our second mission is to make this video platform in such a way, that its high-tech and using the latest technologies and UX, to create a seamless, never-seen and delicious user experience.
|
||||
|
||||
Kerberos is a video surveillance solution, that uses computer vision algorithms to detect changes, and that can trigger actions (notifications, api, etc). It comes in two flavors, Kerberos Open Source and Kerberos Enterprise. Kerberos can be deployed to any ARM device, Linux OS, Docker, Balena Cloud, or cluster such as Kubernetes.
|
||||
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.
|
||||
|
||||
### Kerberos Agent
|
||||
## What is Kerberos.io
|
||||
|
||||
When you install Kerberos Open Source or Kerberos Enterprise we will refer to it as the Kerberos agent. A Kerberos agent, is a software solution that processes the video stream of a single surveillance camera, makes and visualises recordings and takes actions (for example sending notifications).
|
||||
Kerberos.io is a video analytics and monitoring platform, that is focussing on both end-consumer as enterprises. It comes with different solutions to support small deployments, a couple of camera streams and larger deployments, with multiple sites and thousands of camera streams.
|
||||
|
||||
With Kerberos.io you start small with one or more [Kerberos Agents](/opensource/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 is coined the [Kerberos Enterprise Suite](/enterprise/first-things-first/). Kerberos.io is shipped through the concept of container technology such as Docker and Kubernetes, and implements the ideas of bring your own cloud, bring your own storage and bring your own technology.
|
||||
|
||||
{{< figure src="./kerberos-global.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">}}
|
||||
|
||||
The whole idea is that any solution you will find at Kerberos.io, is extensible and allows you to integrate by default. For example, you decide where to deploy the solutions (edge/cloud/hybrid), what storage you want (edge/cloud/hybrid), how to integrate it with other third-party solutions, etc. Every solution you'll find in the Kerberos.io space, ships Swagger APIs by default, and will allow you to build your own applications or integrations.
|
||||
|
||||
Machine learning and Artificial Intelligence is a critical component of the Kerberos.io ecosystem. Within Kerberos Vault you can integrate your own machine learning models, and run them at scale. [Learn more about how we support](/vault/machine-learning/) machine learning use cases.
|
||||
|
||||
581
content/kerberos-global.svg
Normal file
581
content/kerberos-global.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 601 KiB |
@@ -13,42 +13,22 @@ weight: 102
|
||||
toc: true
|
||||
---
|
||||
|
||||
When you install Kerberos Open Source or Kerberos Enterprise we will refer to it as the Kerberos Agent. A Kerberos Agent, is a software solution that consist of two pieces: Front-End and Back-End. The Back-End processes the video stream of a single surveillance camera, makes recordings and takes actions (for example sending notifications). The Front-End allows you to review recordings, and configure the Back-End.
|
||||
A [Kerberos Agent](/opensource/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.
|
||||
|
||||
{{< 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">}}
|
||||
|
||||
## Front-End
|
||||
The Kerberos Agent ships with a web interface (Front-End) and a video processing engine (Back-End). The Front-End allows the user to modify specific settings, and if Kerberos Open Source, watch recordings in a easy-to-use interface; The Front-End for [Kerberos Enterprise](/enterprise/introduction) is only for configuration purposes only.
|
||||
|
||||
## Back-End
|
||||
The Back-End piece of the Kerberos Agent is a service that processes the camera feed with computer vision algorithms to detect motion, and makes recordings and/or execute specific actions. Kerberos Enterprise supports any type of IP-camera (RTSP/ONVIF), and Kerberos Open Source also adds support for USB (V4L2) and the popular Raspberry Pi camera.
|
||||
|
||||
Depending on which Kerberos Agent, Kerberos Open Source or Kerberos Enterprise, you will have different installation methods. If you would like to learn more about the Kerberos Agent, have a look in the related sections: [Open Source](/opensource/introduction), [Enterprise](/enterprise/introduction).
|
||||
|
||||
## Open Source vs Enterprise
|
||||
|
||||
The Kerberos project started as an Open Source project, with a main focus on low-cost devices such as the Raspberry Pi. Later on the Open Source version was bundled inside the Docker technology so that it was easier to distribute. Anyone can use the Open Source version for personal usage.
|
||||
|
||||
Enterprises are more demanding, and have a lot of surveillance cameras, therefore they need a scalable surveillance system. The [Enterprise edition](/enterprise/introduction) of Kerberos allows you to operate a video surveillance cluster (Kubernetes) on-premise or in the cloud (AWS/GCP/Azure).
|
||||
|
||||
{{< figure src="opensource-vs-enterprise-agent.svg" alt="The different deployment options for Opensource and Enterprise agent." caption="The different deployment options for Opensource and Enterprise agent." class="stretch">}}
|
||||
|
||||
The Open Source and Enterprise edition are significantly different from a source code point of view. The [Enterprise edition](/enterprise/introduction) is a complete rewrite of the Open Source version, and got all the best practices we discovered over the years implemented. Both version are and will remain updated in the future.
|
||||
|
||||
## Kerberos Vault
|
||||
|
||||
Users or Enteprises which only have a few surveillance cameras to manage, probably will be fine with Kerberos Open Source. On top of that they might include [Kerberos Cloud](/cloud) for remote access and monitoring.
|
||||
End-consumer or enterprises which only have a few camera streams to manage, probably will be fine with just one or more [Kerberos Agents](/opensource/first-things-first/). If remote access is required they could also benefit from the [Kerberos Hub Saas offering](/hub/first-things-first).
|
||||
|
||||
On the other hand if you plan to manage a larger network of surveillance cameras, you will have to look into [Kerberos Enterprise](/enterprise/introduction). Backed up with Kubernetes, Kerberos Enterprise, will give you the real super powers to your scale surveillance camera landscape. Kerberos Enterprise comes with a Front-End to manage and scale your deployments inside a Kubernetes Cluster.
|
||||
As soon you will process more [Kerberos Agents](/opensource/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.
|
||||
|
||||
[Kerberos Enterprise](/enterprise/first-things-first) leverages a service called, [Kerberos Vault](/vault/introduction), for central and hybrid storage. Kerberos Vault implements the concept of BYOC (Bring Your Own Cloud). By selecting a cloud provider (AWS, GCP, AZURE) or on-premise (Minio) you can bring your recordings where you them to be.
|
||||
|
||||
In addition to the concept of BYOC, Kerberos Vault enables you to connect to Kerberos Cloud (with your own storage), send events to message brokers (such as Kafka or SQS) and enables you to build custom apps or services (such as a custom machine learning service).
|
||||
|
||||
{{< figure src="deployment-vault.svg" alt="Kerberos Vault allows you to bring your own storage, and build extensions and integrations." caption="Kerberos Vault allows you to bring your own storage, and build extensions and integrations." 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">}}
|
||||
|
||||
## Kerberos Hub
|
||||
|
||||
When installing a Kerberos Agent inside your local network, it's possible to review your activity by using the agent its web interface. By all network principles, having a local setup, you will not be able to access the web interface from the cloud (outside your local network). On top of that, the Kerberos Agent doesn't come with a consolidated overview. This means that you will need to open multiple web interfaces, one for each connected surveillance camera. To simplify and resolve all of these challenges, [Kerberos Cloud](/cloud) was developed.
|
||||
One or more [Kerberos Agents](/opensource/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](/opensource/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="deployment-hub.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">}}
|
||||
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.
|
||||
|
||||
627
content/prologue/how/vault-edge-cloud-storage.svg
Normal file
627
content/prologue/how/vault-edge-cloud-storage.svg
Normal file
File diff suppressed because one or more lines are too long
|
After Width: | Height: | Size: 131 KiB |
@@ -13,4 +13,10 @@ weight: 104
|
||||
toc: true
|
||||
---
|
||||
|
||||
The mission of Kerberos.io is to provide everyone on this planet with an affordable and revolutionary video surveillance system. We want every human being or enterprise to secure it's family, property(ies), organisations or anything he finds important.
|
||||
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.
|
||||
|
||||
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).
|
||||
|
||||
Our second mission is to make this video platform in such a way, that its high-tech and using the latest technologies and UX, to create a seamless, never-seen and delicious user experience.
|
||||
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user