diff --git a/content/enterprise/first-things-first.md b/content/enterprise/first-things-first.md
index c4b26fd..4af2f7e 100644
--- a/content/enterprise/first-things-first.md
+++ b/content/enterprise/first-things-first.md
@@ -38,7 +38,7 @@ The major key differentiators compared to to other solutions are:
To provide our customer with the high availability and fail over requirements they have, Kerberos Enterprise was built on top of Kubernetes (k8s). This container orchestrator allows us to scale a video surveillance landscape horizontally, and deliver a never-seen high available video surveillance system.
-
+
Kerberos Enterprise is installed inside a Kubernetes cluster. It will create pods/deployments for every surveillance camera you want to monitor. Kubernetes will scale and distrubute these pods across your nodes (VM's/Baremetal machines).
@@ -50,7 +50,7 @@ By having the power to add nodes to your cluster, you can anticipate to the ever
You install Kerberos Enterprise inside a Kubernetes cluster, but there are no limitations where this cluster will be actually running. This means that whatever security policy you have within your company, you can run it where you want: on-premise, public cloud, private cloud, etc.
-
+
## Licensing
diff --git a/content/enterprise/get-started.md b/content/enterprise/get-started.md
index 67b7df9..ab8b731 100644
--- a/content/enterprise/get-started.md
+++ b/content/enterprise/get-started.md
@@ -26,7 +26,7 @@ Important to note is that this web app is relying on the Golang Kubernetes SDK,
Once you open a browser, and navigate to the Factory web application (see installation for the url), you will land on the login page.
-
+
The default username password of the Factory web applications is:
@@ -41,7 +41,7 @@ On the overview page you will find an intuitive overview of the different pages
When working with Kubernetes, Kerberos Enterprise agents are deployed as a deployment. When working with Docker, Kerberos Enterprise agents are deployed as traditional Docker containers.
-
+
## Kubernetes
@@ -56,18 +56,21 @@ On the left menu you will find the Kubernetes section. In this section 3 sub men
The nodes section lists all the available nodes inside your Kubernetes cluster. It shows a limited amount of information such as the version, the number of Docker images installed on the node, and some basic hardware information.
+
## Deployments
The deployments section will list all the Kerberos Enterprise agents (running as deployments) that you have deployed inside your cluster. This page gives you access to deploy new Kerberos Enterprise agents one by one or in bulk. Next to that you can easily upgrade Kerberos Enterprise agents to a newer version, reboot them, view logging and update the configuration options of the Kerberos Enterprise agent.
+
### Adding a new deployment
There are two options to add a new deployment, single deployments and bulk deployment.
+
- single deployment
@@ -80,12 +83,14 @@ By importing an Excel file, deployments can be created in bulk.
By specifying the name and corresponding RTSP url in multiple rows, you can deploy your deployments in bulk.
+
### Configuring a deployment
Once you have a running deployment, you should see a green circle next to the deployment, indicating that it is succesfully running. At any time you can configure your deployments by clicking on the icon. This will open a popup, allowing you to change some settings.
+
Following settings can be changed:
@@ -93,7 +98,7 @@ Following settings can be changed:
- Time based conditions,
- Pre- and postrecording
- Continious recording
-- Linking to [Kerberos Cloud](/cloud) or [Kerberos Storage](/storage/introduction)
+- Linking to [Kerberos Hub](/hub/first-things-first) or [Kerberos Vault](/vault/first-things-first)
### Global configuration
@@ -102,6 +107,7 @@ Configuration can be specified on a Kerberos Enterprise agent level, this means
By specifying configurations at a higher level, any Kerberos Enterprise agents will inherit from that configuration, improving the overall maintenance and management of your Kerberos Enterprise agents.
+
### Upgrade or reboot a Kerberos Enterprise agent
@@ -110,61 +116,63 @@ At Kerberos.io we have fast development cycles, which means that new versions wi
At any moment you can reboot your Kerberos Enterprise agent. When pressing the reboot button, next to your deployment, Kubernetes will destroy the pod of your deployment, and schedule a new one. This comes in handy, when you noticed one of your Kerberos Enterprise agents is in a stale state.
-
+
## Pods
When creating a Kerberos Enterprise agent, Kubernetes will create a deployment and schedule a pod. This pod will be managed by your deployment, and deployed as a Docker container to one of your available nodes. Once a pod dies/ crashes, or whatever unexpected scenario, the deployment will make sure it is deployed again to a different (or the same) node. This makes sure the Kerberos Enterprise agent is in a healthy state at all times.
-
+
## Storage and video management
Kerberos Enterprise allows you to scale your video landscape horizontally, using the concept of Kubernetes, and brings a strong backbone for stability and performance. It allows you to avoid reinventing the wheel, and get stuck in the numerious challenges of making an intelligent VMS yourself (we worked on this for 2 years with experienced engineers).
-Kerberos Enterprise stores its recordings locally for a short amount of time. This means that long-term storage is not included in the solution. On top of that it also **does not** have a visual component, which allows you te review dashboards or recordings. To overcome these two challenges, long-term storage with extensibility/integration capabilities and visualisation features, following solutions were developed [Kerberos Storage](/storage/introduction) and [Kerberos Cloud](/cloud).
+Kerberos Enterprise stores its recordings locally for a short amount of time. This means that long-term storage is not included in the solution. On top of that it also **does not** have a visual component, which allows you te review dashboards or recordings. To overcome these two challenges, long-term storage with extensibility/integration capabilities and visualisation features, following solutions were developed [Kerberos Vault](/storage/introduction) and [Kerberos Hub](/cloud).
-### Kerberos Storage
+### Kerberos Vault
-[Kerberos Storage](/storage/introduction) is a solution which makes it able to store recordings from Kerberos Enterprise agents (accross different clusters) at a central place, on the storage provider you want. You can store your recordings in the cloud (AWS S3, Google Cloud Storage, Azure Blob storage) or on premise (Minio).
+[Kerberos Vault](/vault/first-things-first) is a solution which makes it able to store recordings from Kerberos Enterprise agents (accross different clusters) at a central place, on the storage provider you want. You can store your recordings in the cloud (AWS S3, Google Cloud Storage, Azure Blob storage) or on premise (Minio).
-On the other hand it's an open platform, as it allows you build extensions and integrations (web apps, mobile apps, machine learning services much more). Kerberos Storage ships with the ability of real-time messaging (Kafka) and a REST API (documented as Swaggger).
+On the other hand it's an open platform, as it allows you build extensions and integrations (web apps, mobile apps, machine learning services much more). Kerberos Vault ships with the ability of real-time messaging (Kafka) and a REST API (documented as Swaggger).
+
-To connect one or more Kerberos Enterprise agents to your Kerberos Storage instance, you should open the configuration option and navigate to the `cloud` tab. Once selected you need to fill-in the credentials from your Kerberos Storage account.
+To connect one or more Kerberos Enterprise agents to your Kerberos Vault instance, you should open the configuration option and navigate to the `cloud` tab. Once selected you need to fill-in the credentials from your Kerberos Vault account.
-- Storage URI: this is the API endpoint of your Kerberos Storage instance. Typically this is in the following format: `http(s)://api.yourdomain.com/storage`. Where `api.yourdomain.com` should match your Kerberos Storage API endpoint.
+- Storage URI: this is the API endpoint of your Kerberos Vault instance. Typically this is in the following format: `http(s)://api.yourdomain.com/storage`. Where `api.yourdomain.com` should match your Kerberos Vault API endpoint.
-- Provider: the name of the provider, which you created on the Kerberos Storage providers page, to which you want to send your recordings to.
+- Provider: the name of the provider, which you created on the Kerberos Vault providers page, to which you want to send your recordings to.
-- Directory: this is the subdirectory in which your files will be stored. At the time of writing this should also equal your Kerberos Cloud username, if you plan to upload to Kerberos Cloud.
+- Directory: this is the subdirectory in which your files will be stored. At the time of writing this should also equal your Kerberos Hub username, if you plan to upload to Kerberos Hub.
-- Access Key: this should match the access key of one of your Kerberos Storage accounts.
+- Access Key: this should match the access key of one of your Kerberos Vault accounts.
-- Secret Access Key: this should match the secret access key of one of your Kerberos Storage accounts.
+- Secret Access Key: this should match the secret access key of one of your Kerberos Vault accounts.
-
+
+
-### Kerberos Cloud
+### Kerberos Hub
-For the visualisation part Kerberos Cloud comes into the picture. Kerberos Cloud is a web app, backed up with a number of microservices, that shows dashboards, live streams, filter recordings and much more. Learn more [about the features and functions here](/cloud).
+For the visualisation part Kerberos Hub comes into the picture. Kerberos Hub is a web app, backed up with a number of microservices, that shows dashboards, live streams, filter recordings and much more. Learn more [about the features and functions here](/cloud).
-You have two choices when using Kerberos Cloud, either you send your recordings from your Kerberos Enterprise agents directly to Kerberos Cloud, or you send your recordings to Kerberos Storage, and connect Kerberos Storage to Kerberos Cloud. About the latter more is explained on the [Kerberos Storage page](/storage/get-started).
+You have two choices when using Kerberos Hub, either you send your recordings from your Kerberos Enterprise agents directly to Kerberos Hub, or you send your recordings to Kerberos Vault, and connect Kerberos Vault to Kerberos Hub. About the latter more is explained on the [Kerberos Vault page](/storage/get-started).
-Select the Kerberos Cloud option, and copy-paste the credentials from your Kerberos Cloud subscription.
-
-
+Select the Kerberos Hub option, and copy-paste the credentials from your Kerberos Hub subscription.
+
+
- Region: this is the region where your recordings will be stored. Only `eu-west-1` for now (will change, on the roadmap).
-- Bucket: the name of the Kerberos Cloud bucket. Only `kerberosaccept` for now (will change, on the roadmap).
+- Bucket: the name of the Kerberos Hub bucket. Only `kerberosaccept` for now (will change, on the roadmap).
-- Directory: this is your personal directory, and matches your Kerberos Cloud username.
+- Directory: this is your personal directory, and matches your Kerberos Hub username.
-- Public Key: this should match the public key of your Kerberos Cloud subscription.
+- Public Key: this should match the public key of your Kerberos Hub subscription.
-- Secret Access Key: this should match the private key of your Kerberos Cloud subscription.
\ No newline at end of file
+- Secret Access Key: this should match the private key of your Kerberos Hub subscription.
\ No newline at end of file
diff --git a/content/opensourcev3/announcement.md b/content/opensourcev3/announcement.md
index fc8adff..b7195cb 100644
--- a/content/opensourcev3/announcement.md
+++ b/content/opensourcev3/announcement.md
@@ -19,7 +19,7 @@ Kerberos Open Source (v3) is the next generation of Kerberos.io, and is the succ
At the bottom line, we are rebuilding the project from scratch using a different technology stack. We are saying goodbye to C++, PHP (Laravel), BackboneJS and saying hello to Golang and React. Despite the technology changes, we are also changing the architecture, we have put in place a couple of years ago. The biggest change is to run the show inside a single repository, and no longer over seperate repos (machinery and web). Read more about this in the FAQ.
-
+
## FAQ
diff --git a/content/prologue/_index.md b/content/opensourcev3/prologue/_index.md
similarity index 100%
rename from content/prologue/_index.md
rename to content/opensourcev3/prologue/_index.md
diff --git a/content/prologue/deployments.md b/content/opensourcev3/prologue/deployments.md
similarity index 100%
rename from content/prologue/deployments.md
rename to content/opensourcev3/prologue/deployments.md
diff --git a/content/prologue/how.md b/content/opensourcev3/prologue/how.md
similarity index 99%
rename from content/prologue/how.md
rename to content/opensourcev3/prologue/how.md
index b1f1661..250409d 100644
--- a/content/prologue/how.md
+++ b/content/opensourcev3/prologue/how.md
@@ -15,7 +15,6 @@ 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.
-
## Front-End
diff --git a/content/prologue/introduction.md b/content/opensourcev3/prologue/introduction.md
similarity index 100%
rename from content/prologue/introduction.md
rename to content/opensourcev3/prologue/introduction.md
diff --git a/content/prologue/quick-start.md b/content/opensourcev3/prologue/quick-start.md
similarity index 100%
rename from content/prologue/quick-start.md
rename to content/opensourcev3/prologue/quick-start.md
diff --git a/content/vault/first-things-first.md b/content/vault/first-things-first.md
index a0946dc..324f072 100644
--- a/content/vault/first-things-first.md
+++ b/content/vault/first-things-first.md
@@ -13,23 +13,23 @@ weight: 300
toc: true
---
-Kerberos Open Source and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
+Kerberos Opensource and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
## The options
-### Kerberos Cloud
+### Kerberos Hub
-One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Cloud](/cloud), and benefit from the visualisation layer Kerberos Cloud offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
+One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Hub](/cloud), and benefit from the visualisation layer Kerberos Hub offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
### Kerberos Storage
-In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Storage. Kerberos Storage allows you to configure the storage providers you want, and allows you to connect to [Kerberos Cloud](/cloud) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
+In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Storage. Kerberos Storage allows you to configure the storage providers you want, and allows you to connect to [Kerberos Hub](/cloud) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
Despite the flexible storage capabilities, Kerberos Storage is also an open platform, which can be used to build extensions (mobile apps, web apps, machine learning services, etc) and integrations. It allows you to leverage a scalable and stable system as a strong backbone for your video analytics solutions, machine learning algorithms, and more.
-## Kerberos Cloud
+## Kerberos Hub
-Within Kerberos Open Source an Kerberos Enterprise you can upload your recordings to our [Kerberos Cloud](/cloud) environment. This means that your data will be hosted and processed (metadata) in our Kerberos datacenter. For more information about how Kerberos Cloud works [can be found here](/cloud).
+Within Kerberos Open Source an Kerberos Enterprise you can upload your recordings to our [Kerberos Hub](/cloud) environment. This means that your data will be hosted and processed (metadata) in our Kerberos datacenter. For more information about how Kerberos Hub works [can be found here](/cloud).
@@ -71,7 +71,7 @@ A couple of usecases are the following ones:
- Continious recording: having continious recordings stored in your Kerberos Storage on premise, you don't want to replicate all your recordings to a Kerberos Storage provider in the cloud (to make them public available). Therefore you could implement custom logic, for example based on a machine learning algorithm, to only replicate recordings which matche a specific scenario.
-- On-Demand request: Having Kerberos Cloud, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Storage on premise to your Kerberos Storage in the cloud. Only when an end user requests one or more recordings, the
+- On-Demand request: Having Kerberos Hub, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Storage on premise to your Kerberos Storage in the cloud. Only when an end user requests one or more recordings, the
upload will start for the requested recordings.
### Open API
diff --git a/layouts/partials/head/favicons.html b/layouts/partials/head/favicons.html
index e34e521..001e0e2 100644
--- a/layouts/partials/head/favicons.html
+++ b/layouts/partials/head/favicons.html
@@ -1,5 +1,5 @@
-
-
-
+
+
+
\ No newline at end of file
diff --git a/static/android-chrome-192x192.png b/static/android-chrome-192x192.png
deleted file mode 100644
index 03a0e70..0000000
Binary files a/static/android-chrome-192x192.png and /dev/null differ
diff --git a/static/android-chrome-512x512.png b/static/android-chrome-512x512.png
deleted file mode 100644
index 74bdfb9..0000000
Binary files a/static/android-chrome-512x512.png and /dev/null differ
diff --git a/static/apple-touch-icon.png b/static/apple-touch-icon.png
deleted file mode 100644
index 225acef..0000000
Binary files a/static/apple-touch-icon.png and /dev/null differ
diff --git a/static/doks.png b/static/doks.png
deleted file mode 100644
index 70d8c78..0000000
Binary files a/static/doks.png and /dev/null differ
diff --git a/static/doks.svg b/static/doks.svg
deleted file mode 100644
index 4631bc5..0000000
--- a/static/doks.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/static/favicon-16x16.png b/static/favicon-16x16.png
deleted file mode 100644
index 8fcd422..0000000
Binary files a/static/favicon-16x16.png and /dev/null differ
diff --git a/static/favicon-32x32.png b/static/favicon-32x32.png
deleted file mode 100644
index 21378a4..0000000
Binary files a/static/favicon-32x32.png and /dev/null differ
diff --git a/static/favicon.ico b/static/favicon.ico
deleted file mode 100644
index 9e2fc8d..0000000
Binary files a/static/favicon.ico and /dev/null differ
diff --git a/static/favicons/android-chrome-192x192.png b/static/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000..2e2554a
Binary files /dev/null and b/static/favicons/android-chrome-192x192.png differ
diff --git a/static/favicons/android-chrome-512x512.png b/static/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000..e8195a6
Binary files /dev/null and b/static/favicons/android-chrome-512x512.png differ
diff --git a/static/favicons/apple-touch-icon.png b/static/favicons/apple-touch-icon.png
new file mode 100644
index 0000000..e7965cc
Binary files /dev/null and b/static/favicons/apple-touch-icon.png differ
diff --git a/static/favicons/browserconfig.xml b/static/favicons/browserconfig.xml
new file mode 100644
index 0000000..30ba266
--- /dev/null
+++ b/static/favicons/browserconfig.xml
@@ -0,0 +1,9 @@
+
+
+
+
+
+ #b4524e
+
+
+
diff --git a/static/favicons/favicon-16x16.png b/static/favicons/favicon-16x16.png
new file mode 100644
index 0000000..baba772
Binary files /dev/null and b/static/favicons/favicon-16x16.png differ
diff --git a/static/favicons/favicon-32x32.png b/static/favicons/favicon-32x32.png
new file mode 100644
index 0000000..6832a0c
Binary files /dev/null and b/static/favicons/favicon-32x32.png differ
diff --git a/static/favicons/favicon.ico b/static/favicons/favicon.ico
new file mode 100644
index 0000000..dc35b2e
Binary files /dev/null and b/static/favicons/favicon.ico differ
diff --git a/static/favicons/mstile-144x144.png b/static/favicons/mstile-144x144.png
new file mode 100644
index 0000000..187a147
Binary files /dev/null and b/static/favicons/mstile-144x144.png differ
diff --git a/static/favicons/mstile-150x150.png b/static/favicons/mstile-150x150.png
new file mode 100644
index 0000000..8b83ec0
Binary files /dev/null and b/static/favicons/mstile-150x150.png differ
diff --git a/static/favicons/mstile-310x150.png b/static/favicons/mstile-310x150.png
new file mode 100644
index 0000000..e889a0d
Binary files /dev/null and b/static/favicons/mstile-310x150.png differ
diff --git a/static/favicons/mstile-310x310.png b/static/favicons/mstile-310x310.png
new file mode 100644
index 0000000..bb7f2c6
Binary files /dev/null and b/static/favicons/mstile-310x310.png differ
diff --git a/static/favicons/mstile-70x70.png b/static/favicons/mstile-70x70.png
new file mode 100644
index 0000000..d8b4f76
Binary files /dev/null and b/static/favicons/mstile-70x70.png differ
diff --git a/static/favicons/safari-pinned-tab.svg b/static/favicons/safari-pinned-tab.svg
new file mode 100644
index 0000000..71ea8fa
--- /dev/null
+++ b/static/favicons/safari-pinned-tab.svg
@@ -0,0 +1,46 @@
+
+
+
diff --git a/static/favicons/site.webmanifest b/static/favicons/site.webmanifest
new file mode 100644
index 0000000..2696d6f
--- /dev/null
+++ b/static/favicons/site.webmanifest
@@ -0,0 +1,19 @@
+{
+ "name": "Kerberos.io",
+ "short_name": "Kerberos.io",
+ "icons": [
+ {
+ "src": "/favicons/android-chrome-192x192.png?v=1",
+ "sizes": "192x192",
+ "type": "image/png"
+ },
+ {
+ "src": "/favicons/android-chrome-512x512.png?v=1",
+ "sizes": "512x512",
+ "type": "image/png"
+ }
+ ],
+ "theme_color": "#ffffff",
+ "background_color": "#ffffff",
+ "display": "standalone"
+}
diff --git a/static/images/factory/deployment-configuration.gif b/static/images/factory/deployment-configuration.gif
new file mode 100644
index 0000000..8b6e9e3
Binary files /dev/null and b/static/images/factory/deployment-configuration.gif differ
diff --git a/static/images/factory/docker-kubernetes.gif b/static/images/factory/docker-kubernetes.gif
new file mode 100644
index 0000000..940ee73
Binary files /dev/null and b/static/images/factory/docker-kubernetes.gif differ
diff --git a/static/images/factory/global-configuration.gif b/static/images/factory/global-configuration.gif
new file mode 100644
index 0000000..7a71d5d
Binary files /dev/null and b/static/images/factory/global-configuration.gif differ
diff --git a/static/images/factory/kerberos-enterprise-storage-setup.gif b/static/images/factory/kerberos-enterprise-storage-setup.gif
new file mode 100644
index 0000000..6975dd8
Binary files /dev/null and b/static/images/factory/kerberos-enterprise-storage-setup.gif differ
diff --git a/static/images/factory/kerberos-enterprise-to-cloud.gif b/static/images/factory/kerberos-enterprise-to-cloud.gif
new file mode 100644
index 0000000..d1d3441
Binary files /dev/null and b/static/images/factory/kerberos-enterprise-to-cloud.gif differ
diff --git a/static/images/factory/kerberos-factory-add-bulk-deployment-excel.png b/static/images/factory/kerberos-factory-add-bulk-deployment-excel.png
new file mode 100644
index 0000000..c8aead4
Binary files /dev/null and b/static/images/factory/kerberos-factory-add-bulk-deployment-excel.png differ
diff --git a/static/images/factory/kerberos-factory-add-bulk-deployment.png b/static/images/factory/kerberos-factory-add-bulk-deployment.png
new file mode 100644
index 0000000..a11a872
Binary files /dev/null and b/static/images/factory/kerberos-factory-add-bulk-deployment.png differ
diff --git a/static/images/factory/kerberos-factory-add-single-deployment.png b/static/images/factory/kerberos-factory-add-single-deployment.png
new file mode 100644
index 0000000..53ba0dc
Binary files /dev/null and b/static/images/factory/kerberos-factory-add-single-deployment.png differ
diff --git a/static/images/factory/kerberos-factory-config-region.png b/static/images/factory/kerberos-factory-config-region.png
new file mode 100644
index 0000000..fca47ca
Binary files /dev/null and b/static/images/factory/kerberos-factory-config-region.png differ
diff --git a/static/images/factory/kerberos-factory-dashboard.png b/static/images/factory/kerberos-factory-dashboard.png
new file mode 100644
index 0000000..6ad0b64
Binary files /dev/null and b/static/images/factory/kerberos-factory-dashboard.png differ
diff --git a/static/images/factory/kerberos-factory-deployments.png b/static/images/factory/kerberos-factory-deployments.png
new file mode 100644
index 0000000..58682d0
Binary files /dev/null and b/static/images/factory/kerberos-factory-deployments.png differ
diff --git a/static/images/factory/kerberos-factory-licensekey.png b/static/images/factory/kerberos-factory-licensekey.png
new file mode 100644
index 0000000..10fa743
Binary files /dev/null and b/static/images/factory/kerberos-factory-licensekey.png differ
diff --git a/static/images/factory/kerberos-factory-loginpage-small.png b/static/images/factory/kerberos-factory-loginpage-small.png
new file mode 100644
index 0000000..9c185e2
Binary files /dev/null and b/static/images/factory/kerberos-factory-loginpage-small.png differ
diff --git a/static/images/factory/kerberos-factory-loginpage.png b/static/images/factory/kerberos-factory-loginpage.png
new file mode 100644
index 0000000..0c2a41e
Binary files /dev/null and b/static/images/factory/kerberos-factory-loginpage.png differ
diff --git a/static/images/factory/kerberos-factory-nodes.png b/static/images/factory/kerberos-factory-nodes.png
new file mode 100644
index 0000000..aeb4697
Binary files /dev/null and b/static/images/factory/kerberos-factory-nodes.png differ
diff --git a/static/images/factory/kerberos-factory-pods.png b/static/images/factory/kerberos-factory-pods.png
new file mode 100644
index 0000000..027360a
Binary files /dev/null and b/static/images/factory/kerberos-factory-pods.png differ
diff --git a/static/images/factory/login.gif b/static/images/factory/login.gif
new file mode 100644
index 0000000..2e3597a
Binary files /dev/null and b/static/images/factory/login.gif differ
diff --git a/static/images/factory/single-bulk-deployment.gif b/static/images/factory/single-bulk-deployment.gif
new file mode 100644
index 0000000..e710442
Binary files /dev/null and b/static/images/factory/single-bulk-deployment.gif differ
diff --git a/static/images/factory/upgrade-reboot.gif b/static/images/factory/upgrade-reboot.gif
new file mode 100644
index 0000000..cba09d6
Binary files /dev/null and b/static/images/factory/upgrade-reboot.gif differ
diff --git a/static/images/opensourcev3/opensource-version2-version3.svg b/static/images/opensourcev3/opensource-version2-version3.svg
new file mode 100644
index 0000000..b3751a0
--- /dev/null
+++ b/static/images/opensourcev3/opensource-version2-version3.svg
@@ -0,0 +1,416 @@
+
diff --git a/static/logo-doks.png b/static/logo-doks.png
deleted file mode 100644
index 74bdfb9..0000000
Binary files a/static/logo-doks.png and /dev/null differ
diff --git a/theme.toml b/theme.toml
index b526d1d..64a700e 100644
--- a/theme.toml
+++ b/theme.toml
@@ -1,12 +1,11 @@
-name = "Doks"
+name = "Kerberos.io"
license = "MIT"
-licenselink = "https://github.com/h-enk/doks/blob/master/LICENSE"
-description = "Hugo theme helping you build modern documentation websites that are secure, fast, and SEO-ready — by default."
-homepage = "https://getdoks.org/"
-tags = ["landing page", "documentation", "blog", "minimal", "modern", "customizable", "search", "dark mode", "bootstrap"]
-features = ["security aware", "fast by default", "seo-ready", "development tools", "bootstrap framework", "netlify-ready", "full text search", "page layouts", "dark mode"]
+description = "Kerberos.io is a scalable and cloud agnostic video surveillance and analytics system, which is open for integrations."
+homepage = "https://doc.kerberos.io/"
+tags = ["kerberos.io", "video surveillance", "video analytics", "scalable"]
+features = ["scalable", "high available", "docker", "kubernetes", "opensource", "bring your own storage", "on premise video surveillance"]
min_version = "0.75.0"
[author]
- name = "Henk Verlinde"
- homepage = "https://henkverlinde.com/"
+ name = "Cedric Verstraeten"
+ homepage = "https://kerberos.io/"
Kerberos Enterprise is installed inside a Kubernetes cluster. It will create pods/deployments for every surveillance camera you want to monitor. Kubernetes will scale and distrubute these pods across your nodes (VM's/Baremetal machines).
@@ -50,7 +50,7 @@ By having the power to add nodes to your cluster, you can anticipate to the ever
You install Kerberos Enterprise inside a Kubernetes cluster, but there are no limitations where this cluster will be actually running. This means that whatever security policy you have within your company, you can run it where you want: on-premise, public cloud, private cloud, etc.
-
+
## Licensing
diff --git a/content/enterprise/get-started.md b/content/enterprise/get-started.md
index 67b7df9..ab8b731 100644
--- a/content/enterprise/get-started.md
+++ b/content/enterprise/get-started.md
@@ -26,7 +26,7 @@ Important to note is that this web app is relying on the Golang Kubernetes SDK,
Once you open a browser, and navigate to the Factory web application (see installation for the url), you will land on the login page.
-
+
## FAQ
diff --git a/content/prologue/_index.md b/content/opensourcev3/prologue/_index.md
similarity index 100%
rename from content/prologue/_index.md
rename to content/opensourcev3/prologue/_index.md
diff --git a/content/prologue/deployments.md b/content/opensourcev3/prologue/deployments.md
similarity index 100%
rename from content/prologue/deployments.md
rename to content/opensourcev3/prologue/deployments.md
diff --git a/content/prologue/how.md b/content/opensourcev3/prologue/how.md
similarity index 99%
rename from content/prologue/how.md
rename to content/opensourcev3/prologue/how.md
index b1f1661..250409d 100644
--- a/content/prologue/how.md
+++ b/content/opensourcev3/prologue/how.md
@@ -15,7 +15,6 @@ 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.
-
## Front-End
diff --git a/content/prologue/introduction.md b/content/opensourcev3/prologue/introduction.md
similarity index 100%
rename from content/prologue/introduction.md
rename to content/opensourcev3/prologue/introduction.md
diff --git a/content/prologue/quick-start.md b/content/opensourcev3/prologue/quick-start.md
similarity index 100%
rename from content/prologue/quick-start.md
rename to content/opensourcev3/prologue/quick-start.md
diff --git a/content/vault/first-things-first.md b/content/vault/first-things-first.md
index a0946dc..324f072 100644
--- a/content/vault/first-things-first.md
+++ b/content/vault/first-things-first.md
@@ -13,23 +13,23 @@ weight: 300
toc: true
---
-Kerberos Open Source and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
+Kerberos Opensource and Kerberos Enterprise both store recordings on the local disk. To centralise your data at a single place, additional solutions are available.
## The options
-### Kerberos Cloud
+### Kerberos Hub
-One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Cloud](/cloud), and benefit from the visualisation layer Kerberos Cloud offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
+One or more Kerberos Enterprise agents, can store their data directly on [Kerberos Hub](/cloud), and benefit from the visualisation layer Kerberos Hub offers. When doing this your recordings will be uploaded inside the Kerberos datacenter (which is a black box for you).
### Kerberos Storage
-In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Storage. Kerberos Storage allows you to configure the storage providers you want, and allows you to connect to [Kerberos Cloud](/cloud) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
+In addition to that you have the option to Bring Your Own Storage (BYOS), using Kerberos Storage. Kerberos Storage allows you to configure the storage providers you want, and allows you to connect to [Kerberos Hub](/cloud) in parrallel. These storage provider could live in the cloud such as AWS S3, GCP storage and Azure Blob store, or can be located on premise - at the edge - such as Minio.
Despite the flexible storage capabilities, Kerberos Storage is also an open platform, which can be used to build extensions (mobile apps, web apps, machine learning services, etc) and integrations. It allows you to leverage a scalable and stable system as a strong backbone for your video analytics solutions, machine learning algorithms, and more.
-## Kerberos Cloud
+## Kerberos Hub
-Within Kerberos Open Source an Kerberos Enterprise you can upload your recordings to our [Kerberos Cloud](/cloud) environment. This means that your data will be hosted and processed (metadata) in our Kerberos datacenter. For more information about how Kerberos Cloud works [can be found here](/cloud).
+Within Kerberos Open Source an Kerberos Enterprise you can upload your recordings to our [Kerberos Hub](/cloud) environment. This means that your data will be hosted and processed (metadata) in our Kerberos datacenter. For more information about how Kerberos Hub works [can be found here](/cloud).
@@ -71,7 +71,7 @@ A couple of usecases are the following ones:
- Continious recording: having continious recordings stored in your Kerberos Storage on premise, you don't want to replicate all your recordings to a Kerberos Storage provider in the cloud (to make them public available). Therefore you could implement custom logic, for example based on a machine learning algorithm, to only replicate recordings which matche a specific scenario.
-- On-Demand request: Having Kerberos Cloud, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Storage on premise to your Kerberos Storage in the cloud. Only when an end user requests one or more recordings, the
+- On-Demand request: Having Kerberos Hub, an end-user could initiate a request for upload. By default no recordings are forwarded from your Kerberos Storage on premise to your Kerberos Storage in the cloud. Only when an end user requests one or more recordings, the
upload will start for the requested recordings.
### Open API
diff --git a/layouts/partials/head/favicons.html b/layouts/partials/head/favicons.html
index e34e521..001e0e2 100644
--- a/layouts/partials/head/favicons.html
+++ b/layouts/partials/head/favicons.html
@@ -1,5 +1,5 @@
-
-
-
+
+
+
\ No newline at end of file
diff --git a/static/android-chrome-192x192.png b/static/android-chrome-192x192.png
deleted file mode 100644
index 03a0e70..0000000
Binary files a/static/android-chrome-192x192.png and /dev/null differ
diff --git a/static/android-chrome-512x512.png b/static/android-chrome-512x512.png
deleted file mode 100644
index 74bdfb9..0000000
Binary files a/static/android-chrome-512x512.png and /dev/null differ
diff --git a/static/apple-touch-icon.png b/static/apple-touch-icon.png
deleted file mode 100644
index 225acef..0000000
Binary files a/static/apple-touch-icon.png and /dev/null differ
diff --git a/static/doks.png b/static/doks.png
deleted file mode 100644
index 70d8c78..0000000
Binary files a/static/doks.png and /dev/null differ
diff --git a/static/doks.svg b/static/doks.svg
deleted file mode 100644
index 4631bc5..0000000
--- a/static/doks.svg
+++ /dev/null
@@ -1 +0,0 @@
-
\ No newline at end of file
diff --git a/static/favicon-16x16.png b/static/favicon-16x16.png
deleted file mode 100644
index 8fcd422..0000000
Binary files a/static/favicon-16x16.png and /dev/null differ
diff --git a/static/favicon-32x32.png b/static/favicon-32x32.png
deleted file mode 100644
index 21378a4..0000000
Binary files a/static/favicon-32x32.png and /dev/null differ
diff --git a/static/favicon.ico b/static/favicon.ico
deleted file mode 100644
index 9e2fc8d..0000000
Binary files a/static/favicon.ico and /dev/null differ
diff --git a/static/favicons/android-chrome-192x192.png b/static/favicons/android-chrome-192x192.png
new file mode 100644
index 0000000..2e2554a
Binary files /dev/null and b/static/favicons/android-chrome-192x192.png differ
diff --git a/static/favicons/android-chrome-512x512.png b/static/favicons/android-chrome-512x512.png
new file mode 100644
index 0000000..e8195a6
Binary files /dev/null and b/static/favicons/android-chrome-512x512.png differ
diff --git a/static/favicons/apple-touch-icon.png b/static/favicons/apple-touch-icon.png
new file mode 100644
index 0000000..e7965cc
Binary files /dev/null and b/static/favicons/apple-touch-icon.png differ
diff --git a/static/favicons/browserconfig.xml b/static/favicons/browserconfig.xml
new file mode 100644
index 0000000..30ba266
--- /dev/null
+++ b/static/favicons/browserconfig.xml
@@ -0,0 +1,9 @@
+
+