> For the complete documentation index, see [llms.txt](https://openvpp.gitbook.io/openvpp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openvpp.gitbook.io/openvpp-docs/technology-overview/registry-service.md).

# Registry Service

The Registry Service is an on-chain database which stores all of the device and utility addresses and attribute, capability, and program data. The service is updated any time a device connects or disconnects from a utility or when it enrolls or unenrolls from a program. The service keeps a log of all of the active formed connections and represents a global picture of all device-to- utility links.

The Registry Service is only called upon when a device’s connectivity status is changed and does not have knowledge or partake in the day-to-day traffic between a device and utility server.

A fee is assessed in $OVPP for commercial users (such as utilities, governments, or grid operators) who want to view “grid level device awareness” data. This data can be accessed via API.

The registry service handles all device and utility data for example:

The registry service handles all device and utility data for example:

* Device make and mode}
* Device capability (kW, kWh, etc.)ƒ
* Device protocol†
* Device enrollment and connectivity status
* Utility territory and program mapping
* Utility enrollment quantities
* Utility and device server addresses