# Provisioning Provisioning is the process of preparing and registering devices so they can securely connect to and operate within the Nexus Platform. It’s the process of registering the device, assigning it an identity, and giving it the necessary configuration so it can securely connect and start working as part of the platform. Once provisioned, devices are ready to interact with the platform. For example receive their assigned modules, collect data through Data Connectors and publish measurements from Tags. ### Device Types The Nexus platform supports two types of IoT devices, each with different roles and capabilities. When provisioning devices, it’s important to understand the distinction between **Edge Devices** and **Standard Devices**. **Edge Devices** Edge Devices are capable of running Nexus Modules as containerized workloads directly on the device. They handle local data collection, buffering, and—optionally—processing, making them essential for real-time operations and continued functionality during network outages. Edge Devices run the Nexus Edge Runtime and are fully managed from the platform, including deployment, monitoring, and configuration updates. **Standard Devices** Standard Devices are typically simpler or resource-constrained devices such as sensors and embedded controllers. These devices do not support running Nexus Modules, but they may be children of Edge Devices. While Standard Devices can be registered and monitored in Nexus, **module deployment to them is not supported**. --- # 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.tricloudnexus.io/management-portal/management/provisioning.md?ask= ``` 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.