diff --git a/docs/architecture/.$containers.drawio.bkp b/docs/architecture/.$containers.drawio.bkp
new file mode 100644
index 0000000..d597f66
--- /dev/null
+++ b/docs/architecture/.$containers.drawio.bkp
@@ -0,0 +1,36 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/architecture/Thumbs.db b/docs/architecture/Thumbs.db
new file mode 100644
index 0000000..777886e
Binary files /dev/null and b/docs/architecture/Thumbs.db differ
diff --git a/docs/architecture/basic-containers.png b/docs/architecture/basic-containers.png
new file mode 100644
index 0000000..00ded38
Binary files /dev/null and b/docs/architecture/basic-containers.png differ
diff --git a/docs/architecture/containers-Performance.png b/docs/architecture/containers-Performance.png
new file mode 100644
index 0000000..02aff45
Binary files /dev/null and b/docs/architecture/containers-Performance.png differ
diff --git a/docs/architecture/containers.drawio b/docs/architecture/containers.drawio
new file mode 100644
index 0000000..557cdcd
--- /dev/null
+++ b/docs/architecture/containers.drawio
@@ -0,0 +1,90 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/architecture/img.png b/docs/architecture/img.png
new file mode 100644
index 0000000..cf5c830
Binary files /dev/null and b/docs/architecture/img.png differ
diff --git a/docs/architecture/img_1.png b/docs/architecture/img_1.png
new file mode 100644
index 0000000..9c06130
Binary files /dev/null and b/docs/architecture/img_1.png differ
diff --git a/docs/architecture/index.md b/docs/architecture/index.md
new file mode 100644
index 0000000..e6df793
--- /dev/null
+++ b/docs/architecture/index.md
@@ -0,0 +1,131 @@
+# Architectural
+
+---
+
+## Application
+
+The application is based on the following Model-View-Controle frameworks:
+
+- Laravel version 9.1 or higher
+- WinterCMS version 1.2.5 or higher
+
+The Model-View-Controller (MVC) framework is an architectural/design pattern that separates
+an application into three main logical components Model, View, and Controller.
+Each architectural component is built to handle specific development aspects of an application.
+It isolates the business logic and presentation layer from each other. It was traditionally
+used for desktop graphical user interfaces (GUIs). Nowadays, MVC is one of the most frequently
+used industry-standard web development frameworks to create scalable and extensible
+applications.
+
+
+
+Futhermore Object-Oriented Programming (OOP) is used for development of the software.
+OOP is a programming paradigm based on the concept of objects, which can contain data
+and code: data in the form of fields (often known as attributes or properties), and
+code in the form of procedures (often known as methods). In OOP, computer programs
+are designed by making them out of objects that interact with one another.
+
+Important is the use of the WinterCMS framework. SCARt uses as much as possible the
+standard functionality of this framework. See here for the [WinterCMS Development Guide](https://wintercms.com/docs/v1.2/docs/architecture/developer-guide#html-element-naming).
+
+SCARt also adapts the version numbering of "major.minor.point". For example v1.0.1 or v5.3.2.
+
+- **major**; should be increased for substantial changes made to the plugin, such as complete
+rewrites or pivoting of the purpose of the plugin. These changes are assumed to be
+backwards-incompatible and will require manual intervention by the users of the plugin.
+- **minor**; should be increased for smaller changes or new features that may still be
+backwards-incompatible with adequate justification. This can include changes to the
+database schema or changes to component settings.
+- **point**; should be increased for minor fixes, translation updates or very minor new
+features that maintain backwards compatibility.
+
+Release notes are referencing to a version and contain (if applicable) the following
+elements:
+
+- Breaking changes
+- New features
+- Other changes
+- Bug fixes
+- Translation updates
+
+See here for more information about the versioning: [WinterCMS plugin version history](https://wintercms.com/docs/v1.2/docs/plugin/updates).
+
+## Containers
+
+The MVC is futher enhanced in SCART by containerizing the different system components. This
+makes them scalable and provide failover functionality. With containers the application
+components are also placed in a seperated (local) network.
+
+A basic container setup:
+
+
+
+You see the basic system components. The PHP-FPM is (only) used for the frontend processing
+and servers the UI. The PHP-CRON is responsible for the background processes.
+
+## Background processes
+
+Within the PHP-CRON the background work exists of the following jobs:
+
+| Name | Description |
+|:--------------|:--------------------------------------------------------------------------------------------------------------------------------------|
+| ImportExport | Import by email or ICCAM the reports |
+| AnalyzeInput | Read the imported reports, scrape them and get the WhoIs information |
+| CheckNTD | Checks if the illegal reports are still online and the WHoIs the same (*) |
+| SendNTD | Send NTD by email (or API) to the hoster, registrar, site owner or LEA |
+| SendAlert | Send alerts to the info mailbox about the actions done by the background jobs |
+| UpdateWHoIs | Update the WhoIs every 12 hours |
+| CreateReports | Create the user reports (export CSV files) |
+| Cleanup | Every night this background job runs to cleanup the SCARt environment (*) |
+| Archive | In some SCARt environments the number of reports are such big, archiving is needed to keep the runtime performance optimized |
+
+(*) see seperated chapters for more information
+
+It's easy within docker to make for each of these jobs a seperated container. In this
+way the performance can be optimzied.
+
+The following container setup is an example for an optimized setup:
+
+
+
+In this setup the ImportExport and CheckNTD are placed in a seperated containers with
+an own work and resource environment.
+
+## Realtime online check
+
+The CheckNTD job is responsible for the check if an URL is still online.
+
+The standard CheckNTD job is a single PHP job (threat) which starts a headless browser an
+checks each URL.
+
+For bigger hotlines with a lot of illegal URLs to check, there is also the realtime version
+of the CheckNTD job. This realtime version used pooling to start and stop dynamically threats
+for checking the online status. Configuration consist of:
+
+- maximum time within an URL has be checked again (default 4 hours)
+- minimum time after which an uRL has to be checked (default 1 hour)
+- minimum time after which spinning down a worker (default 15 min)
+
+There is no limit from the number of concurrent threats other then the resources on the
+hosting server(s).
+
+Note that the threat job not only checks the online status of an image but also the
+WhoIs information. The hosting (country) information can be changed. On that moment the
+report is placed in the status "CHANGED".
+
+A report is set "offline" when 3 times after eachother, with a delay of 3 minutes, the
+image (hash) is not found online.
+
+### Illegal content browsing
+
+With the docker and the threating setup, the following secure browsing environment exists:
+
+Within the browser container (docker), the website is analyzed and media is download for
+classification. The browser context (website with illegal content) is reset after the
+scraping of the website. The headless browser environment has no direct contact with the
+other SCARt components and/or server and/or SCART client user.
+
+The setup of this realtime version is done by the S3group. They have to knowledge to configure
+and maintain this environment. Please ask your SCARt contact for more information.
+
+
diff --git a/docs/details/cleanup.md b/docs/details/cleanup.md
new file mode 100644
index 0000000..4c6bb1a
--- /dev/null
+++ b/docs/details/cleanup.md
@@ -0,0 +1,60 @@
+# Cleanup
+
+---
+
+## Automatic background process
+
+Every night the cleanup background job runs to do a checkup from the SCARt environment.
+The following actions are done:
+
+1. Recycle of the SCARt application logfile
+2. Reset for scraping-again from inputs-open-for-classify and not look at in the past 24 hours
+3. Remove cached images that have finished being analyzed
+4. Cleanup of the WhoIs cache; removal not active domain and/or IP records
+5. Rewind the ICCAM import one day to be sure every ICCAM report is imported
+6. Make anonymous if the retention time is met
+7. Cleanup "deleted marked records" in the database
+
+## Anonymous
+
+SCARt can be configured (not standard) to anonymouse privacy related fields. These fields
+include:
+
+- URL
+- URL_host
+- URL_base
+- URL_referer
+- URL_IP
+- URL_HASH
+
+After the retention time (for example 1 year) the values in the database of these fields
+are overwriten with "anonymouse-[record-id]".
+
+The status or for example the classification will be kept in the database, so general
+reports without the privacy information can be reported (exported).
+
+The specific retention time has to be configured. Please contact your SCARt contact for
+more information.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/mkdocs.yml b/mkdocs.yml
index 40f83d1..79aeda0 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -29,6 +29,8 @@ nav:
- Custom Webforms: details/custom_webforms.md
- Email import whitelist: details/whitelist.md
- ICCAM: details/iccam.md
+ - Cleanup: details/cleanup.md
+ - "": architecture/architecture.md
diff --git a/themes/mkdocs/base.html b/themes/mkdocs/base.html
index b48ee88..9f2455b 100644
--- a/themes/mkdocs/base.html
+++ b/themes/mkdocs/base.html
@@ -238,7 +238,7 @@
{%- if config.copyright %}
{{ config.copyright }}
{%- endif %}
- SCARt.io - version 0.9 PRE-RELEASE documentation
+ SCARt.io - version 0.9.2 PRE-RELEASE documentation
{%- endblock %}