-
🚀
diff --git a/src/get-started/overview/what-is-iexec.md b/src/get-started/overview/what-is-iexec.md
index 3bf5a69f..bd416f56 100644
--- a/src/get-started/overview/what-is-iexec.md
+++ b/src/get-started/overview/what-is-iexec.md
@@ -10,51 +10,88 @@ description:
iExec is a **decentralized confidential computing toolkit** that helps
developers build privacy-preserving applications.
-## 🎯 **Mission**
+## The Protocol (Simple Version)
-iExec democratizes **confidential computing** by providing a toolkit that
-combines:
+### Step 1: Protect Data
-- **🔐 Privacy Protection** - Data remains encrypted during computation
-- **⚡ Scalable Computing** - Access to distributed computing resources
-- **💰 Monetization** - Fair compensation for computing providers
-- **🌐 Decentralization** - No single point of failure or control
+Your sensitive data gets encrypted and stored online. Only you control who can
+access it.
-## 🏗️ **Core Architecture**
+→ **DevTool**: [DataProtector](/references/dataProtector) handles this for you
-### **Three Main Components:**
+### Step 2: Secure Computing (Workers)
-1. **🤖 iApp (iExec Applications)**
- - Confidential computing applications
- - Run in secure enclaves (TEEs)
- - Process encrypted data without exposing it
+Code runs inside **secure enclaves** (TEEs) on iExec workers. The worker can
+access your data to process it, but only within the privacy-safe TEE
+environment - your data never leaves the secure bubble.
-2. **🔐 DataProtector**
- - End-to-end encryption solution
- - Manage data access and sharing
- - Monetize protected datasets
+### Step 3: Run iApp
-3. **⚙️ Worker Network**
- - Distributed computing providers
- - Execute iApp securely
- - Earn
tokens for contributions
+You submit a **Task** = "Run this iApp on this protected data". The protocol
+finds available workers and executes everything confidentially.
-## 🚀 **Key Features**
+→ **DevTool**: [iApp Generator](/references/iapp-generator) helps you create and
+deploy iApp
-- **TEE (Trusted Execution Environment)** support
-- **Zero-knowledge computation**
-- **Decentralized marketplace** for computing resources
-- **
token** for payments and governance
-- **Cross-chain compatibility**
+### Step 4: Get Results
-## 🔗 **Get Started**
+Results come back **encrypted to you**. Workers never see raw data, you never
+lose control.
-Ready to explore iExec? Check out:
+```
+Protected Data + iApp + Worker = Task → Encrypted Result
+```
-- [What is Protected Data?](/get-started/overview/what-is-protected-data)
-- [What is an iApp?](/get-started/overview/what-is-iapp)
-- [Hello World Tutorial](/get-started/helloWorld)
+## What Each Piece Does
-
+### **Protected Data**
+
+Your data, encrypted. You set the rules: "Only these apps can use it, only for
+these purposes."
+
+### **iApp**
+
+Your code, packaged to run on workers. Can be AI models, data processing
+scripts, any computation.
+
+### **Workers (Secure Enclaves)**
+
+Computers that process your data inside privacy-safe TEE environments. They can
+access your data to work with it, but the TEE ensures it stays confidential and
+tamper-proof.
+
+### **Deals**
+
+The execution instruction that unifies the entire flow: "Run this iApp on this
+Protected Data using a TEE Worker, then return the encrypted result to me." The
+protocol takes care of worker allocation and secure coordination.
+
+## Real Example Walkthrough
+
+**AI Model Training (Private)**
+
+1. **Protect**: Medical researchers upload patient data → becomes Protected Data
+2. **Deploy**: AI company packages their model → becomes iApp
+3. **Execute**: Someone submits Task → "Train model on this data"
+4. **Result**: Model gets trained, researcher gets insights, raw data never
+ leaves enclave
+
+**Web3 Email**
+
+1. **Protect**: Users upload email contacts → Protected Data
+2. **Execute**: App submits Task → "Send email via Web3Mail iApp"
+3. **Result**: Email sent, addresses stay private, sender/receiver authenticated
+
+## Start Building
+
+Now that you get the protocol, pick your devtools:
+
+- **Quick Win**: Add [Web3Mail](/references/web3mail) or
+ [Web3Telegram](/references/web3telegram) to your project ! (uses the protocol
+ under the hood)
+- **Protect Data**: Try [DataProtector](/references/dataProtector) to encrypt
+ your first dataset
+- **Build iApp**: Create confidential compute with
+ [iApp Generator](/references/iapp-generator)
+- **Hands-On**: Follow our [Hello World](/get-started/helloWorld) to see all
+ devtools working together
diff --git a/src/get-started/overview/what-is-workerpool.md b/src/get-started/overview/what-is-workerpool.md
deleted file mode 100644
index fa8ffde6..00000000
--- a/src/get-started/overview/what-is-workerpool.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: What is a Workerpool?
-description:
- Learn about workerpools in iExec - the computing resources that execute iApp
----
-
-# What is a Workerpool?
-
-This page is under development.
-
-
diff --git a/src/get-started/overview/workerpool.md b/src/get-started/overview/workerpool.md
new file mode 100644
index 00000000..26699824
--- /dev/null
+++ b/src/get-started/overview/workerpool.md
@@ -0,0 +1,163 @@
+---
+title: Workerpool
+description:
+ Learn about workerpool in iExec - the computing resources that execute iApp
+---
+
+# Workerpool
+
+A **Workerpool** is a group of computing machines (workers) managed by a
+**Workerpool Manager** that provides computational resources to execute iApp in
+secure environments on the iExec network.
+
+
+
Think of a workerpool as a computing cluster where your iApp runs. Each workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.
+
+
+## Key Concepts
+
+### Workerpool Manager
+
+
+
+
+
+
+
•
+
+ Resource Coordinator: Manages and organizes available computing resources
+
+
+
+
•
+
+ Task Scheduler: Distributes tasks among available workers
+
+
+
+
•
+
+ Network Interface: Connects the workerpool to the iExec marketplace
+
+
+
+
+
+### Workers (Computing Machines)
+
+
+
+
+
+
+
•
+
+ TEE-enabled Hardware: Machines equipped with Trusted Execution Environments
+
+
+
+
•
+
+ Task Execution: Run iApp and process protected data securely
+
+
+
+
•
+
+ RLC Rewards: Earn RLC tokens for successfully completed tasks
+
+
+
+
+
+### Security & Privacy
+
+
+
+
+
+
+
•
+
+ TEE Protection: All computations happen inside secure enclaves
+
+
+
+
•
+
+ Data Isolation: Protected data never leaves the secure environment
+
+
+
+
•
+
+ Proof of Contribution: Cryptographic verification of task completion
+
+
+
+
+
+## How Workerpool Work
+
+
+
+
+
1.
+
+ Task Request: User submits a task to execute an iApp on protected data
+
+
+
+
2.
+
+ Workerpool Selection: PoCo system matches request with available workerpool
+
+
+
+
3.
+
+ Task Distribution: Workerpool manager assigns task to an available worker
+
+
+
+
4.
+
+ Secure Execution: Worker downloads iApp and executes it in TEE environment
+
+
+
+
5.
+
+ Result Delivery: Encrypted results are returned to the requester
+
+
+
+
+
+## Getting Started
+
+
+
Want to use workerpool? Start building iApp and the protocol will handle workerpool selection automatically.
+
+
+## Next Steps
+
+
diff --git a/src/references/iapp-generator.md b/src/references/iapp-generator.md
index 3fcbb33b..c653c8b3 100644
--- a/src/references/iapp-generator.md
+++ b/src/references/iapp-generator.md
@@ -37,8 +37,7 @@ SGX/TDX secure enclaves where data stays private during processing.
Start here to understand what iApp are and how they work:
-- **[What Is an iApp?](/get-started/overview/what-is-iapp)** - Core concepts and
- TEE overview
+- **[iApp](/get-started/overview/iapp)** - Core concepts and TEE overview
- **[Getting Started](/references/iapp-generator/getting-started)** - Your first
iApp in 15 minutes
- **[Building Your iApp](/references/iapp-generator/building-your-iexec-app)** -