robusta-dev · moshemorad · May 4, 2026 · Apr 30, 2026 · Apr 30, 2026 · Apr 30, 2026
diff --git a/docs/conf.py b/docs/conf.py
@@ -71,7 +71,11 @@
     "developer-guide/actions/findings-api.html": "/master/playbook-reference/actions/develop-actions/findings-api.html",
     "tutorials/my-first-custom-action.html": "/master/playbook-reference/actions/develop-actions/index.html",
     "user-guide/self-hosting.html": "/master/how-it-works/oss-vs-saas.html",
-    "getting-started/installation.html": "/master/setup-robusta/installation/all-in-one-installation.html",
+    "getting-started/installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/all-in-one-installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/standalone-installation.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/installation/dev-setup.html": "/master/help.html",
+    "setup-robusta/supported-clusters.html": "/master/setup-robusta/installation/index.html",
     "tutorials/java-troubleshooting.html": "/master/tutorials/application-troubleshooting-java.html",
     "catalog/sinks/index.html": "/master/configuration/sinks/index.html",
     "tutorials/prometheus-enrichment.html": "/master/tutorials/alert-custom-enrichment.html",
@@ -97,7 +101,8 @@
     "configuration/defining-playbooks/playbook-basics.html": "/master/playbook-reference/index.html",
     "configuration/defining-playbooks/trigger-action-binding.html": "/master/playbook-reference/index.html#matching-actions-to-triggers",
     "playbook-reference/defining-playbooks/trigger-action-binding.html": "/master/playbook-reference/index.html#matching-actions-to-triggers",
-    "configuration/additional-settings.html": "/master/setup-robusta/additional-settings.html",
+    "configuration/additional-settings.html": "/master/setup-robusta/installation/index.html",
+    "setup-robusta/additional-settings.html": "/master/setup-robusta/installation/index.html",
     "developer-guide/writing-playbooks.html": "/master/playbook-reference/defining-playbooks/index.html",
     "user-guide/slack.html": "/master/configuration/sinks/slack.html",
     "user-guide/elasticsearch.html": "/master/playbook-reference/triggers/elasticsearch.html",
@@ -130,8 +135,11 @@
     "tutorials/alert-custom-prometheus.html": "/master/configuration/alertmanager-integration/alert-custom-prometheus.html",
     "catalog/triggers/prometheus.html": "/master/configuration/alertmanager-integration/index.html",
     "playbook-reference/prometheus-examples/alert-remediation.html": "/master/playbook-reference/automatic-remediation-examples/index.html",
-    "configuration/ai-analysis.html": "/master/configuration/holmesgpt/main-features.html",
-    "configuration/holmesgpt/index.html": "/master/configuration/holmesgpt/main-features.html",
+    "configuration/ai-analysis.html": "https://robusta.dev/",
+    "configuration/holmesgpt/index.html": "https://robusta.dev/",
+    "configuration/holmesgpt/main-features.html": "https://robusta.dev/",
+    "configuration/holmesgpt/getting-started.html": "https://robusta.dev/",
+    "configuration/holmesgpt/holmesgpt-docs.html": "https://robusta.dev/",
     # AI Analysis pages redirects to holmesgpt.dev (docs have moved there)
     "configuration/holmesgpt/builtin_toolsets.html": "https://holmesgpt.dev/data-sources/builtin-toolsets/?tab=robusta-helm-chart",
     "configuration/holmesgpt/permissions.html": "https://holmesgpt.dev/data-sources/permissions/?tab=robusta-helm-chart",
@@ -164,12 +172,12 @@
     "tutorials/more-tutorials.html": "/master/help.html",
     "common-errors.html": "/master/help.html#common-errors",
     "user-guide/defining-playbooks.html": "/master/playbook-reference/defining-playbooks/index.html",
-    "user-guide/global-config.html": "/master/setup-robusta/additional-settings.html#global-config",
+    "user-guide/global-config.html": "/master/setup-robusta/installation/index.html",
     "user-guide/configuration-secrets.html": "master/setup-robusta/configuration-secrets.html",
     "user-guide/additional-playbooks.html": "/master/playbook-reference/defining-playbooks/external-playbook-repositories.html",
     "user-guide/embedded-prometheus.html": "/master/configuration/alertmanager-integration/embedded-prometheus.html#enabling-the-embedded-prometheus",
     "user-guide/node-selector.html": "/master/setup-robusta/node-selector.html",
