diff --git a/docs/architecture/self-hosted/download-logs.md b/docs/architecture/self-hosted/download-logs.md
index ad014b1b00..46c018ba4f 100644
--- a/docs/architecture/self-hosted/download-logs.md
+++ b/docs/architecture/self-hosted/download-logs.md
@@ -2,7 +2,7 @@
 title: Download logs
 id: download-logs
 description: Download Prophecy support logs
-sidebar_position: 5
+sidebar_position: 6
 tags:
   - download
   - support logs
diff --git a/docs/architecture/self-hosted/generate-api-key.md b/docs/architecture/self-hosted/generate-api-key.md
index b18f4751c3..5629ad4cd2 100644
--- a/docs/architecture/self-hosted/generate-api-key.md
+++ b/docs/architecture/self-hosted/generate-api-key.md
@@ -2,7 +2,7 @@
 title: Generate API key
 id: generate-api-key
 description: Generate your own custom API key per deployment
-sidebar_position: 6
+sidebar_position: 7
 tags:
   - Generate
   - API
diff --git a/docs/architecture/self-hosted/img/monitoring.png b/docs/architecture/self-hosted/img/monitoring.png
new file mode 100644
index 0000000000..7fc4799c2e
Binary files /dev/null and b/docs/architecture/self-hosted/img/monitoring.png differ
diff --git a/docs/architecture/self-hosted/resource-monitoring.md b/docs/architecture/self-hosted/resource-monitoring.md
new file mode 100644
index 0000000000..c2dd1547ac
--- /dev/null
+++ b/docs/architecture/self-hosted/resource-monitoring.md
@@ -0,0 +1,40 @@
+---
+title: Resource monitoring
+id: resource-monitoring
+description: Find an overview of resource monitoring, alert configuration, and scaling recommendations
+sidebar_position: 5
+tags:
+  - scaling
+  - resources
+  - monitoring
+---
+
+This page provides an overview of resource monitoring, alert configuration, and scaling recommendations for effectively managing Prophecy deployments.
+
+## Monitoring
+
+To have a better understanding of how Prophecy is using resources, you can find an overview in **Settings > Admin > Monitoring**.
+
+![Monitoring settings](./img/monitoring.png)
+
+## Alerts
+
+To set up automated alerts about your resource usage, visit the page on [Alerts Configuration](docs/architecture/self-hosted/configurations/configure-alerts.md).
+
+## Scaling
+
+Scaling is taken care of by the **Autoscaler** component in our platform. Therefore, if something happens like the number of
+users increases by 10 times, the Prophecy deployment can be scaled appropriately.
+
+The following are estimated recommended cluster sizes depending on the number of concurrent users:
+
+| Number of users           | 25       | 50       | 100       |
+| ------------------------- | -------- | -------- | --------- |
+| CPUs                      | 56 vCPUs | 96 vCPUs | 180 vCPUs |
+| Memory                    | 128 GB   | 256 GB   | 440 GB    |
+| Disk space (with backups) | 360 GB   | 720 GB   | 1440 GB   |
+
+:::info
+The recommended resource may vary based on the intensity of the usage of each developer. The numbers
+presented above are based on the average recorded usage of Prophecy customers.
+:::
diff --git a/docs/architecture/self-hosted/upgrade-backup-restore.md b/docs/architecture/self-hosted/upgrade-backup-restore.md
index 05c0327116..12d65fbaad 100644
--- a/docs/architecture/self-hosted/upgrade-backup-restore.md
+++ b/docs/architecture/self-hosted/upgrade-backup-restore.md
@@ -78,6 +78,10 @@ Below is a list of supported variables that you can change.
 | `backupRetentionCount`      | Number of last `N` backups to retain.                                                                                                                                                     | `30`          |
 | `enableRegularBackups`      | State of automated backup creation.                                                                                                                                                       | `false`       |
 
+### View past backups
+
+You can view a history of backups in **Settings > Admin > Backup**.
+
 ### Additional backup APIs
 
 Here is a list of additional APIs for backups. One sample call may look like: