diff --git a/website/config.toml b/website/config.toml
index 3edc0813cbf6d..b8aecb32b3974 100644
--- a/website/config.toml
+++ b/website/config.toml
@@ -164,23 +164,29 @@ url = "/docs/about"
 parent = "about"
 weight = 1
 
+[[languages.en.menus.footer]]
+name = "What is Observability Pipelines?"
+url = "/docs/about/what-is-observability-pipelines"
+parent = "about"
+weight = 2
+
 [[languages.en.menus.footer]]
 name = "Contact us"
 url = "/community"
 parent = "about"
-weight = 2
+weight = 3
 
 [[languages.en.menus.footer]]
 name = "Privacy"
 url = "https://www.datadoghq.com/legal/privacy/"
 parent = "about"
-weight = 3
+weight = 4
 
 [[languages.en.menus.footer]]
 name = "Cookies"
 url = "https://www.datadoghq.com/legal/cookies/"
 parent = "about"
-weight = 4
+weight = 5
 
 [[languages.en.menus.footer]]
 name = "Components"
diff --git a/website/content/en/docs/about/concepts.md b/website/content/en/docs/about/concepts.md
index 5bf95e3c28263..3e0ae67acae80 100644
--- a/website/content/en/docs/about/concepts.md
+++ b/website/content/en/docs/about/concepts.md
@@ -1,6 +1,6 @@
 ---
 title: Concepts
-weight: 2
+weight: 3
 tags: ["concepts", "meta", "events", "logs", "metrics", "components", "sources", "transforms", "sinks", "pipeline", "roles", "agent", "aggregator", "topology"]
 ---
 
@@ -26,7 +26,7 @@ A **metric** event represents a numerical operation performed on a time series.
 
 ### Traces
 
-A **trace** event can be thought of as a special kind of log event. As of this writing, the components that support trace events are: the `datadog_agent` source, the `datadog_traces` sink, and the `sample` and `remap` transforms.
+A **trace** event can be thought of as a special kind of log event. The components that support trace events are: the `datadog_agent` source, the `datadog_traces` sink, and the `sample` and `remap` transforms. **Note**: Support for traces is limited and is in alpha.
 
 If you're interested in using traces with a Vector component that doesn't yet support them, please open an issue so we can have a better understanding of what components to prioritize adding trace support for.
 
diff --git a/website/content/en/docs/about/what-is-observability-pipelines.md b/website/content/en/docs/about/what-is-observability-pipelines.md
new file mode 100644
index 0000000000000..0d87e3772c4bd
--- /dev/null
+++ b/website/content/en/docs/about/what-is-observability-pipelines.md
@@ -0,0 +1,20 @@
+---
+title: What is Observability Pipelines?
+weight: 2
+tags: ["concepts"]
+---
+
+Datadog's Observability Pipelines is a commercial observability data pipeline for collecting, processing, and routing observability data from any source to any destination in the infrastructure that you own or manage.
+
+Use Observability Pipelines to:
+
+- Manage your pipelines from a control plane. You can build or edit pipelines, whether it is to route a subset of data to a new destination or introduce a new sensitive data redaction rule, and roll out these changes to your active pipelines from the Datadog UI.
+- Monitor your pipelines to understand the health of your pipelines, identify bottlenecks and latencies, fine-tune performance, validate data delivery, and investigate your largest volume contributors.
+- Better optimize volume and control costs by enforcing quotas, store noisy logs in an archive, and more.
+- Scan for and redact sensitive data flowing through your pipelines.
+
+## Learn more
+
+- [Observability Pipelines Overview](https://www.datadoghq.com/product/observability-pipelines/)
+- [Take Control of Your Telemetry Data with Datadog Observability Pipelines](https://www.datadoghq.com/blog/datadog-observability-pipelines/)
+- [Observability Pipelines documentation](https://docs.datadoghq.com/observability_pipelines/)
diff --git a/website/content/en/docs/setup/_index.md b/website/content/en/docs/setup/_index.md
index bd960afc61766..e5e182dc8ac10 100644
--- a/website/content/en/docs/setup/_index.md
+++ b/website/content/en/docs/setup/_index.md
@@ -4,7 +4,7 @@ short: Setup
 weight: 2
 ---
 
-This section of the documentation covers everything you know to get up and running with Vector, from installation to deployment.
+This section of the documentation covers everything you know to get up and running with Vector, from installation to deployment. Alternatively, download [Observability Pipelines](https://www.datadoghq.com/product/observability-pipelines/) if you want to build, manage, and monitor your pipelines in the Datadog UI.
 
 ## Installing