-    "user-guide/interactivity.html": "/master/setup-robusta/additional-settings.html#two-way-interactivity",
+    "user-guide/interactivity.html": "/master/setup-robusta/installation/index.html",
     "user-guide/flow-control.html": "/master/playbook-reference/index.html#using-filters-to-restrict-triggers",
     "catalog/triggers/index.html": "/master/playbook-reference/triggers/index.html",
     "catalog/triggers/kubernetes.html": "/master/playbook-reference/triggers/kubernetes.html",
@@ -216,7 +224,7 @@
     "playbook-reference/overview.html": "/master/playbook-reference/index.html",
     "playbook-reference/defining-playbooks/playbook-basics.html": "/master/playbook-reference/index.html",
     "how-it-works/alert-builtin-enrichment.html": "/master/playbook-reference/builtin-alert-enrichment.html",
-    "setup-robusta/installation/extend-prometheus-installation.html": "/master/setup-robusta/installation/standalone-installation.html",
+    "setup-robusta/installation/extend-prometheus-installation.html": "/master/setup-robusta/installation/index.html",
     "playbook-reference/defining-playbooks/index.html": "/master/playbook-reference/index.html",
     "configuration/alertmanager-integration/alert-custom-prometheus.html": "/master/configuration/alertmanager-integration/embedded-prometheus.html#creating-custom-prometheus-alerts",
     "configuration/alertmanager-integration/index.html": "/master/configuration/index.html",

diff --git a/docs/configuration/alertmanager-integration/_testing_integration.rst b/docs/configuration/alertmanager-integration/_testing_integration.rst
@@ -56,4 +56,4 @@ If everything is setup properly, this alert will reach Robusta. It will show up
 
     Robusta enriches alerts with Kubernetes and log data using Prometheus labels for mapping.
     Standard label names are used by default. If your setup differs, you can
-    `customize this mapping </setup-robusta/additional-settings.html#alert-label-mapping>`_ to fit your environment.
+    `customize this mapping </configuration/alertmanager-integration/customize-labels-priorities.html>`_ to fit your environment.
diff --git a/docs/configuration/exporting/robusta-pro-features.rst b/docs/configuration/exporting/robusta-pro-features.rst
@@ -19,9 +19,7 @@ Data Export and Reporting
 * :doc:`Alert Reporting API <alert-statistics-api>`: Get aggregated statistics and counts for different alert types
 * :doc:`Send Alerts API <send-alerts-api>`: Send alerts programmatically from external systems
 * :doc:`Configuration Changes API <configuration-changes-api>`: Track configuration changes in your environment
-* :doc:`Namespace Resources API <namespace-resources-api>`: Query namespace-level resource information
 * :doc:`RBAC Configuration API <rbac-api>`: Programmatically manage role-based access control configurations
-* :doc:`Prometheus Query API <prometheus-query-api>`: Run PromQL queries against Prometheus in your connected clusters
 
 Getting Started
 ---------------

diff --git a/docs/configuration/exporting/send-alerts-api.rst b/docs/configuration/exporting/send-alerts-api.rst
@@ -261,7 +261,7 @@ Troubleshooting
 
         **Alerts arriving but missing Kubernetes context?**
 
-        Check :doc:`Alert Label Mapping </setup-robusta/additional-settings>` to customize how Prometheus labels map to Kubernetes resources.
+        Check :doc:`Customize Labels and Priorities </configuration/alertmanager-integration/customize-labels-priorities>` to customize how Prometheus labels map to Kubernetes resources.
 
 Testing Your Integration
 ------------------------

diff --git a/docs/configuration/holmesgpt/getting-started.rst b/docs/configuration/holmesgpt/getting-started.rst
diff --git a/docs/configuration/holmesgpt/holmesgpt-docs.rst b/docs/configuration/holmesgpt/holmesgpt-docs.rst
diff --git a/docs/configuration/holmesgpt/main-features.rst b/docs/configuration/holmesgpt/main-features.rst
diff --git a/docs/configuration/metric-providers-external.rst b/docs/configuration/metric-providers-external.rst
@@ -185,5 +185,5 @@ Next Steps
 ----------
 
 - Configure :doc:`alert routing </notification-routing/index>`
