# Roadmap

Idle Network will adopt a staged roll-out process, proving out the system architecture on existing rewards networks via easily accessible device categories before launching Native MetaVaults and that apply the analogous architecture to monetize increasingly exotic idle asset categories.\
\
The roadmap will develop as follows:\
\
**Q3 2025: Roll-Out of PoC & OmniPlatform MetaVaults V1**

* **Asset Focus:** Idle compute, storage and bandwidth
* **Rewards Focus:** OmniPlatform MetaVaults harnessing rewards from existing ecosystems.
* **Extra Features:** Rewards Bridge Layer rolled out

**Q4 2025: Roll-Out of Idle Robotics & Drones Marketplace**

* **Asset Focus:** Idle robotics devices and drones
* **Rewards Focus:** Native MetaVaults generating rewards for currently uncatered to asset categories
* **Extra Features:** Edge Compute Vaults & OEM Pilots

**Q1 2026: Roll-Out of Idle MCU & IOT Marketplace**

* **Asset Focus:** Idle MCUs and IOT devices
* **Rewards Focus:** Existing rewards to be boosted by new customer streams via Customer Discovery Portal on native Idle Network Robotics & Drones Marketplace&#x20;
* **Extra Features: Native** Customer Discovery Portal connecting idle asset owners to users in demand of idle assets

**Q2 2026: OEM Licensing Stack**

* **Asset Focus:** OEM licensing deals
* **Rewards Focus:** Multi-model OEM license monetization model
* **Extra Features:** Additional high-demand asset categories added to marketplace


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.idlenetwork.com/tokenomics-and-roadmap/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
