diff --git a/pages/environmental-footprint/additional-content/managed-databases-env-footprint.mdx b/pages/environmental-footprint/additional-content/managed-databases-env-footprint.mdx
new file mode 100644
index 0000000000..9c4cca5107
--- /dev/null
+++ b/pages/environmental-footprint/additional-content/managed-databases-env-footprint.mdx
@@ -0,0 +1,47 @@
+---
+title: Managed Database footprint calculation
+description: This page explains how Scaleway calculates the environmental footprint of its Managed databases in detail.
+tags: managed database environmental-footprint
+dates:
+  validation: 2026-02-10
+  posted: 2026-02-10
+---
+
+This page includes the specificities of the environmental footprint calculation for Managed Databases (PostgreSQL, Redis, and MongoDB).
+
+## Calculation aspects
+
+The environmental footprint of Scaleway's Managed Databases products is calculated by aggregating the impact of all underlying resources dedicated to your database instances, clusters, and associated services (storage, backups, and snapshots).
+
+Since Managed Databases are built on top of other Scaleway products (Instances, Block Storage, Object Storage, Kubernetes), our methodology relies on the sum of these individual components.
+
+### PostgreSQL and MySQL
+
+For PostgreSQL and MySQL databases, the carbon footprint is the sum of the impact of: 
+- **Nodes**: The nodes are based on Scaleway Instances. We apply the [Instance environmental footprint methodology](/environmental-footprint/additional-content/instances-env-footprint/). Each node corresponds to a specific Scaleway Instance type (e.g., a `db-dev1-l` database node uses a `dev1-l` Instance). If you use a High Availability configuration, your database runs on two nodes (a primary and a standby). Therefore, the compute impact is doubled compared to a standalone node. Each additional Read Replica counts as an additional compute node.
+
+- **Storage volumes**: The storage attached to your database for data persistence is based on Scaleway Block Storage. We apply the [Block Storage environmental footprint methodology](/environmental-footprint/additional-content/block-storage-env-footprint/) based on the provisioned capacity (in GB).
+ 
+- **Backups and snapshots**: Automated or manual backups are stored using Object Storage. We apply the [Object Storage environmental footprint methodology](/environmental-footprint/additional-content/object-storage-env-footprint/) based on the size of the stored backups. If you create snapshots of your database volume, we apply the [Block Storage snapshot methodology](/environmental-footprint/additional-content/block-storage-env-footprint/).
+
+- **Control plane**: The control plane represents the shared infrastructure managed by Scaleway to orchestrate, monitor, and maintain your databases. We allocate a fixed share of the global control plane's power consumption and manufacturing impact to each active database node.
+
+
+### Redis
+
+For Redis, the carbon footprint is the sum of the impact of: 
+- **Nodes**: Since Redis™ is an in-memory store, the impact is calculated based on the underlying Instances used to host your nodes. We map your Redis™ node type to its corresponding Scaleway Instance and apply the [Instance environmental footprint methodology](/environmental-footprint/additional-content/instances-env-footprint/). If you use a High Availability configuration, your database runs on two nodes (a primary and a standby). Therefore, the compute impact is doubled compared to a standalone node. If you use Cluster mode, your database impact is the impact of the total number of nodes selected in your cluster configuration (e.g., a 3-node cluster = 3 × Instance impact).
+
+- **Control plane**: The control plane represents the shared infrastructure managed by Scaleway to orchestrate, monitor, and maintain your databases. We allocate a fixed share of the global control plane's power consumption and manufacturing impact to each active database node.
+
+### MongoDB
+
+For MongoDB, the carbon footprint is the sum of the impact of:
+- **The nodes**: Your MongoDB® nodes are effectively Kubernetes nodes running on specific Instance types. We apply the [Kubernetes environmental footprint methodology](/environmental-footprint/additional-content/kubernetes-env-footprint/). As your cluster scales (adding nodes for performance or redundancy), the footprint increases linearly with the number of underlying instances reserved.
+
+- **Storage volumes**:  The storage attached to your database for data persistence is based on Scaleway Block Storage. We apply the [Block Storage environmental footprint methodology](/environmental-footprint/additional-content/block-storage-env-footprint/) based on the provisioned capacity (in GB).
+
+- **Snapshots**: If you create snapshots of your database volume, we apply the [Block Storage snapshot methodology](/environmental-footprint/additional-content/block-storage-env-footprint/).
+
+- **Control plane**: The control plane represents the shared infrastructure managed by Scaleway to orchestrate, monitor, and maintain your databases. We allocate a fixed share of the global control plane's power consumption and manufacturing impact to each active database node.
+
diff --git a/pages/environmental-footprint/menu.ts b/pages/environmental-footprint/menu.ts
index 12c89f4960..48e4e96914 100644
--- a/pages/environmental-footprint/menu.ts
+++ b/pages/environmental-footprint/menu.ts
@@ -68,6 +68,10 @@ export const environmentalFootprintMenu = {
         {
           label: 'Kubernetes footprint calculation',
           slug: 'kubernetes-env-footprint'
+        },
+        {
+          label: 'Managed Database footprint calculation',
+          slug: 'managed-databases-env-footprint'
         }
       ],
       label: 'Additional Content',