-- Set up :doc:`AI-powered insights </configuration/holmesgpt/getting-started>`
+- `Set up AI-powered insights <https://platform.robusta.dev/signup>`_
 - Learn about :doc:`common configuration options <metric-providers>`
diff --git a/docs/configuration/sinks/sinks-development.rst b/docs/configuration/sinks/sinks-development.rst
@@ -27,7 +27,7 @@ Each sink consists of a sink class and a config class. Optionally, helpers are u
 
 To implement a new sink you must:
 
-1. :ref:`Build Robusta from source <Build from Source>`
+1. Clone the `Robusta repo <https://github.com/robusta-dev/robusta>`_ and follow the README to build from source
 2. Add a new Python module inside `src/robusta/core/sinks <https://github.com/robusta-dev/robusta/tree/master/src/robusta/core/sinks>`_ containing your sink’s source code
 3. Implement a sink config class
 4. Implement a sink class

diff --git a/docs/configuration/sinks/slack.rst b/docs/configuration/sinks/slack.rst
@@ -20,14 +20,14 @@ Quick Start
 
 **Option 1: Automatic Setup (Recommended)**
 
-When installing Robusta, run ``robusta gen-config`` and follow the prompts. This automatically configures Slack using our `official
+Sign up for a `free Robusta account <https://platform.robusta.dev/signup>`_ and connect Slack during the signup wizard. This automatically configures Slack using our `official
 Slack app <https://slack.com/apps/A0214S5PHB4-robusta?tab=more_info>`_.
 
 Note: Robusta can only write messages and doesn't require read permissions.
 
 **Option 2: Manual Configuration**
 
-Generate a Slack API key by running ``robusta integrations slack``, then add to your ``generated_values.yaml``:
+Generate a Slack API key on your own (see :ref:`Creating Custom Slack Apps` below), then add it to your ``generated_values.yaml``:
 
 .. code-block:: yaml
 

diff --git a/docs/help.rst b/docs/help.rst
@@ -41,54 +41,12 @@ Issues are organized by installation phase to help you quickly find solutions.
 
    <div style="margin: 20px 0; padding: 15px; background-color: #f0f7ff; border-left: 4px solid #0066cc;">
    <strong>Where are you stuck?</strong><br>
-   • <a href="#phase-1-configuration-generation">Phase 1: Configuration Generation</a> - Issues with robusta gen-config<br>
-   • <a href="#phase-2-helm-installation">Phase 2: Helm Installation</a> - Helm install/upgrade failures<br>
-   • <a href="#phase-3-runtime-issues">Phase 3: Runtime Issues</a> - Alerts not arriving, pods crashing<br>
-   • <a href="#phase-4-integration-issues">Phase 4: Integration Issues</a> - Slack, Prometheus connection problems
+   • <a href="#phase-1-helm-installation">Phase 1: Helm Installation</a> - Helm install/upgrade failures<br>
+   • <a href="#phase-2-runtime-issues">Phase 2: Runtime Issues</a> - Alerts not arriving, pods crashing<br>
+   • <a href="#phase-3-integration-issues">Phase 3: Integration Issues</a> - Slack, Prometheus connection problems
    </div>
 
-Phase 1: Configuration Generation
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Issues when running ``robusta gen-config`` or generating initial configuration.
-
-.. details:: command not found: robusta (CLI not in path)
-
-    1. Determine where the Robusta-cli binary file is located
-
-    .. code-block:: bash
-        :name: cb-find-python-cli-loc
-
-        find / -regex '.*/bin/robusta' 2>/dev/null
-
-    2. Add the path you found (e.g ``/opt/homebrew/bin/``) to your PATH. To do so, find your shell config file ( ~/.profile or ~/.bash_profile or ~/.zshrc etc...) and append the following:
-
-    .. code-block:: bash
-        :name: add-path-var
-
-        export PATH="$PATH:<new-path>"
-
-    3. Reopen the terminal or run:
-
-    .. code-block:: bash
-        :name: cb-refresh-terminal
-
-        source <your-shell-config-file>
-
-    .. admonition:: Alternative Solution
-
-      Instead of modifying PATH, run Robusta commands via the python3 binary: ``python3 -m robusta.cli.main gen-config``
-
-.. details:: SSL certificate errors on Mac OS
-
-    This implies a python package with certificates is missing on your system.
-
-    To fix it, run ``/Applications/Python 3.9/Install Certificates.command``
-
-    For more info see:
-    https://stackoverflow.com/questions/52805115/certificate-verify-failed-unable-to-get-local-issuer-certificate
-
-Phase 2: Helm Installation
+Phase 1: Helm Installation
 ^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Problems when running ``helm install`` command or installing via GitOps.
