diff --git a/pages/instances/menu.ts b/pages/instances/menu.ts
index c565ef50c9..ed67016836 100644
--- a/pages/instances/menu.ts
+++ b/pages/instances/menu.ts
@@ -210,6 +210,14 @@ export const instancesMenu = {
           "label": "Understanding Instance pricing",
           "slug": "understanding-instance-pricing"
         },
+        {
+          "label": "Understanding Instance lifecycle",
+          "slug": "instance-lifecycle"
+        },
+        {
+          "label": "Understanding Instance states",
+          "slug": "instance-states"
+        },
         {
           "label": "Identifying devices of an Instance",
           "slug": "identify-devices"
diff --git a/pages/instances/reference-content/assets/alert.webp b/pages/instances/reference-content/assets/alert.webp
new file mode 100644
index 0000000000..c32d17de58
Binary files /dev/null and b/pages/instances/reference-content/assets/alert.webp differ
diff --git a/pages/instances/reference-content/assets/healthy.webp b/pages/instances/reference-content/assets/healthy.webp
new file mode 100644
index 0000000000..82ae74bfab
Binary files /dev/null and b/pages/instances/reference-content/assets/healthy.webp differ
diff --git a/pages/instances/reference-content/assets/restriction.webp b/pages/instances/reference-content/assets/restriction.webp
new file mode 100644
index 0000000000..c9f1300488
Binary files /dev/null and b/pages/instances/reference-content/assets/restriction.webp differ
diff --git a/pages/instances/reference-content/assets/scaleway_instance_lifecycle.webp b/pages/instances/reference-content/assets/scaleway_instance_lifecycle.webp
new file mode 100644
index 0000000000..0cc8be92a4
Binary files /dev/null and b/pages/instances/reference-content/assets/scaleway_instance_lifecycle.webp differ
diff --git a/pages/instances/reference-content/assets/stop.webp b/pages/instances/reference-content/assets/stop.webp
new file mode 100644
index 0000000000..90c322cbfb
Binary files /dev/null and b/pages/instances/reference-content/assets/stop.webp differ
diff --git a/pages/instances/reference-content/instance-lifecycle.mdx b/pages/instances/reference-content/instance-lifecycle.mdx
new file mode 100644
index 0000000000..9eea3e150a
--- /dev/null
+++ b/pages/instances/reference-content/instance-lifecycle.mdx
@@ -0,0 +1,39 @@
+---
+title: Understanding Scaleway Instances Lifecycle
+description: Learn about the Instance lifecycle at Scaleway.
+tags: Instance lifecycle
+dates:
+  validation: 2026-03-12
+  posted: 2026-03-12
+---
+
+import Requirements from '@macros/iam/requirements.mdx'
+
+import alert from './assets/alert.webp'
+import healthy from './assets/healthy.webp'
+import restriction from './assets/restriction.webp'
+import stop from './assets/stop.webp'
+import lifecycle from './assets/scaleway_Instance_lifecycle.webp'
+
+Scaleway continuously refreshes its hardware to keep performance, security, and sustainability at their best. When an Instance type (for example, an older generation) reaches the end of its planned lifespan, it moves through a defined **lifecycle** that governs how the service is introduced, supported, and eventually retired.
+
+Each stage—ranging from **Private Beta** and **Public Beta** to **General Availability**, followed by a series of "end-of…" phases—has a specific visibility level and set of guarantees (e.g., SLA coverage, feature updates). Understanding this roadmap lets you anticipate when a generation will stop accepting new orders, when feature development will cease, and when you must migrate to a newer generation before the service is fully retired.
+
+<Lightbox image={lifecycle} alt="Scaleway Instance Lifecycle Diagram" />
+
+The table below summarizes the key lifecycle states, their visibility, and what you can expect at each point.
+
+#### Key states
+|   | State                     | Description                                                                                                                                                                |
+|---|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|   | Private Beta              | Early version for a limited group of selected customers. Purpose: test, validate, and provide feedback. Access granted by the product team. No SLA.  |
+|   | Public Beta               | Open testing for all customers. Final features may be incomplete. Intended for test environments. Last step before General Availability (GA). No SLA. |
+| <Lightbox image={healthy} alt="" size="small" />  | General Availability (GA) | Fully launched and supported. Covered by the standard SLA.                                                                                                                 |
+| <Lightbox image={alert} alt="" size="small" />   | End of New Features       | No new features are developed. The offer only receives critical security patches and bugfixes.                                                                             |
+| <Lightbox image={restriction} alt="" size="small" />  | End of Growth             | The Instance type can no longer be ordered by new customers. Existing customers can still create new Instances.                                                            |
+| <Lightbox image={restriction} alt="" size="small" />  | End of Sales              | The Instance type can no longer be ordered by any customer. Existing Instances continue to run normally.                                                                   |
+| <Lightbox image={stop} alt="" />  | End of Life (EOL)         | The service is retired. Any existing Instances are automatically shut down and migrated to equivalent offers for ensured continuity.                    |
+
+<Message type="tip">
+  Scaleway will **inform you via email and console notifications** once an Instance generation enters its **End of Sales** period, providing you with ample time to plan your migration to a newer generation before the End of Life date.
+</Message>
diff --git a/pages/instances/reference-content/instance-states.mdx b/pages/instances/reference-content/instance-states.mdx
new file mode 100644
index 0000000000..1a0a5300cf
--- /dev/null
+++ b/pages/instances/reference-content/instance-states.mdx
@@ -0,0 +1,30 @@
+---
+title: Understanding Scaleway Instance states
+description: Learn about the Instance states on Scaleway and their billing implications.
+tags: Instance lifecycle
+dates:
+  validation: 2026-04-03
+  posted: 2026-04-03
+---
+
+Scaleway Instances can be in several lifecycle states, each reflecting how the underlying compute resources are allocated and billed.  
+Understanding these states helps you choose the most appropriate one for your workload, optimise costs, and avoid unexpected interruptions.
+
+The table below summarizes the official states, their behaviour, and the associated billing implications. Use it as a quick reference when managing your Instances through the Console, API, or CLI.
+
+| State                | Description                                                                                                                                                                                                                                                                                                                                 |
+|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| **Running**          | The Instance is fully active and consumes compute resources. This is the default after creation or after a power‑on. **Full billing applies** (compute + storage + IP).                                                                                                                                                                      |
+| **Stopped**          | The Instance is halted and the underlying hypervisor is released. Compute billing **stops**, but you continue to pay for any attached storage (local volumes that you chose to keep or Block Storage volumes) and for any Flexible IPs. When stopping you can:<br />• **Keep local storage** – it remains attached and is billed as storage.<br />• **Archive local storage** – the data is snapshotted to the volume store; the Instance can be restarted later and the snapshot is restored automatically. This is the recommended option for long‑term cost savings. |
+| **Error / Locked**   | Temporary or administrative states (e.g., during a resize, rescue mode, or when the Instance is locked to prevent accidental actions). No billing changes occur while the Instance is in these states; you are billed according to the underlying resources that remain allocated.                                            |
+| **Deleted**          | The Instance and its local volumes are permanently removed. Flexible IPs that were attached are **preserved** unless you release them manually. Once deleted, the resource no longer appears in the API/Console.                                                                                                                    |
+
+### Additional notes
+
+- **Protected flag** – Instances have a `protected` attribute that can be [enabled to prevent accidental stop or delete operations](Instances/how-to/use-protected-Instance/). This is **not a lifecycle state**; it is a safety setting you can toggle in the Console or via the API.
+- **Billing summary**  
+  - **Running:** compute + storage + IP.  
+  - **Stopped (keep local storage):** storage + IP (no compute).  
+  - **Stopped (archive local storage):** snapshot storage + IP (no compute).  
+  - **Deleted:** no ongoing charges (except for any IPs you keep).  
+