diff --git a/docs/VictoriaLogs/README.md b/docs/VictoriaLogs/README.md
index c860f30c2..3e8e73f3b 100644
--- a/docs/VictoriaLogs/README.md
+++ b/docs/VictoriaLogs/README.md
@@ -129,6 +129,21 @@ For example, the following command starts VictoriaLogs, which stores the data at
 
 VictoriaLogs automatically creates the `-storageDataPath` directory on the first run if it is missing.
 
+## High Availability
+
+### High Availability (HA) Setup with VictoriaLogs Single-Node Instances
+
+This schema outlines how to configure a High Availability (HA) setup using VictoriaLogs Single-Node instances. The setup consists of the following components:
+
+- **Log Collector**: The log collector should support multiplexing incoming data to multiple outputs (destinations). Popular log collectors like [Logstash](https://www.elastic.co/guide/en/logstash/current/output-plugins.html), [Fluentd](https://docs.fluentd.org/output/copy), and [Vector](https://vector.dev/docs/setup/configuration/sinks/) already offer this capability. Refer to their documentation for configuration details.
+
+- **VictoriaLogs Single-Node Instances**: Use two or more instances to achieve HA.
+
+- **[vmauth](https://docs.victoriametrics.com/vmauth/#load-balancing) or Load Balancer**: Used for reading data from one of the replicas to ensure balanced and redundant access.
+
+![VictoriaLogs Single-Node Instance High-Availability schema](ha-victorialogs-single-node.webp)
+
+
 ## Backup and restore
 
 VictoriaLogs currently does not have a snapshot feature and a tool like vmbackup as VictoriaMetrics does.
diff --git a/docs/VictoriaLogs/ha-victorialogs-single-node.webp b/docs/VictoriaLogs/ha-victorialogs-single-node.webp
new file mode 100644
index 000000000..70c1eccb6
Binary files /dev/null and b/docs/VictoriaLogs/ha-victorialogs-single-node.webp differ