@@ -128,7 +86,7 @@ Problems when running ``helm install`` command or installing via GitOps.
 
       Follow this guide for :ref:`upgrading CRDs from an older version <Manual Upgrade>`.
 
-Phase 3: Runtime Issues
+Phase 2: Runtime Issues
 ^^^^^^^^^^^^^^^^^^^^^^^
 
 Issues after installation when pods are running but not working correctly.
@@ -252,7 +210,7 @@ Holmes
 
         See :ref:`Using Existing Secrets <Reading the Robusta UI Token from a secret in HolmesGPT>` to configure Holmes to read the ``token``
 
-Phase 4: Integration Issues
+Phase 3: Integration Issues
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Problems with external service integrations after Robusta is running.

diff --git a/docs/how-it-works/architecture.rst b/docs/how-it-works/architecture.rst
@@ -1,7 +1,7 @@
 Architecture
 ==================
 
-Robusta uses `HolmesGPT <https://github.com/robusta-dev/holmesGPT>`_, an open source AI agent, to automatically investigate and root-cause Kubernetes alerts. HolmesGPT runs as part of the **in-cluster Agent**, connects to your existing **data sources**, and reports findings through the **Robusta Platform** (SaaS or self-hosted).
+Robusta uses `HolmesGPT <https://github.com/robusta-dev/holmesGPT>`_ to automatically investigate and root-cause alerts. HolmesGPT runs as part of the **in-cluster Agent**, connects to your existing **data sources**, and reports findings through the **Robusta Platform** (SaaS or self-hosted).
 
 .. image:: ../images/architecture-overview.png
    :width: 800
@@ -15,7 +15,7 @@ Agent (In-Cluster)
 The Robusta Agent runs inside your Kubernetes cluster. It includes HolmesGPT and is responsible for:
 
 - Fetching data from external `data sources <https://holmesgpt.dev/data-sources/?tab=robusta-helm-chart>`_
-- Optional: for customers troubleshooting issues on Kubernetes itself, track new deploys and changes to Kubernetes and query Kubernetes events
+- Optional: tracking Kubernetes deploys, changes, and events for teams troubleshooting Kubernetes itself
 
 The Agent keeps your data secure — it fetches data from your data sources directly, so there is no direct connection from the Robusta Platform to your data sources.
 
@@ -44,7 +44,6 @@ Security & Networking
 - The Agent runs entirely within your cluster with configurable RBAC permissions
 - Data sources are accessed only by the in-cluster Agent, never by the Platform
 - SaaS connectivity is outbound-only — no inbound access is required
-- All data remains in your cluster unless explicitly sent to configured sinks or the Robusta Platform
 
 Next Steps
 ^^^^^^^^^^

diff --git a/docs/how-it-works/index.rst b/docs/how-it-works/index.rst
@@ -13,16 +13,16 @@ Overview
 
         How Robusta's components work together — the Agent, HolmesGPT, data sources, and the Platform.
 
-    .. grid-item-card:: :octicon:`package;1em;` Open Source vs SaaS
+    .. grid-item-card:: :octicon:`package;1em;` Deployment Options
         :class-card: sd-bg-light sd-bg-text-light
         :link: oss-vs-saas
         :link-type: doc
 
-        Compare deployment options: open source HolmesGPT, SaaS, and self-hosted.
+        SaaS, self-hosted, or open source HolmesGPT.
 
 .. toctree::
    :maxdepth: 1
    :hidden:
 
    Architecture <architecture>
-   Open Source vs SaaS <oss-vs-saas>
+   Deployment Options <oss-vs-saas>